all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Losing minibuffer input
Date: Tue, 18 Nov 2014 23:40:34 +0200	[thread overview]
Message-ID: <87zjbokx0t.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvbnoareiv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 13 Nov 2014 16:14:12 -0500")

>> The fix is simple: allow up-down arrow keys to have their usual behavior
>> and only on hitting the beginning/end of the minibuffer move to the next
>> or previous history item, thus making navigation more smooth and continuous.
>
> Sounds good to me (oddly enough, while I use up/down/left/right
> frequently in normal buffers, it seems that I never use up/down in the
> minibuffer (I use M-p/M-n to go through the history and C-p/C-n for
> in-buffer movement)).

There is another convenience in other programs that we could use.
Most programs allow typing S-RET to insert a newline in their analogue
of the minibuffer.  Even though it might be unavailable on some terminals,
what do you think about adding it for GUI sessions?



  reply	other threads:[~2014-11-18 21:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-09 17:57 Losing minibuffer input Juri Linkov
2014-11-09 18:17 ` Óscar Fuentes
2014-11-09 18:33   ` Juri Linkov
2014-11-09 18:53     ` Drew Adams
2014-11-13 20:23       ` Juri Linkov
2014-11-14 11:16         ` Dmitry Gutov
2014-11-18 21:36           ` Juri Linkov
2014-11-20 22:38             ` Johan Bockgård
2014-11-20 23:58               ` Juri Linkov
2014-11-21  7:37               ` previous-line, next-line at the first, last lines of the buffer Ivan Shmakov
2014-11-21  8:49                 ` Eli Zaretskii
2014-11-21  9:12                   ` Ivan Shmakov
2014-11-30 13:31                     ` Stefan Monnier
2014-11-09 18:52   ` Losing minibuffer input Drew Adams
2014-11-09 18:52 ` Drew Adams
2014-11-13 21:14 ` Stefan Monnier
2014-11-18 21:40   ` Juri Linkov [this message]
2014-11-19  4:22     ` Drew Adams
2014-11-20 23:52       ` Juri Linkov
2014-11-21  0:24         ` Drew Adams
2014-11-20 16:35     ` Daniel Colascione
2014-11-20 23:55       ` Juri Linkov
2014-12-05  0:38       ` Multi-line input (was: Losing minibuffer input) Juri Linkov
2014-12-05  2:03         ` Multi-line input Stefan Monnier
2014-12-05 16:24           ` Yuri Khan
2014-12-05 18:45             ` Stefan Monnier
2014-12-05 22:43           ` Richard Stallman
     [not found]           ` <<E1Xx1bN-0007f9-Ut@fencepost.gnu.org>
2014-12-05 23:02             ` Drew Adams
2014-12-06 12:06               ` Richard Stallman
     [not found]             ` <<94e0230f-c396-4266-8ada-9816d8118946@default>
     [not found]               ` <<E1XxE8T-0002OE-U9@fencepost.gnu.org>
2014-12-06 16:44                 ` Drew Adams
2014-12-05 23:43           ` Juri Linkov
2014-12-06  3:20             ` Drew Adams

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=87zjbokx0t.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@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.