From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: dickey@his.com, bug-ncurses@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs difficulties in linux console with ncurses-6.3 caused by kcbt=\E^I.
Date: Sat, 07 May 2022 18:03:45 +0300 [thread overview]
Message-ID: <83levdxu3y.fsf@gnu.org> (raw)
In-Reply-To: <YnaDmhpzoAAo3zsP@ACM> (message from Alan Mackenzie on Sat, 7 May 2022 14:35:06 +0000)
> Date: Sat, 7 May 2022 14:35:06 +0000
> Cc: dickey@his.com, bug-ncurses@gnu.org, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > > Maybe we can write an entry in PROBLEMS and leave it to the user to fix
> > > in her .emacs. Or maybe we can put code in lisp/term/linux.el
> > > ourselves.
>
> > I'm okay with both alternatives, since I have no opinion on what is
> > more important to users of Emacs on the Linux console.
>
> Having thought about it, I think putting
>
> (define-key input-decode-map "\e\t" nil)
>
> into lisp/term/linux.el would be the best thing. It will restore Emacs
> on the Linux console to what it was before the recent ncurses release.
Fine with me.
> > > I don't know how typical I am of Linux console users, but I have my
> > > keymap set up to send a different code for <shift><tab> - namely
> > > "\033[4}\011".
>
> > Perhaps that PROBLEMS entry could suggest that as well, so that users
> > could have the cake and eat it, too.
>
> Here's a first stab at the PROBLEMS entry, under * Runtime problems on
> character terminals>:
Also fine, thanks. But please capitalize "TAB" and "ESC" in the text,
to make them consistent with our notation elsewhere.
next prev parent reply other threads:[~2022-05-07 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 18:18 Emacs difficulties in linux console with ncurses-6.3 caused by kcbt=\E^I Alan Mackenzie
2022-05-06 0:01 ` Thomas Dickey
2022-05-06 11:26 ` Stefan Monnier
2022-05-06 18:49 ` Alan Mackenzie
2022-05-06 19:14 ` Eli Zaretskii
2022-05-07 10:41 ` Alan Mackenzie
2022-05-07 10:45 ` Eli Zaretskii
2022-05-07 14:35 ` Alan Mackenzie
2022-05-07 15:03 ` Eli Zaretskii [this message]
2022-05-07 17:37 ` Alan Mackenzie
2022-05-07 17:55 ` Eli Zaretskii
2022-05-08 23:37 ` Richard Stallman
2022-05-08 12:09 ` Alan Mackenzie
2022-05-08 16:05 ` Thomas Dickey
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83levdxu3y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=bug-ncurses@gnu.org \
--cc=dickey@his.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).