From: Ed Avis <eda@waniasset.com>
To: 'Stefan Monnier' <monnier@iro.umontreal.ca>
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 13:59:56 +0000 [thread overview]
Message-ID: <7E039918541B4C4183BFDB8F015C743065AF26@WCL-EXCH02.wcl.local> (raw)
In-Reply-To: <jwvy51f6sfj.fsf-monnier+emacsbugs@gnu.org>
Stefan Monnier wrote:
>But we could make C-p/C-n jump to the previous/next history element
>when called from the first/last line,
That would work. So where it currently prints 'Beginning of buffer' it
would instead go to the previous item in the history. But where C-p
currently does something, its behaviour would not change.
You are right that the minibuffer can contain multiple lines just because
the filename is long enough. I was still thinking in terms of the old days
when next-line went to the next logical line, not the next physical line
on screen.
--
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 13:59 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 [this message]
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=7E039918541B4C4183BFDB8F015C743065AF26@WCL-EXCH02.wcl.local \
--to=eda@waniasset.com \
--cc=16740@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.