bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Solaris 9 'less' mishandles groff 1.19 SGR commands


From: Paul Eggert
Subject: Re: Solaris 9 'less' mishandles groff 1.19 SGR commands
Date: Wed, 18 Jun 2003 15:59:57 -0700

> Date: Sat, 07 Jun 2003 10:01:27 +0200 (CEST)
> From: Werner LEMBERG <address@hidden>
> 
> From: "Paul Eggert" <address@hidden>
> Subject: Solaris 9 'less' mishandles groff 1.19 SGR commands
> Date: Fri,  6 Jun 2003 14:49:04 -0700
> 
> > groff -Tascii -man /usr/share/man/man1/bash.1 | /usr/bin/less -R
> > 
> > DESCRIPTION OF INCORRECT BEHAVIOUR:
> > The output doesn't look good, because "less" doesn't seem to
> > act on escape sequences like "ESC [ 2 4 m".  It does act on
> > "ESC [ 0 m", though.  I don't know why.
> > 
> > /usr/bin/less -V reports "less 358".  I built and used less 381, but
> > had the same problem with it.
> 
> I can't reproduce this problem on my GNU/Linux box.  It looks like
> being related to Solaris 9.  Until today, I didn't get such a report.
> Mark, anything known about Paul's problem?



I looked into the problem some more, and it's a problem with "kterm".
Apparently kterm 6.2.0 doesn't support escape sequences like "ESC [ 2
4 m".  It works OK with xterm.  Unfortunately we use kterm a lot
around here, since we have to deal with Kanji, so asking people to use
xterm is a non-starter.  Anyway, perhaps you should mention in the
groff and/or less documentation that "less -R" does not work with
kterm so people who want Japanese support have to avoid this solution.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]