NetBSD-Bugs archive

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

Re: bin/56496: etcupdate(8) merge formatting issue

The following reply was made to PR bin/56496; it has been noted by GNATS.

From: Valery Ushakov <>
Cc: Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>
Subject: Re: bin/56496: etcupdate(8) merge formatting issue
Date: Fri, 19 Nov 2021 16:40:02 +0300

 On Thu, Nov 18, 2021 at 21:45:01 +0000, Hauke Fath wrote:
 > > see tset(1) ... setting the tabs is something
 > > it does.
 > Even when all 'tset -Qs' is supposed to do is produce shell-specific
 > command strings for setting TERM?
 TERM is not describing something set in stone.  You can can have a
 termcap entry (i.e. the value that TERM points to) that, say,
 describes vt220 with application cursor keys and have the init
 sequence that turns that feature on.  Or you can setup the entry to
 describe normal cursor keys and have the init sequence that turns that
 off.  Now, I no longer remember if application keys are the default on
 vt220 (probably not), but if the vt220 entry is set up with
 application keys and you don't output the init sequence, you will not
 see the application key sequences on key presses.  Ditto for other
 features, like auto wrap and what not.  You can actually see in the
 database entries like vt200-w for 132 columns wide mode, etc.
 So it's not really that unlogical a choice for tset to re/init the
 termial.  It's like: "Ok, I have put your device in the specicic known
 state w.r.t. its possible configurations, that is described by the
 termcap entry $TERM".
 On Fri, Nov 19, 2021 at 11:35:01 +0000, Hauke Fath wrote:
 >  >  Unfortunately, yes. One has to do `tset -Qs -` to make tset not
 >  >  send the term init sequences.
 >  That would be great, except for whatever reason `tset -Qs -` output
 >  prepends the terminal string:
 >  % echo `tset -Qs -`
 >  xterm set noglob; setenv TERM xterm; unset noglob;
 echo `tset -Qs - | sed 1d`  ?

Home | Main Index | Thread Index | Old Index