From: "André A. Gomes" <andremegafone@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: History completion
Date: Thu, 09 Dec 2021 22:52:52 +0000 [thread overview]
Message-ID: <87ee6lo0fv.fsf@gmail.com> (raw)
In-Reply-To: <861r2lspqo.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 09 Dec 2021 19:12:49 +0200")
Juri Linkov <juri@linkov.net> writes:
>> Another suggestion would be to follow comint mode's bindings: C-c M-r/s.
>> But, unlike comint's case, C-c M-p/n aren't being used so it's also an
>> option.
>
> Two key presses is not the most convenient to browse completions.
> Horizontal Icomplete uses ‘C-,’ and ‘C-.’.
Maybe I got something wrong, but I thought we're discussing commands
that were similar `next-matching-history-element' and
`previous-matching-history-element' (bound to M-s and M-r).
The ones I thought we're referring to would match an element based on a
given prefix (akin to comint-previous-matching-input-from-input and
friends).
IMO, it would make sense to have a symmetric behaviour in comint mode
and the minibuffer. Some will argue that I can just type "^" right
after I call M-r/s in the minibuffer. Well...
In that vein, I suggested C-c M-r/s for the hypothetical
`previous-matching-history-element-from-input' and
`next-matching-history-element-from-input'.
--
André A. Gomes
"Free Thought, Free World"
next prev parent reply other threads:[~2021-12-09 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 18:54 History completion Juri Linkov
2021-12-08 20:02 ` André A. Gomes
2021-12-09 6:05 ` Manuel Uberti
2021-12-09 17:12 ` Juri Linkov
2021-12-09 22:52 ` André A. Gomes [this message]
2021-12-08 20:52 ` [External] : " Drew Adams
2021-12-09 8:30 ` Daniel Fleischer
2021-12-09 17:16 ` Juri Linkov
2021-12-09 18:13 ` [External] : " Drew Adams
2021-12-09 7:51 ` Manuel Uberti
2021-12-09 17:18 ` Juri Linkov
2021-12-09 17:40 ` Manuel Uberti
2022-06-09 7:01 ` 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=87ee6lo0fv.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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).