* bug#27941: 25.2; next-line-add-newlines and minibuffer
@ 2017-08-04 6:14 Daniel Gildea
2017-08-04 7:59 ` Eli Zaretskii
0 siblings, 1 reply; 2+ messages in thread
From: Daniel Gildea @ 2017-08-04 6:14 UTC (permalink / raw)
To: 27941
If you
(setq next-line-add-newlines t)
then pressing <down> in the minibuffer always adds a newline,
rather than moving to the next history item.
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#27941: 25.2; next-line-add-newlines and minibuffer
2017-08-04 6:14 bug#27941: 25.2; next-line-add-newlines and minibuffer Daniel Gildea
@ 2017-08-04 7:59 ` Eli Zaretskii
0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2017-08-04 7:59 UTC (permalink / raw)
To: Daniel Gildea; +Cc: 27941
> From: Daniel Gildea <gildea@cs.rochester.edu>
> Date: Fri, 04 Aug 2017 02:14:00 -0400
>
> If you
>
> (setq next-line-add-newlines t)
>
> then pressing <down> in the minibuffer always adds a newline,
> rather than moving to the next history item.
I think that's the intended behavior; you need to type M-n to get the
next history element.
"C-h k <down>" says this key moves cursor either down or to the next
history element. The minibuffer can be more than one line high.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-08-04 7:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-04 6:14 bug#27941: 25.2; next-line-add-newlines and minibuffer Daniel Gildea
2017-08-04 7:59 ` Eli Zaretskii
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).