From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ralf Angeli <angeli@caeruleus.net>
Cc: emacs-devel@gnu.org
Subject: Re: scroll-lock-mode and goal-column
Date: Sun, 29 Jun 2008 15:03:02 -0400 [thread overview]
Message-ID: <jwvskuwcbu8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <g48j7b$71a$1@ger.gmane.org> (Ralf Angeli's message of "Sun, 29 Jun 2008 20:10:51 +0200")
>>> For example if you open the info dir with `C-h i d', activate Scroll
>>> Lock mode, move point down a bit into the introductory blurb, then move
>>> it to column 30 and scroll down line by line with `C-n', point will
>>> sometimes stick to column 0 even though there is text to the right where
>>> it can be moved to.
>>
>> Most likely, `last-command' is not among '(scroll-up scroll-down) so the
>> C code doesn't understand that it should preserve the column position
>> from before the last command.
> Can I make the C code acquainted with the functions of scroll-lock.el?
Not directly, no. Maybe we should add a variable for that.
Othrwise, you can either set this-command to `scroll-up' (since it's
later on mvoes to last-command), or you can let-bind last-command
appropriately around the calls to scroll-up/down.
> If this is what would remedy the situation. I'm a bit confused because
> in scroll-lock.el, the goal column is updated if `last-command' is _not_
> among the scrolling functions.
updated = changed = not preserved.
I understand that since we're talking about preserving something used to
preserve something else, it's not very clear.
>> Sounds very strange, indeed. But Info buffers have funny contents, so
>> maybe you were in column 0 on a big display-property space that spanned
>> columns from 0 to 26?
> There are no display properties, AFAICS.
I'm pretty sure they're there: they're used for alignemnt. But indeed
C-u C-x = has trouble finding them because there are insible spaces
before them.
> And if I open the raw dir file the behavior is even worse, meaning
> point will not jump back into the previous column at all once it got
> stuck to column 0.
I actually much prefer this behavior because it's consistent with the
simple `last-command' problem, so it should be easy to fix.
Stefan
next prev parent reply other threads:[~2008-06-29 19:03 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 [this message]
2008-06-30 20:31 ` Ralf Angeli
2008-07-03 22:10 ` Stefan Monnier
2008-07-20 19:49 ` Ralf Angeli
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvskuwcbu8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.