From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Minibuffer bindings.
Date: Sun, 2 Oct 2005 07:20:29 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICEEPHCMAA.drew.adams@oracle.com> (raw)
In-Reply-To: <878xxcdxe4.fsf@t-lrde.epita.fr>
I was wondering why C-p and C-n are not binded like <up> and <down>
in the minibuffer.
I agree. In fact, as I wrote on 9/01 (RE: make `occur' use word at point as
default), I was thinking this was already the case (RMS corrected me).
Although my main point was that we could redefine some of the redundant
minibuffer bindings that are now equivalent to down/up, I assumed that
C-n/C-p were among these, and I specifically did not suggest that we
redefine those bindings. It's good to have down = C-n and up = C-p, IMO.
next prev parent reply other threads:[~2005-10-02 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 10:30 Minibuffer bindings Michael Cadilhac
2005-10-02 14:20 ` Drew Adams [this message]
2005-10-02 20:31 ` Richard M. Stallman
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=DNEMKBNJBGPAOPIJOOICEEPHCMAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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).