From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16740@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Ed Avis <eda@waniasset.com>
Subject: bug#16740: 24.2; Please allow C-p and C-n in minibuffer
Date: Sun, 26 Dec 2021 19:28:23 +0200 [thread overview]
Message-ID: <86r19zz6vc.fsf@mail.linkov.net> (raw)
In-Reply-To: <87o853y3z9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 26 Dec 2021 12:56:10 +0100")
>> Before closing, we need to decide whether to bind C-p and C-n
>> to the same commands that were bound in 2014 to [up] and [down],
>> i.e. whether to apply such patch:
> [...]
>> (define-key map [down] 'next-line-or-history-element)
>> + (define-key map "\C-n" 'next-line-or-history-element)
>
> If I remember correctly, I think the idea was to have a way for the user
> to skip the nice magical DWIM stuff that's on up/down, so C-n/C-p was
> left alone on purpose. And I think that's still the right decision.
This was my recollection too. So if no one has new arguments
to change this decision, this request could be closed.
next prev parent reply other threads:[~2021-12-26 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 11:04 bug#16740: 24.2; Please allow C-p and C-n in minibuffer Ed Avis
2014-02-13 11:22 ` Andreas Schwab
2014-02-13 11:26 ` Dani Moncayo
2014-02-13 11:32 ` Ed Avis
2014-02-13 11:41 ` Dani Moncayo
2014-02-13 13:46 ` Stefan Monnier
2014-02-13 13:59 ` Ed Avis
2014-02-13 14:44 ` Drew Adams
2014-02-13 14:53 ` Dani Moncayo
2014-02-13 16:03 ` Stefan Monnier
2021-12-25 6:28 ` Stefan Kangas
2021-12-25 9:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-25 18:30 ` Juri Linkov
2021-12-25 21:53 ` Stefan Kangas
2021-12-26 7:41 ` Juri Linkov
2021-12-26 11:56 ` Lars Ingebrigtsen
2021-12-26 17:28 ` Juri Linkov [this message]
2021-12-29 3:05 ` Stefan Kangas
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=86r19zz6vc.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=16740@debbugs.gnu.org \
--cc=eda@waniasset.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).