[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: TERM=ibm327x causes an error with setupterm
From: |
Dr. Werner Fink |
Subject: |
Re: TERM=ibm327x causes an error with setupterm |
Date: |
Fri, 24 Jan 2014 23:16:19 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Jan 24, 2014 at 04:35:36PM -0500, Thomas Dickey wrote:
> On Fri, Jan 24, 2014 at 03:54:51PM +0100, Dr. Werner Fink wrote:
> > Hi,
> >
> > on s390 the command tput and tset returning
> >
> > s390vsl065:~ # TERM=ibm327x tset
> > tset: unknown terminal type ibm327x
> > Terminal type?
> >
> > it works with TERM=dumb but the natural terminal type seems to
> > be ibm327x:
>
> The entry is marked "gn" (generic).
>
> tset uses setupterm, and the error message is consistent with the manpage
> description of setupterm:
>
> 0 means that the terminal could not be found, or that it is a generic
> type, having too little information for curses applications to run.
Hmm ... then I've to reconfigure agetty not to use ibm327x but dumb even if on
a 3270 or 3272 line. Or the other solution could be to remove the gn even if
the line is a block input and not character input type. This because it
makes no sense to warp every ncurses application like tput.
> > s390vsl065:~ # infocmp -T ibm327x -1
> > # Reconstructed via infocmp from file:
> > /usr/share/terminfo/i/ibm327x
> > ibm327x|line mode IBM 3270 style,
> > gn,
> > clear=^M^J,
> > el=^M,
> > home=^M,
> > s390vsl065:~ # infocmp -T dumb -1
> > # Reconstructed via infocmp from file: /usr/share/terminfo/d/dumb
> > dumb|80-column dumb tty,
> > am,
> > cols#80,
> > bel=^G,
> > cr=^M,
> > cud1=^J,
> > ind=^J,
> >
> > how can I avoid this?
Werner
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
pgpqnEdgX51Cz.pgp
Description: PGP signature