From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 19824@debbugs.gnu.org
Subject: bug#19824: 25.0.50; Support goal column in multi-line minibuffer
Date: Wed, 11 Feb 2015 17:39:18 +0200 [thread overview]
Message-ID: <83iof87909.fsf@gnu.org> (raw)
In-Reply-To: <87mw4l72xw.fsf@mail.linkov.net>
> From: Juri Linkov <juri@linkov.net>
> Cc: 19824@debbugs.gnu.org
> Date: Wed, 11 Feb 2015 01:38:03 +0200
>
> > Why do you use current-column and move-to-column here, instead of
> > using the line-move-visual methods we use by default in any other
> > buffer? Is there some technical problem to use visual-line movement
> > in the minibuffer? If not, I think we should do that for consistency
> > of the user experience.
>
> line-move-visual is still used while moving point inside the minibuffer,
> but when moving to another history element, the whole contents of the
> minibuffer is erased, and new text is inserted, in which the column
> should be positioned correctly.
Right, sorry. So I guess now I don't understand why we try keeping
the horizontal position across history elements. Why not reset the
position to just after the prompt? There's nothing in common between
the history elements, in general.
next prev parent reply other threads:[~2015-02-11 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 0:45 bug#19824: 25.0.50; Support goal column in multi-line minibuffer Juri Linkov
2015-02-10 15:57 ` Eli Zaretskii
2015-02-10 23:38 ` Juri Linkov
2015-02-11 15:39 ` Eli Zaretskii [this message]
2015-02-12 0:54 ` Juri Linkov
2015-03-12 20:27 ` Juri Linkov
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=83iof87909.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19824@debbugs.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).