unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: UP and DOWN with multi-line minibuffer history
Date: Sun, 13 Dec 2015 17:24:15 +0200	[thread overview]
Message-ID: <83lh8y5q3k.fsf@gnu.org> (raw)
In-Reply-To: <87y4czz63l.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 13 Dec 2015 01:20:49 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: emacs-devel@gnu.org
> Date: Sun, 13 Dec 2015 01:20:49 +0200
> 
> > I think it would be more consistent, including with how
> > line-move-visual behaves in normal buffers, if UP ended up in the last
> > line of the previous item.  WDYT?
> 
> The initial implementation of this feature was like you described above.
> But later I received complaints off-list that convinced me to open
> bug#19824 with better implementation to address the inconvenience of
> navigating through the multi-line minibuffer history: for backward-compatible
> behavior we need every UP in the sequence move to a previous history item.
> This can be achieved when UP places the cursor at the top line of a
> multi-line history item, ready for going to the next previous item with
> successive UP.

Sorry, I don't understand why supporting goal-column must have this
side effect.  In a normal buffer, we do support goal-column (in the
visual-line sense), and still we don't jump to the firs screen line of
a long logical line.  Why should the minibuffer behave differently?

I guess the description in bug#19824 lacks some crucial details,
because I simply don't see why preserving the column should force to
jump to the first screen line of the previous history item.  Can you
explain?  Are you interpreting the goal-column in physical, rather
than visual, sense?



  reply	other threads:[~2015-12-13 15:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 14:19 UP and DOWN with multi-line minibuffer history Eli Zaretskii
2015-12-12 15:03 ` Dmitry Gutov
2015-12-12 23:04   ` John Wiegley
2015-12-12 22:47 ` Eric Hanchrow
2015-12-12 23:20 ` Juri Linkov
2015-12-13 15:24   ` Eli Zaretskii [this message]
2015-12-14  0:07     ` Juri Linkov
2015-12-14  3:39       ` Eli Zaretskii
2015-12-14 23:45         ` Juri Linkov
2015-12-15  3:37           ` Eli Zaretskii
2015-12-16  0:32             ` Juri Linkov
2015-12-16  1:33               ` Dmitry Gutov
2015-12-17  0:45                 ` Juri Linkov
2015-12-16  2:02               ` Yuri Khan
2015-12-16  6:29                 ` Drew Adams
2015-12-17  0:49                 ` Juri Linkov
2015-12-15  3:43         ` Dmitry Gutov
2015-12-15 15:45           ` Eli Zaretskii
2015-12-14  9:25     ` David Kastrup
2015-12-14 16:00       ` Eli Zaretskii
2015-12-14 16:41         ` David Kastrup
2015-12-14 17:03           ` Eli Zaretskii
     [not found] <CABr8ebZDmnsCKyBnzU3sSDHefJ2_3uC4Omwg=N4qQ8h80vTxpw@mail.gmail.com>
2015-12-13  3:31 ` Eli Zaretskii
2015-12-13  5:38   ` Anders Lindgren

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=83lh8y5q3k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).