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: Fri, 06 May 2022 22:14:04 +0300 [thread overview]
Message-ID: <83v8uizd6r.fsf@gnu.org> (raw)
In-Reply-To: <YnVtw1ZkZKTinel9@ACM> (message from Alan Mackenzie on Fri, 6 May 2022 18:49:39 +0000)
> Date: Fri, 6 May 2022 18:49:39 +0000
> Cc: bug-ncurses@gnu.org, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > > Is there perhaps some strategy we could use in Emacs (C code) which would
> > > work around this problem with using ugly ad-hoc code?
>
> > I suppose you could tell Emacs to ignore kcbt (termcap kB) for Linux.
>
> Sorry, I mistyped there. I meant to write "withOUT using ugly ... code".
> Eli Zaretskii, the maintainer of Emacs, is against putting in special
> handling for the linux console's kcbt.
I'm not against that, I'm against doing that in term.c for all the
text-mode terminals. You could, for example, modify input-decode-map
in lisp/term/linux.el, and that would be OK with me, if there's no
better solution for this. Doing that will cause users of Emacs on the
Linux console to lose Backtab and gain M-TAB instead. Personally, I'm
not sure which one is more important, but then I don't use the Linux
console.
next prev parent reply other threads:[~2022-05-06 19:14 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 [this message]
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
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=83v8uizd6r.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).