emacs-devel
[Top][All Lists]
Advanced

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

Re: Emacs difficulties in linux console with ncurses-6.3 caused by kcbt=


From: Alan Mackenzie
Subject: Re: Emacs difficulties in linux console with ncurses-6.3 caused by kcbt=\E^I.
Date: Sat, 7 May 2022 17:37:10 +0000

Hello, Eli.

On Sat, May 07, 2022 at 18:03:45 +0300, Eli Zaretskii wrote:
> > 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.

OK, DONE, it works.  :-)

> > > > 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.

One other little thing: I think this problem counts as "major" or "safe",
so the fix should go onto the release branch, shouldn't it, despite the
upcoming release being nn.2?

-- 
Alan Mackenzie (Nuremberg, Germany).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]