From: Po Lu <luangruo@yahoo.com>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Juri Linkov <juri@linkov.net>,
Daniel Mendler <mail@daniel-mendler.de>,
Ergus <spacibba@aol.com>, Drew Adams <drew.adams@oracle.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: Completions and history
Date: Wed, 13 Apr 2022 20:12:27 +0800 [thread overview]
Message-ID: <87lew9tc5w.fsf@yahoo.com> (raw)
In-Reply-To: <87ee215h1j.fsf@gmail.com> (Augusto Stoffel's message of "Wed, 13 Apr 2022 14:00:56 +0200")
Augusto Stoffel <arstoffel@gmail.com> writes:
> Discussing default keybindings tends to be rather unfruitful, but still:
> unless I'm missing something, `M-r' (previous-matching-history-element)
> is strictly less powerful than `C-M-r' (isearch-backward-regexp).
> History completion is quite handy and would be a better use for `M-r' in
> my opinion.
M-r is much easier to type than C-M-r, so if anything it should be the
other way around.
Or even better we could have M-S-r and M-S-s bound to history
completion.
next prev parent reply other threads:[~2022-04-13 12:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411112901.kv3lsyvx6yxwjbph.ref@Ergus>
2022-04-11 11:29 ` Completions and history Ergus
2022-04-11 16:56 ` Juri Linkov
2022-04-11 17:40 ` Ergus
2022-04-12 16:20 ` Juri Linkov
2022-04-12 16:53 ` Ergus
2022-04-12 16:59 ` Ergus
2022-04-12 17:12 ` Juri Linkov
2022-04-12 17:35 ` Ergus
2022-04-12 18:10 ` Juri Linkov
2022-04-12 17:24 ` Augusto Stoffel
2022-04-12 17:50 ` [External] : " Drew Adams
2022-04-12 18:05 ` Juri Linkov
2022-04-12 19:49 ` Drew Adams
2022-04-13 7:50 ` Juri Linkov
2022-04-13 12:00 ` Augusto Stoffel
2022-04-13 12:12 ` Po Lu [this message]
2022-04-14 2:56 ` Richard Stallman
2022-04-13 16:40 ` Drew Adams
2022-04-13 17:58 ` Juri Linkov
2022-04-13 17:57 ` Juri Linkov
2022-04-13 15:49 ` Drew Adams
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=87lew9tc5w.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=arstoffel@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=mail@daniel-mendler.de \
--cc=spacibba@aol.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 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.