From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 736@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: Re: bug#736: C-l interacts badly with scroll-conservatively
Date: Sun, 17 Aug 2008 15:12:04 -0400 [thread overview]
Message-ID: <87tzdj8ni3.fsf@cyd.mit.edu> (raw)
In-Reply-To: <00da01c90083$58563410$0200a8c0@us.oracle.com> (Drew Adams's message of "Sun, 17 Aug 2008 09:07:26 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> emacs -q
>> M-: (setq scroll-conservatively 100) RET
>> C-h n
>> C-v
>> C-l
>> C-l
>> C-l
>>
>> The repeated C-l's don't move to the top or bottom of the
>> window, unlike the usual behavior (new to Emacs 23) of
>> recenter-top-bottom.
>
> Maybe I'm misunderstanding the bug report, but by design
> `scroll-conservatively' modifies the behavior of
> `recenter-top-bottom'. As the doc string says:
>
> "Top and bottom destinations are actually
> `scroll-conservatively' lines from true window top
> and bottom."
That's true; I didn't see that.
But why does recenter-top-bottom use scroll-conservatively? AFAICT,
people often use a large nonzero number for scroll-conservatively so
that when point is at the bottom of the window, C-n scrolls down by one
and keeps the cursor at the bottom; and similarly, if point is at the
top of the window, C-p keeps the cursor at the top. It doesn't make
sense to make scroll-conservatively affect C-l.
I think we should use scroll-margin for this purpose, rather than
scroll-conservatively.
What do people think?
next parent reply other threads:[~2008-08-17 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873al3u0ao.fsf@stupidchicken.com>
[not found] ` <00da01c90083$58563410$0200a8c0@us.oracle.com>
2008-08-17 19:12 ` Chong Yidong [this message]
2008-08-17 20:14 ` bug#736: C-l interacts badly with scroll-conservatively Drew Adams
2008-08-18 3:47 ` Chong Yidong
[not found] ` <87tzdj8ni3.fsf__43536.6355035969$1219001342$gmane$org@cyd.mit.edu>
2008-08-17 19:58 ` Dan Nicolaescu
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=87tzdj8ni3.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=736@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
--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).