bug#42862: 28.0.50; {previous,next}-line-or-history-element ignores line-move-visual

[Michael Welsh Duggan]

Run:

    emacs -Q --exec "(setq-default line-move-visual nil)"

Visit a file in a directory where the directory name is not long enough
to wrap in the minibuffer, but the filename is long enough that,
appended to that directory, the minibuffer would wrap.

Example:
/tmp/this-is-a-very-long-directory-name-that-will-not-wrap/but-this-file-name-will-make-it-wrap

Specifically, visit this file such that it will enter the minibuffer
history for file visiting.

Type `C-h f'.  When you hit the up-arrow (not `M-p'!) you should end up
with the very long file name in your minibuffer, with the point at the
end of the first visual line.  This is intended behavior so that
multiple invocations of up-arrow will scroll through the history instead
of moving up a visible line.  (See comments in
`{previous,next}-line-or-history-element' to that effect.)

It is my belief that if `line-move-visual' is nil,
`previous-line-or-history-element' should move to the end of the first
logical line instead of the first visual line.  (Similarly for
`next-line-or-history-element'.)


In GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 
1.16.0)
 of 2020-07-12 built on maru2
Repository revision: 0d5e17b549a223e21ae893c455c0f00753af251c
Repository branch: md5i
Windowing system distributor 'The X.Org Foundation', version 11.0.12008000
System Description: Debian GNU/Linux bullseye/sid

Configured using:
 'configure --with-modules --without-toolkit-scroll-bars
 --with-x-toolkit=lucid --with-wide-int --with-gameuser=:staff
 'CFLAGS=-Og -ggdb3''

Configured features:
XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY
INOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF
ZLIB LUCID X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER LCMS2

Important settings:
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix


-- 
Michael Welsh Duggan
(md5i@md5i.com)