From: Juri Linkov <juri@linkov.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: 16740@debbugs.gnu.org, 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: Sat, 25 Dec 2021 20:30:42 +0200 [thread overview]
Message-ID: <86h7awmt9p.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkmkByJNyTmqngt5hWbyzrC1B3=XRk=LtmUy66mB5m-5P9w@mail.gmail.com> (Stefan Kangas's message of "Fri, 24 Dec 2021 22:28:13 -0800")
>>>> But we could make C-p/C-n jump to the previous/next history element
>>>> when called from the first/last line, which would combine both
>>>> behaviors. The implementation should be careful to make sure that
>>>> C-p followed by C-n brings you back to the same position (same for
>>>> C-n followed by C-p), otherwise such behavior can get irritating
>>>> when you accidentally hit C-p from the first line.
>>> Just makes the user interaction more confusing.
>>
>> I wouldn't like it, indeed, and I don't think it would make sense as
>> a default. But an option could provide that behavior.
>
> No one has implemented this in 8 years, so I'm leaning towards closing
> this feature request. If anyone thinks it should remain open, please
> speak up. Thanks.
This feature was implemented in the same year when requested.
next prev parent reply other threads:[~2021-12-25 18:30 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 [this message]
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
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=86h7awmt9p.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=16740@debbugs.gnu.org \
--cc=eda@waniasset.com \
--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).