This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ANNOUNCEMENT] xterm 348-1

Am 07.11.2019 um 03:39 schrieb Takashi Yano:
Wait. I have just found /etc/X11/app-defaults/XTerm has a entry
*VT100*eightBitInput: false
which is added from cygwin xterm 348-1.

Removing this line or changing the value to true solves this issue.

Katsumi, could you please check if this solves the issue?
The option value of eightBitInput must not be set to false nowadays, it's a relic of ASCII times. There are a number of further questionable changes in /etc/X11/app-defaults/XTerm
(not checked to other XTerm default entries there):

 < *backarrowKeyIsErase: true
 < *metaSendsEscape: true
 < *ptyInitialErase: true
 > ! Cygwin Defaults
 > +*backarrowKeyIsErase: true
 > +*metaSendsEscape: true
 > +*ptyInitialErase: true
Using the obscure "+" prefix here seems to reset the option to its default, regardless of the given value. Clearer configuration would be preferrable. Changing backarrowKeyIsErase and ptyInitialErase consistently may go unnoticed for most users, but it effectively switches away from the Linux habit to use DEL for the backarrow key, just to note. Setting metaSendsEscape to false make input inconsistent. Alt+x will still enter ESC x (for whatever reason) but Alt+ö will enter only ö (again, for whatever reason). Option value true makes this consistent.

 > ! Red Hat Defaults:
 > *allowFontOps: false
 > *allowTcapOps: false
The "allow*" options are meant to provide security but I see no security problem with these two, particularly not TcapOps (which seems to be used by vim to fine-tune terminal feature usage).

 > *VT100*eightBitInput: false
Must be true!
 > *VT100*scrollBar: true
Why not, but it's a change that users may dislike.
 > *VT100*utf8Title: true
Probably a good idea.
 > *termName: xterm-256color
For applications that make a difference in colour usage depending on the TERM setting, this updates mega-legacy 16 colours to legacy 256 colours. Note that xterm also supplies a terminfo entry "xterm-direct" to reflect true colour support. Using it would require an update of the terminfo package, too, though, to get the xterm-direct entry included.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]