From: Dani Moncayo <dmoncayo@gmail.com>
To: Ed Avis <eda@waniasset.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 12:41:16 +0100 [thread overview]
Message-ID: <CAH8Pv0jknV-V=w7d3wyQpTdzNnJpVZAS2eQu1=aWc6L-_ehSpQ@mail.gmail.com> (raw)
In-Reply-To: <7E039918541B4C4183BFDB8F015C743065AD34@WCL-EXCH02.wcl.local>
On Thu, Feb 13, 2014 at 12:32 PM, Ed Avis <eda@waniasset.com> wrote:
>>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 think that having different meanings for C-p/C-n and M-p/M-n would
give a richer user interface, also in bash, because it would allow, on
one hand to browse the command history (with M-p/M-n) while at the
same time move vertically within a single multiline command (with
C-p/C-n). Just like in Emacs. IMO that would be TRT.
--
Dani Moncayo
next prev parent reply other threads:[~2014-02-13 11:41 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8Pv0jknV-V=w7d3wyQpTdzNnJpVZAS2eQu1=aWc6L-_ehSpQ@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=16740@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.