From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 47699@debbugs.gnu.org
Subject: bug#47699: [PATCH] Improve completion-list-mode-map
Date: Sun, 11 Apr 2021 10:31:03 +0300 [thread overview]
Message-ID: <83o8el46rs.fsf@gnu.org> (raw)
In-Reply-To: <3755fe92dcbf588701ae@heytings.org> (message from Gregory Heytings on Sun, 11 Apr 2021 01:03:56 +0000)
> Date: Sun, 11 Apr 2021 01:03:56 +0000
> From: Gregory Heytings <gregory@heytings.org>
>
> Currently completion-list-mode-map does not give a specific meaning to
> most keys, which means that most keypresses display an error "Buffer is
> read-only #<buffer *Completions*>". I suggest to make it a child of
> special-mode-map, and to bind the "n" and "p" keys to "next-completion"
> and "previous-completion".
Why just 'n' and 'p'? If we want more commands to move between
completions, I could think about several others: <, >, C-f, C-b, C-n,
C-p, Home, End, the arrow keys, etc.
However, these bindings are only available if one makes *Completions*
the current buffer, right? Which rarely if ever happens in
TAB-completion scenarios, right? If so, is that really helpful to
have these additional bindings, and if so, in what use cases?
next prev parent reply other threads:[~2021-04-11 7:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 1:03 bug#47699: [PATCH] Improve completion-list-mode-map Gregory Heytings
2021-04-11 7:24 ` Eli Zaretskii
2021-04-11 7:31 ` Eli Zaretskii [this message]
2021-04-11 7:58 ` Gregory Heytings
2021-04-11 8:14 ` Eli Zaretskii
2021-04-11 8:31 ` Gregory Heytings
2021-04-11 8:34 ` Eli Zaretskii
2021-04-11 10:14 ` Gregory Heytings
2021-04-11 10:40 ` Eli Zaretskii
2021-04-11 10:50 ` Gregory Heytings
2021-04-11 13:31 ` Eli Zaretskii
2021-04-11 18:30 ` Gregory Heytings
2021-04-11 18:46 ` Eli Zaretskii
2021-04-11 19:13 ` Gregory Heytings
2021-04-11 19:37 ` Eli Zaretskii
2021-04-11 20:44 ` Gregory Heytings
2021-04-12 7:24 ` Gregory Heytings
2021-04-11 18:59 ` bug#47699: [External] : " Drew Adams
2021-04-11 19:21 ` Gregory Heytings
2021-04-11 22:33 ` Drew Adams
2021-04-12 6:49 ` Gregory Heytings
2021-04-12 14:50 ` Drew Adams
2021-05-25 4:39 ` Lars Ingebrigtsen
2021-05-25 7:32 ` Gregory Heytings
2021-05-25 7:37 ` Lars Ingebrigtsen
2021-05-25 8:34 ` Gregory Heytings
2021-05-25 8:40 ` Lars Ingebrigtsen
2021-05-25 8:42 ` Gregory Heytings
2021-05-25 12:31 ` Basil L. Contovounesios
2021-05-25 19:22 ` Lars Ingebrigtsen
2021-05-25 19:25 ` Gregory Heytings
2021-05-25 19:27 ` Gregory Heytings
2021-04-11 22:36 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o8el46rs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47699@debbugs.gnu.org \
--cc=gregory@heytings.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.