Re: [dwm] [ANNOUNCE] dvtm-0.5

From: Donald Chai <donald.chai_AT_gmail.com>
Date: Fri, 30 Jan 2009 20:07:50 -0800

On Jan 30, 2009, at 6:43 AM, bill lam wrote:

> On Fri, 30 Jan 2009, Donald Chai wrote:
>>
>> On Jan 29, 2009, at 8:54 PM, bill lam wrote:
>>> 1. on my ubuntu, $TERM is xterm (actually it is 256 color), but
>>> dvtm
>>> cannot detect it and makes it a 8 (or 16?) color rxvt.
>>
>> You probably need to set TERM to xterm-256color. If 'infocmp xterm'
>> says you have 8 colors, ncurses and dvtm will think your terminal
>> only
>> supports 8 colors. If you don't have the proper terminfo files,
>> then be
>> prepared for some fun with 'infocmp' and 'tic'.
>>
>
> After install terminfo for xterm-256color,
> echo $TERM inside xterm now gives xterm-256color, but after enter
> dvtm,
> echo $TERM now gives rxvt-256color, why not xterm-256color?.
> Moreover colors are displayed incorrectly. This is worse than using
> the previous xterm setting.

So you mean that if you run the following shell command both outside
and inside dvtm, you get different results?
        for i in `seq 1 64`; do echo -e "\e[38;5;${i}mXXX"; done
The colors *should* match. If not, that's a bug.

TERM is set to rxvt or rxvt-256color because those are the escape
sequences interpreted by madtty.c. If you have code that absolutely
must have TERM=xterm, I think it's sufficient to modify "keytable" in
that file.

>>> 2. if start dvtm from dmenu typing "xterm -e dvtm" there is always
>>> an
>>> extra ^Z placed in ttyin so that when I start to type any
>>> character, the ^Z appear and I have to delete it,
>>> However if I start dvtm from xterm, it is OK.
>>
>> Change config.mk to use ncursesw (LIBS_UTF8).
>>
>
> I already built with unicode
> $ldd dvtm
> linux-vdso.so.1 => (0x00007fffa7ffe000)
> libc.so.6 => /lib/libc.so.6 (0x00007f869f99c000)
> libutil.so.1 => /lib/libutil.so.1 (0x00007f869f799000)
> libncursesw.so.5 => /lib/libncursesw.so.5 (0x00007f869f552000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f869fd0e000)
> libdl.so.2 => /lib/libdl.so.2 (0x00007f869f34e000)

There seems to be some sort of race condition between SIGWINCH being
raised and some other magic. I personally use rxvt-unicode (which
works fine with "urxvt -e dvtm") and only ever use dvtm on remote
computers, so I'm not inclined to dig any deeper into this.
Received on Sat Jan 31 2009 - 04:07:50 UTC

This archive was generated by hypermail 2.2.0 : Sat Jan 31 2009 - 04:12:13 UTC