unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: yuri.v.khan@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: What's happened to M-<tab> `completion-at-point'?
Date: Thu, 05 May 2022 09:20:17 +0300	[thread overview]
Message-ID: <83fslo33ha.fsf@gnu.org> (raw)
In-Reply-To: <YnLq+AMDPW6UCaOL@ACM> (message from Alan Mackenzie on Wed, 4 May 2022 21:07:04 +0000)

> Date: Wed, 4 May 2022 21:07:04 +0000
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>,
>   Emacs developers <emacs-devel@gnu.org>
> From: Alan Mackenzie <acm@muc.de>
> 
> Maybe the best thing we can do in Emacs is to remove that entry for "kB"
> in src/term.c.  That would prevent Emacs recognising <shift>TAB on all
> these misconfigured keyboards.  I think that is a lesser evil than
> failing to recognise <meta>TAB.

This doesn't sound like a good idea to me.  Emacs shouldn't try
second-guessing the user's keyboard configuration, it isn't in our
mandate.

If the terminfo database you have doesn't do what you want, why can't
you modify it?  The tools to do that are available, and aren't part of
Emacs.  (We could include the instructions for making such a change in
PROBLEMS, if this is a common issue.)  Of course, the best solution
would be if the distro changes the terminfo database.



  parent reply	other threads:[~2022-05-05  6:20 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
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 [this message]
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=83fslo33ha.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).