thanks,
The XFree86 xterm supports ANSI color and VT220 emulation
There's an faq at
http://invisible-island.net/xterm/xterm.faq.html
ftp://invisible-island.net/xterm
--
Thomas E. Dickey <dic...@radix.net> <dic...@herndon4.his.com>
http://dickey.his.com
ftp://dickey.his.com
/usr/dt/bin/dtterm or upgrade to Solaris 9 which adds color support to
Solaris xterm.
--
________________________________________________________________________
Alan Coopersmith al...@alum.calberkeley.org
http://www.CSUA.Berkeley.EDU/~alanc/ aka: Alan.Coo...@Sun.COM
Working for, but definitely not speaking for, Sun Microsystems, Inc.
> /usr/dt/bin/dtterm or upgrade to Solaris 9 which adds color support to
> Solaris xterm.
for the latter, try
http://invisible-island.net/vttest/
(there are a number of new problems which I observed running the i18n patch,
which your previous posting indicated was the one that ships with Solaris 9)
At least on Solaris 9 the on board xterm just supports colors.
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schi...@fokus.gmd.de (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
guess why... ;-)
--
Kjetil T. ==. ,,==. ,,==. ,,==. ,,==. ,,==
::://:::://:::://:::://:::://::::
=='' `=='' `=='' `=='' `=='' `== http://folding.stanford.edu
> guess why... ;-)
not exactly. I read in this newsgroup that the Solaris 9 xterm uses a
different patch. That article pointed to a patch which is supposedly the
changes that were incorporated. It fails a few tests in vttest which the other
versions do not. Given what I saw, dtterm is still better than that version.
It's actually based on the Li18nux xterm, not the XFree86 one.
This is really interesting:
If you log into Linux from a Solaris xterm and call 'man something'
you will see rotten output.
- Underlines are always going to the left end of the window
- After more displayes the first prompt, the screen stays
inverse video.
This happens if I use the less/more that is on Linux (Uses TERMINFO)
or with my 'p' ftp://ftp.fokus.gmd.de/pub/unix/p (uses my completely
stand alone TERMCAP implementation) with the Linux supplied databases.
If you do the same Linux/linux there is no problem.
If I use ~/.termcap file with an xterm entry fetched from Eric Raymonds
server and use my 'p', everything is OK too.
yes. Reading the patch, less than 10% was focused on the i18n aspect which it
supposedly uses as an improvement. Rather than indulging in not-invented-here
(the other 90%), it might be nice to abstract that portion, define it
properly, and make it configurable.
(some of the commentary in the patch was incorrect, which tends to obscure
what was actually done)
> This is really interesting:
> If you log into Linux from a Solaris xterm and call 'man something'
> you will see rotten output.
> - Underlines are always going to the left end of the window
that's probably one of the details that I indicated for vttest
> - After more displayes the first prompt, the screen stays
> inverse video.
but this one is a different matter - using the XFree86 xterm terminfo
(which has vt220-style controls) on the Solaris xterm, which used to
emulate at least vt102 (but falls short with the Solaris 9 version).
Perhaps it will all work properly in Solaris 10 (or 9r2, etc).
> /usr/dt/bin/dtterm or upgrade to Solaris 9 which adds color support to
> Solaris xterm.
well he did say he's running Solaris 5. I've been told that some hardware
won't upgrade to Solaris 8 or 9. And if it's an old box that he doesn't
own, perhaps dtterm isn't an option either.
(it would be nice if OP would followup in these threads ;-)
>> This is really interesting:
>
>> If you log into Linux from a Solaris xterm and call 'man something'
>> you will see rotten output.
>
>> - Underlines are always going to the left end of the window
>
>that's probably one of the details that I indicated for vttest
The vttest does not reproduce the problem...
>> - After more displayes the first prompt, the screen stays
>> inverse video.
>
>but this one is a different matter - using the XFree86 xterm terminfo
>(which has vt220-style controls) on the Solaris xterm, which used to
>emulate at least vt102 (but falls short with the Solaris 9 version).
>
>Perhaps it will all work properly in Solaris 10 (or 9r2, etc).
The test has been made on S9 9/02, but it seems obvious that the bug
is on the Linux side. If you use the official terminal description
from Eric Raymond, no problems occur.
> The vttest does not reproduce the problem...
When I ran vttest on this a few months ago there was more than one problem
in the first few screens (enough that I didn't bother keeping the executable
for retesting, though I do of course still have the patch). If I have to
go back and re-test, I'll document it in my faq.
>>Perhaps it will all work properly in Solaris 10 (or 9r2, etc).
> The test has been made on S9 9/02, but it seems obvious that the bug
> is on the Linux side. If you use the official terminal description
> from Eric Raymond, no problems occur.
actually it's a copy of one that I wrote.
On Solaris 7 (I have not confirmed Solaris 9) the xterm in /usr/openwin
wants to use a different sequence for exitting standout mode than the
terminfo and termcap specify for "xterm" on RedHat systems. There may be
other salient differences that I do not recall.
If you log into a RedHat system from an xterm on a Solaris system, use
"xterm-r6" for your terminal type and "more", "less", etc. work just
fine.
--
Daryl Clevenger
dlc=use...@cs.cmu.edu
>>>It's actually based on the Li18nux xterm, not the XFree86 one.
>>
>>This is really interesting:
>>
>>If you log into Linux from a Solaris xterm and call 'man something'
>>you will see rotten output.
>>
>>- Underlines are always going to the left end of the window
>>
>>- After more displayes the first prompt, the screen stays
>> inverse video.
>>
>>This happens if I use the less/more that is on Linux (Uses TERMINFO)
>>or with my 'p' ftp://ftp.fokus.gmd.de/pub/unix/p (uses my completely
>>stand alone TERMCAP implementation) with the Linux supplied databases.
>>
>>If you do the same Linux/linux there is no problem.
>
>On Solaris 7 (I have not confirmed Solaris 9) the xterm in /usr/openwin
>wants to use a different sequence for exitting standout mode than the
>terminfo and termcap specify for "xterm" on RedHat systems. There may be
>other salient differences that I do not recall.
>
>If you log into a RedHat system from an xterm on a Solaris system, use
>"xterm-r6" for your terminal type and "more", "less", etc. work just
>fine.
So you confirm a Linux bug.
The official string for exitting standout mode does work also and for this
reason, the official xterm TERMCAP entry does work too.
There is no reason for this Linux specifics.... It looks to me the same as
is a person on Linux write a script that calls "rm --force" instead
of "rm -f".
It is just non-portable....
It is coming back to me...I looked at this a few years ago.
On Solaris, the termcap entries for se and ue (rmso and rmul in terminfo)
use the sequence
se=\E[m
ue=\E[m
On RedHat (6.2 and 7.1), "xterm" is actually "xterm-redhat" (which sets kD
and kb) and in turn uses "xterm-xfree86". The "xterm-xfree86" entry contains
se=\E[27m
ue=\E[24m
I have no idea if this is really the xfree86 termcap entry, nor who is
right or wrong in this case. I also see there are other differences between
the entries on the 2 systems, but have no idea what is right or wrong.
--
Daryl Clevenger
dlc=use...@cs.cmu.edu
> On RedHat (6.2 and 7.1), "xterm" is actually "xterm-redhat" (which sets kD
> and kb) and in turn uses "xterm-xfree86". The "xterm-xfree86" entry contains
> se=\E[27m
> ue=\E[24m
> I have no idea if this is really the xfree86 termcap entry, nor who is
> right or wrong in this case. I also see there are other differences between
> the entries on the 2 systems, but have no idea what is right or wrong.
it's an faq
http://invisible-island.net/xterm/xterm.faq.html#xterm_hilite
(i am using solaris 2.5)
thanks,
Kees Damen <kees....@chello.nl> wrote in message news:<3DA34F81...@chello.nl>...
unless you set TERM on the linux box to be TERM=xterm-r5
--
[Trim the no-bots from my address to reply to me by email!]
[ Do NOT email-CC me on posts. Pick one or the other.]
S.1618 http://thomas.loc.gov/cgi-bin/bdquery/z?d105:SN01618:@@@D
http://www.spamlaws.com/state/ca1.html
But this is not what I like to do....
If Linux uses a different TERM than others (or a noticable number
of people) then Linux should rather default to TERM=xterm-r5 and
keep a backward compatible TERM=xterm for other users.
> But this is not what I like to do....
> If Linux uses a different TERM than others (or a noticable number
> of people) then Linux should rather default to TERM=xterm-r5 and
> keep a backward compatible TERM=xterm for other users.
That's basically what I do. Each terminal emulator sets $TERM to the
correct one (on my home machine, I therefore have xterm-r5, xterm-r6,
color_xterm, rxvt, Eterm, xterm-xfree86). But it seems too complicated
for users to do this (which is why I see random advice to set it to
vt100, linux, xterm-color, xterm).
I agree.
Now try convincing the fanatics they should actually stick to standards.
I've tried. It's ugly.
NIH developers decide to rewrite the standards, and then opensource
fanatics conclude, "the linux developer did it this way, it MUST be the
BEST way!"
Actually, it's worse than that. The "xterm FAQ" actually recommands that
if you have [tweaked] xterm installed, and want to keep interoperability
with other hosts, you should adjust the xterm resources so that it
auto-sets the TERM to be xterm-xyz, and keep the system 'xterm' termcap
definition pure.
But the X maintainer of a certain unnamed linux distro is a hothead who doesnt
give a damn about cross-platform compatibility,
or anyone else's way but his own.
(Yet he has the gall to reference the xterm FAQ, still!)
> But the X maintainer of a certain unnamed linux distro is a hothead who doesnt
> give a damn about cross-platform compatibility,
> or anyone else's way but his own.
> (Yet he has the gall to reference the xterm FAQ, still!)
but at least he responds to email, unlike the so-called maintainers of
other distributions.