This appears to be a minimal way to recreate the problem. Try this.
env -i PATH=$PATH HOME=$HOME TERM=$TERM MANWIDTH=80 /usr/bin/emacs -Q -nw
Then I will repeat the recreation instructions.
emacs -Q # no configuration
M-x man RET # look at a man page
ls RET # something a few pages long
C-x o # go there
M-> # jump to the bottom
C-x o # return to original buffer
This recreates the problem on an different Sid Unstable system.
And avoiding MANWIDTH avoids the problem.
env -i PATH=$PATH HOME=$HOME TERM=$TERM /usr/bin/emacs -Q -nw
Or just avoiding MANWIDTH only is enough:
env -u MANWIDTH /usr/bin/emacs -Q -nw
And of course as we know:
man man
MANWIDTH
If $MANWIDTH is set, its value is used as the line length for
which manual pages should be formatted. If it is not set,
manual pages will be formatted with a line length appropriate to
the current terminal (using the value of $COLUMNS, and ioctl(2)
if available, or falling back to 80 characters if neither is
available). Cat pages will only be saved when the default
formatting can be used, that is when the terminal line length is
between 66 and 80 characters.
So why does MANWIDTH trigger this problem? And not in the previous
version? Hmm...
Bob
