From: Ed Avis <eda@waniasset.com>
To: 'Dani Moncayo' <dmoncayo@gmail.com>
Cc: "16740@debbugs.gnu.org" <16740@debbugs.gnu.org>
Subject: bug#16740: 24.2; Please allow C-p and C-n in minibuffer
Date: Thu, 13 Feb 2014 11:32:09 +0000 [thread overview]
Message-ID: <7E039918541B4C4183BFDB8F015C743065AD34@WCL-EXCH02.wcl.local> (raw)
In-Reply-To: <CAH8Pv0gQScWs4C5_SzqEoAp-mmx2NuL9i+jpQHQdFEsh_+ZSdg@mail.gmail.com>
>IOW, I'd rather change bash behavior to match the Emacs one, instead
>of the other way around.
I expected that to be the response. And no doubt on the bash mailing
list it would be the opposite. I will ask them though. To my mind the
best resolution is for both programs to accept both keybindings.
I agree that sometimes it happens that the minibuffer contains more than
one line of text. But never with find-file. I don't think I've ever wanted to
create or open a filename with embedded newline using Emacs.
As a compromise could Emacs make C-p do previous-line if the minibuffer
contains more than one line, and previous-history-element otherwise?
--
Ed Avis <eda@waniasset.com>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
next prev parent reply other threads:[~2014-02-13 11:32 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 [this message]
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
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=7E039918541B4C4183BFDB8F015C743065AD34@WCL-EXCH02.wcl.local \
--to=eda@waniasset.com \
--cc=16740@debbugs.gnu.org \
--cc=dmoncayo@gmail.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).