unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>,  Eli Zaretskii <eliz@gnu.org>,
	 Emacs developers <emacs-devel@gnu.org>
Subject: Re: What's happened to M-<tab> `completion-at-point'?
Date: Wed, 04 May 2022 16:16:53 -0400	[thread overview]
Message-ID: <jwv35hpvyzn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAP_d_8Wdj0Z+N-tSPR2-kZmVUuGMHB-JnG76ns9NG_vG6FVt=A@mail.gmail.com> (Yuri Khan's message of "Thu, 5 May 2022 02:47:41 +0700")

>     $ infocmp linux
>     #       Reconstructed via infocmp from file: /lib/terminfo/l/linux
>     linux|Linux console,
>             am, bce, ccc, eo, mir, msgr, xenl, xon,
>             …
>             kb2=\E[G, kbs=^?, kcbt=\E^I, kcub1=\E[D, kcud1=\E[B,
>             …
>
> In other words, the terminfo database declares a capability named
> ‘kcbt’ with the value ESC TAB. And ‘man terminfo’ says ‘kcbt’ is the
> backtab key.

Indeed.  And then Emacs's C code builds a default `input-decode-map`
which maps ESC TAB to `backtab`.

This is a weird choice, tho (on their side).
AFAIK the `backtab` is usually used for `S-tab` rather than `M-tab`.

What do you get if you hit the TAB key together with the Shift modifier?
Does Emacs also receive the ESC TAB byte sequence in that (and then maps
it back (correctly this time) to `backtab`)?

You should definitely report this as a problem.


        Stefan




  reply	other threads:[~2022-05-04 20:16 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
2022-05-04 19:47             ` Yuri Khan
2022-05-04 20:16               ` Stefan Monnier [this message]
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=jwv35hpvyzn.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@gmail.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.
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).