Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: [Heads up] TERM=xterm is now the default (on non-i386)

0 views
Skip to first unread message

Andrey Chernov

unread,
Nov 29, 2009, 11:41:30 PM11/29/09
to
On Fri, Nov 13, 2009 at 07:00:21AM +0100, Ed Schouten wrote:
> Hi folks,
>
> I just committed the previously mentioned patch to SVN. Please refer to
> the last part of the commit message to see what you can do when you run
> into trouble.

It seems xterm emulator can't co-exist with screen maps, namely
vidcontrol -l koi8-r2cp866
I got Russian letters everywhere instead of vt100 pseudographics due to
missing (i.e. default) ac= termcap capability (f.e. in tzsetup etc.)
There are 2 ways to fix it.
1) Make separate xterm-r with corrected ac= (that way is ugly).
2) Don't seek for vt100 pseudographics in loaded font at all, just use
internal kernel font.
Please decide how to fix this better. For now only fallback to '-T cons25'
is solution for Russian users.

--
http://ache.pp.ru/

Andrey Chernov

unread,
Nov 30, 2009, 12:49:19 AM11/30/09
to
On Mon, Nov 30, 2009 at 07:41:30AM +0300, Andrey Chernov wrote:
> Please decide how to fix this better. For now only fallback to '-T cons25'
> is solution for Russian users.

Another bug found.
-T cons25 can't coexist with 'mode' argument, i.e.
xterm# vidcontrol -T cons25 80x30
really makes xterm 80x30, not cons25 80x30.
xterm# vidcontrol -T cons25
alone works, but there is only single 'allscreens_flags' variable in the
/etc/rc.conf, so I can't switch to 80x30 at once.

The strange thing is that
cons25# vidcontrol -T xterm 80x30
works as supposed.

Please fix.

--
http://ache.pp.ru/

Vladimir Grebenschikov

unread,
Dec 13, 2009, 10:33:22 AM12/13/09
to
Hi

Any chance to get it fixed somehow ?

midnight commander does not work correctly even with no screen-maps,
vidcontrol -T xterm, env TERM=xterm LANG=ru_RU.UTF-8


also, console does not handle correctly multi-byte utf-8 characters
(it should already or not ?)


-----Original Message-----
From: Andrey Chernov <ac...@nagual.pp.ru>
To: Ed Schouten <e...@80386.nl>
Cc: FreeBSD Current <cur...@freebsd.org>
Subject: Re: [Heads up] TERM=xterm is now the default (on non-i386)
Date: Mon, 30 Nov 2009 07:41:30 +0300

On Fri, Nov 13, 2009 at 07:00:21AM +0100, Ed Schouten wrote:
> Hi folks,
>
> I just committed the previously mentioned patch to SVN. Please refer to
> the last part of the commit message to see what you can do when you run
> into trouble.

It seems xterm emulator can't co-exist with screen maps, namely
vidcontrol -l koi8-r2cp866
I got Russian letters everywhere instead of vt100 pseudographics due to
missing (i.e. default) ac= termcap capability (f.e. in tzsetup etc.)
There are 2 ways to fix it.
1) Make separate xterm-r with corrected ac= (that way is ugly).
2) Don't seek for vt100 pseudographics in loaded font at all, just use
internal kernel font.

Please decide how to fix this better. For now only fallback to '-T cons25'
is solution for Russian users.

--
Vladimir B. Grebenschikov
vo...@fbsd.ru
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

0 new messages