unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: What's happened to M-<tab> `completion-at-point'?
Date: Wed, 4 May 2022 19:10:12 +0000	[thread overview]
Message-ID: <YnLPlPFDfEWBwvRH@ACM> (raw)
In-Reply-To: <83r1592km7.fsf@gnu.org>

Hello, Eli.

On Wed, May 04, 2022 at 21:55:28 +0300, Eli Zaretskii wrote:
> > Date: Wed, 4 May 2022 18:13:30 +0000
> > Cc: emacs-devel@gnu.org
> > From: Alan Mackenzie <acm@muc.de>

> > > >     [backtab] is undefined

> > > And what does "C-h l" show after that?

> > If I first press ESC TAB and C-h l, followed by C-M-i and C-h l, I get
> > this:

> >  ESC TAB ;; nil
> >  C-h l   ;; view-lossage
> >  ESC TAB ;; nil
> >  C-h l   ;; view-lossage

> So who is converting this to <backtab>?

I don't know, yet.

> > I think I've found the problem.  A new version of ncurses was
> > installed on my machine on 2022-05-01.  It contains a version of
> > terminfo, specifically /etc/terminfo/l/linux.

> > The new version is ncurses-6.3_p20211106.  The old version was
> > ncurses-6.2_p20210619.

> > So, possibly we need to amend Emacs (? src/term.c) to work properly on
> > this version of the Linux console.

> Amend how?  I still don't understand where did <backtab> come from.
> If you do understand, can you describe that?

I don't understand it either, yet.  To be sure that terminfo is the
problem, I'll have to do something like reinstalling the old version of
ncurses, and seeing the problem is no longer there.

But in src/term.c L1258 appears:

      {"kB", "backtab"},    /* terminfo */

The "kB" is a terminfo code for back-tab, and the "backtab" might
somehow be the source for the "[backtab] is undefined" error message.

I'm still at an early stage of understanding this bug.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2022-05-04 19:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 21:06 What's happened to M-<tab> `completion-at-point'? Alan Mackenzie
2022-05-04  6:32 ` Eli Zaretskii
2022-05-04 16:34   ` Alan Mackenzie
2022-05-04 16:40     ` Eli Zaretskii
2022-05-04 18:13       ` Alan Mackenzie
2022-05-04 18:55         ` Eli Zaretskii
2022-05-04 19:10           ` Alan Mackenzie [this message]
2022-05-04 19:47             ` Yuri Khan
2022-05-04 20:16               ` Stefan Monnier
2022-05-04 20:31                 ` Yuri Khan
2022-05-04 20:50                   ` Stefan Monnier
2022-05-04 21:07                   ` Alan Mackenzie
2022-05-05  5:03                     ` tomas
2022-05-05  6:20                     ` Eli Zaretskii
2022-05-05 16:57                       ` Alan Mackenzie
2022-05-05 17:28                         ` Eli Zaretskii
2022-05-06 23:19                           ` Richard Stallman
2022-05-07 11:03                             ` Alan Mackenzie
2022-05-08 23:35                               ` Richard Stallman
2022-05-04 20:35               ` Alan Mackenzie
2022-05-04 19:16           ` Tassilo Horn
2022-05-04 19:39             ` Eli Zaretskii
2022-05-04 19:45               ` Tassilo Horn
2022-05-04 19:57               ` Andreas Schwab
2022-05-04  6:33 ` Lars Ingebrigtsen
2022-05-04 16:26   ` Alan Mackenzie

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=YnLPlPFDfEWBwvRH@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --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).