From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com, Yaakov Selkowitz <yselkowi@redhat.com>
Subject: Re: [ANNOUNCEMENT] xterm 348-1
Date: Thu, 07 Nov 2019 08:31:00 -0000 [thread overview]
Message-ID: <f24b92f6-4a12-5142-b4c6-330c4613031d@towo.net> (raw)
In-Reply-To: <20191107113936.129b5b6f0c1879dbd5be7ed7@nifty.ne.jp>
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.
------
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-11-07 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 22:43 Yaakov Selkowitz
2019-11-01 1:36 ` Katsumi Yamaoka
2019-11-06 12:13 ` Takashi Yano
2019-11-06 14:11 ` Brian Inglis
2019-11-06 15:48 ` Takashi Yano
2019-11-06 17:24 ` Brian Inglis
2019-11-07 2:40 ` Takashi Yano
2019-11-07 8:31 ` Thomas Wolff [this message]
2019-11-07 10:16 ` Takashi Yano
2019-11-07 15:52 ` Brian Inglis
2019-11-07 15:50 ` Brian Inglis
2019-11-07 17:03 ` Brian Inglis
2019-11-08 4:19 ` Katsumi Yamaoka
2019-11-08 13:13 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f24b92f6-4a12-5142-b4c6-330c4613031d@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
--cc=yselkowi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).