From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47699@debbugs.gnu.org
Subject: bug#47699: [PATCH] Improve completion-list-mode-map
Date: Sun, 11 Apr 2021 08:31:00 +0000 [thread overview]
Message-ID: <3755fe92dc4a9ba66a0b@heytings.org> (raw)
In-Reply-To: <83k0p944s5.fsf@gnu.org>
>>> 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.
>>
>> It's not "just 'n' and 'p'"
>
> The question was why add only those 2.
>
As many as you want could be added. But there are already three ways to
move between completions. < and > are assigned by special-mode-map to
beginning-of-buffer and end-of-buffer. IMO changing the C-{fbnp} commands
is not necessary, given that that moving around with their usual meaning
makes sense.
>> Well, vanilla Emacs defines M-v = switch-to-completions, which opens
>> *Completions* and makes it the current buffer. In a selection-like
>> scenario, it makes sense to switch to the completions buffer where you
>> can freely move around, use isearch, and so forth.
>
> I wonder how many people use this paradigm
>
I do, from time to time. I'd be surprised if I were the only one, as I
remember that it's something I already did during the first days I used
Emacs. When you see a window with lots of information appearing, is it
not natural to enter that window and to move around?
>
> (And how does one switch back without closing the window that shows
> completions?)
>
C-x o. Perhaps it would make sense to bind "o" for this, too. And/or
"Q". WDYT?
next prev parent reply other threads:[~2021-04-11 8: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
2021-04-11 7:58 ` Gregory Heytings
2021-04-11 8:14 ` Eli Zaretskii
2021-04-11 8:31 ` Gregory Heytings [this message]
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
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=3755fe92dc4a9ba66a0b@heytings.org \
--to=gregory@heytings.org \
--cc=47699@debbugs.gnu.org \
--cc=eliz@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).