unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "16740@debbugs.gnu.org" <16740@debbugs.gnu.org>,
	Ed Avis <eda@waniasset.com>
Subject: bug#16740: 24.2; Please allow C-p and C-n in minibuffer
Date: Thu, 13 Feb 2014 15:53:06 +0100	[thread overview]
Message-ID: <CAH8Pv0hOW=EVF6=8JHMq5M+wxWag94hTnPQkufZ4dz9Hovn6cw@mail.gmail.com> (raw)
In-Reply-To: <266758c2-0b11-4526-854e-bb655805478a@default>

On Thu, Feb 13, 2014 at 3:44 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> 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.
>
> In particular, in some cases it might not be obvious to a user
> that s?he is at the last line, or s?he might not notice that fact.
>
> Or s?he might intentionally hold down `C-n' or `C-p' to get to the
> end or start without counting or looking after each keypress.
>
> YAGNI.

That's exactly what I think.

I've just filed a request to the Bash developers (bug-bash@gnu.org)
about this [1].  Let's see what they say...


--- footnotes ---

[1] But it doesn't appear yet at
http://lists.gnu.org/archive/html/bug-bash/2014-02/index.html

-- 
Dani Moncayo





  reply	other threads:[~2014-02-13 14:53 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 [this message]
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
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='CAH8Pv0hOW=EVF6=8JHMq5M+wxWag94hTnPQkufZ4dz9Hovn6cw@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=16740@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eda@waniasset.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).