[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#27191: 26.0.50; Long history items in minibuffer (again)
From: |
Stephen Berman |
Subject: |
bug#27191: 26.0.50; Long history items in minibuffer (again) |
Date: |
Thu, 01 Jun 2017 22:46:15 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
0. emacs -Q
1. C-x C-f
~/foo/bar/very/long/file/name/that/overflows/minibuffer/window/line/when/displayed
<RET>
2. C-x C-f <up>
=> The file name entered in step 1 appears in the minibuffer, with point
on the "w" of "when" (i.e., column 80, the end of the visual line).
If at step 2 instead of <up> you type `M-p', then point is at the end of
the file name in the minibuffer. This is what I expected for <up> too.
The result with <up> is due to the fix for bug#22544. In the bug thread
(http://lists.gnu.org/archive/html/bug-gnu-emacs/2016-02/msg00357.html),
the above problem was noted:
> > Can't we special-case a line that isn't broken into several visual
> > lines, and put the cursor at the end of such lines only? That'd be
> > the best.
>
> The problem here is that like bash and other shells with histories do,
> we need to put the cursor at the end of the previous history element
> so the user can start editing it immediately (usually deleting the chars
> from the end of the logical line). OTOH, a subsequent <UP> should
> continue navigating the history and put the next previous element to the
> minibuffer. But then <UP> can't be used to move between visual lines.
> This is a lose-lose situation, unless we'll find some clever DWIM.
The attached patch isn't particularly clever, but (unless I've
overlooked something) DWIM: it puts point at the end of a history
element longer than window-width, and if such an element is a single
line, the next <up> displays the previous history element. Otherwise,
<up> moves by visual lines (specifically also in multi-line history
elements, including those with lines longer than window-width).
(I wanted to add tests for this, but I haven't been able to figure out
how to emulate minibuffer history navigation non-interactively.)
In GNU Emacs 26.0.50 (build 30, x86_64-pc-linux-gnu, GTK+ Version 3.22.8)
of 2017-05-29 built on rosalinde
Repository revision: c503188f8079ae73d95abd0bce0f53d104b03205
Windowing system distributor 'The X.Org Foundation', version 11.0.11901000
2017-06-01 Stephen Berman <stephen.berman@gmx.net>
Improve navigation through minibuffer history
* lisp/simple.el (previous-line-or-history-element): If the
element extends beyond window-width, go to its logical end,
since that is the natural target for editing history elements.
If it consists of a single line, move by logical lines to hit
beginning-of-buffer immediately and get the previous history
element. Otherwise, move by visual lines.
txtOOrCBXJoGm.txt
Description: previous-line-or-history-element patch
- bug#27191: 26.0.50; Long history items in minibuffer (again),
Stephen Berman <=