Discussion:
terminal emultators
Sam Carleton
2002-09-11 15:59:20 UTC
Permalink
I have been using VanDyke's SecureCRT for a while now
as the primary terminal to my NetBSD machine. Today
I discovered that it will display color for me when
I tell it to use the Linux terminal type.

Now, vim seems to work fine, as does many other apps,
but when mutt displays messages in threads, the
characters used nolonger looks like the little
arrows they use to look like. I was wondering if
there is some way to fix this for mutt and other
app that would have the problem?

Sam
Aaron J. Grier
2002-09-11 22:28:47 UTC
Permalink
I have been using VanDyke's SecureCRT for a while now as the primary
terminal to my NetBSD machine. Today I discovered that it will
display color for me when I tell it to use the Linux terminal type.
secureCRT reports its term type as vt220, which is a black & white
terminal. the color version in the vt220-series (according to
http://vt100.net/) was vt241, but that terminal type doesn't appear to
be in either terminfo or termcap as distributed by NetBSD.

TERM=xterm-16color gives color with secureCRT set to vt220.
Now, vim seems to work fine, as does many other apps, but when mutt
displays messages in threads, the characters used nolonger looks like
the little arrows they use to look like. I was wondering if there is
some way to fix this for mutt and other app that would have the
problem?
what you normally see with secureCRT set to vt220 under mutt are not
supposed to be little arrows: they're line-draw characters -- the
arrowheads shouldn't be there.

this gets even screwier with secureCRT set to linux, which uses IBM
character set if I'm not mistaken.

I thing what secureCRT really wants to be is a vt340 or vt340+, which is
color and uses ISO Latin 1 encoding. vt241 would work too, if secureCRT
can actually get their character mapping straightened out. a workaround
would be to allow the user to change the TERM string passed to the
server when opening a session.

likewise termcap and terminfo should add color for vt340, and an entry
for vt241. (I guess I should file a PR...)
--
Aaron J. Grier | "Not your ordinary poofy goof." | ***@poofygoof.com
"i'm convinced that the cray cabinet has an outlet for plugging in
welding attachments." -- Skeezics Boondoggle, on the cray CS6400
Johnny Billquist
2002-09-18 09:54:11 UTC
Permalink
Post by Aaron J. Grier
I have been using VanDyke's SecureCRT for a while now as the primary
terminal to my NetBSD machine. Today I discovered that it will
display color for me when I tell it to use the Linux terminal type.
secureCRT reports its term type as vt220, which is a black & white
terminal. the color version in the vt220-series (according to
http://vt100.net/) was vt241, but that terminal type doesn't appear to
be in either terminfo or termcap as distributed by NetBSD.
Yes and no. The Vt241 have four colors, but you don't select them with the
ansi attribute escape sequences... (and neither on the VT340 which have 16
colors).
Post by Aaron J. Grier
likewise termcap and terminfo should add color for vt340, and an entry
for vt241. (I guess I should file a PR...)
Unless you really check out how to select different colors, don't do
this. They don't support the ansi color attribute sequences.

Johnny

Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: ***@update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Aaron J. Grier
2002-09-19 02:12:48 UTC
Permalink
Post by Johnny Billquist
Yes and no. The Vt241 have four colors, but you don't select them with
the ansi attribute escape sequences... (and neither on the VT340 which
have 16 colors).
Post by Aaron J. Grier
likewise termcap and terminfo should add color for vt340, and an
entry for vt241. (I guess I should file a PR...)
Unless you really check out how to select different colors, don't do
this. They don't support the ansi color attribute sequences.
wow. so there were never any VT-series terminals which had ansi color
support?

time to pester the makers of secureCRT to get their TERM setting
straight... ;)
--
Aaron J. Grier | "Not your ordinary poofy goof." | ***@poofygoof.com
"i'm convinced that the cray cabinet has an outlet for plugging in
welding attachments." -- Skeezics Boondoggle, on the cray CS6400
Johnny Billquist
2002-09-19 06:57:37 UTC
Permalink
Post by Aaron J. Grier
wow. so there were never any VT-series terminals which had ansi color
support?
I seem to remember that the VT500-series finally supports this.
Post by Aaron J. Grier
time to pester the makers of secureCRT to get their TERM setting
straight... ;)
There are, unfortunately, very few good terminal emulators. I still use
KERMIT, which is definitely the best I've found.

Johnny

Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: ***@update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Brian A. Seklecki
2002-09-12 19:49:50 UTC
Permalink
On Wed, 11 Sep 2002 @ 11:59am (-0400), Sam Carleton wrote:

SC> I have been using VanDyke's SecureCRT for a while now

in securecrt, just change the font to 'vt100' or terminal

make sure $TERM is set to xterm-color

-lava


SC> as the primary terminal to my NetBSD machine. Today
SC> I discovered that it will display color for me when
SC> I tell it to use the Linux terminal type.
SC>
SC> Now, vim seems to work fine, as does many other apps,
SC> but when mutt displays messages in threads, the
SC> characters used nolonger looks like the little
SC> arrows they use to look like. I was wondering if
SC> there is some way to fix this for mutt and other
SC> app that would have the problem?
SC>
SC> Sam
SC>

later - | _BonaFide[] = { coder, author, | /~\ The ASCII Ribbon
Brian A. Seklecki | problem solver, scholar, BOFH, | \ / Campaign Against
| vegetarian, runner, NetBSD | X Exchange, Outlook
| advocate, spiritual machine }; | / \ & HTML Email

PGP: 0111 4618 0111 4618 4AB2 24EB C853 6611 75C4 A91E A7A7 4973
Jim Breton
2002-09-13 00:05:37 UTC
Permalink
Post by Sam Carleton
but when mutt displays messages in threads, the
characters used nolonger looks like the little
arrows they use to look like. I was wondering if
there is some way to fix this for mutt and other
app that would have the problem?
Other people have suggested ways of setting the proper terminal type,
and I'm sure that is the "correct" way of fixing it. But for the sake
of completeness, if you were to encounter a terminal emulator that just
did not have the modes you need to display those "arrows" correctly, in
mutt you can set the "ascii_chars" variable which should work with any
terminal type. They don't look as good as the normal drawn-characters,
but they'll work everywhere. HTH.
Loading...