From: Ralf Angeli <angeli@caeruleus.net>
To: emacs-devel@gnu.org
Subject: Re: scroll-lock-mode and goal-column
Date: Sun, 20 Jul 2008 21:49:43 +0200 [thread overview]
Message-ID: <g604so$7i1$1@ger.gmane.org> (raw)
In-Reply-To: jwvabgyfwp4.fsf-monnier+emacs@gnu.org
* Stefan Monnier (2008-07-04) writes:
>> However, I'd prefer the column to be preserved. Since this behavior of
>> `forward-line' is by design, I'm not sure if we can get rid of the
>> manual preservation of the goal column.
>
> How 'bout using next-line?
Not much better. It sometimes happens that when the last command was
`scroll-up' and the next one is `next-line', i.e. the bottom of the
buffer is reached, the goal column will not be preserved if point is not
at the original goal column but e.g. at the start of the line. So it
looks as if `next-line' is unaware of the goal column being in effect
for `scroll-up'.
There are other funny things going on sometimes, though they don't seem
to be related to `next-line' because they happen with `forward-line' as
well. Start Emacs with `emacs -Q', type `C-h i d', enable Scroll Lock
mode, type `M-<' to put point at the start of the buffer, scroll up with
`C-n' till point is just below the "* Menu" line, then scroll down with
`C-p' till point reaches the start of the buffer (the line with
"(dir)Top". Once this happens, point jumps back down to the first
content line after "* Menu" which is "* Info..." here. (This is with
the patched version of scroll-mode.el. Not sure if this happens with
the unpatched one as well.)
--
Ralf
prev parent reply other threads:[~2008-07-20 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 15:49 scroll-lock-mode and goal-column Stefan Monnier
2008-06-13 16:05 ` David Kastrup
2008-06-13 17:50 ` Stefan Monnier
2008-06-29 14:33 ` Ralf Angeli
2008-06-29 17:51 ` Stefan Monnier
2008-06-29 18:10 ` Ralf Angeli
2008-06-29 19:03 ` Stefan Monnier
2008-06-30 20:31 ` Ralf Angeli
2008-07-03 22:10 ` Stefan Monnier
2008-07-20 19:49 ` Ralf Angeli [this message]
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='g604so$7i1$1@ger.gmane.org' \
--to=angeli@caeruleus.net \
--cc=emacs-devel@gnu.org \
/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).