From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 13690@debbugs.gnu.org
Subject: bug#13690: 24.3.50; scroll-conservatively and Info-up
Date: Thu, 14 Feb 2013 07:12:38 +0200 [thread overview]
Message-ID: <83621v4gxl.fsf@gnu.org> (raw)
In-Reply-To: <871ucj7qgp.fsf@rosalinde.fritz.box>
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 13690@debbugs.gnu.org
> Date: Thu, 14 Feb 2013 00:18:30 +0100
>
> > . scroll-conservatively being non-nil
>
> I think you mean non-zero, since only integer values are admissible.
> But when scroll-conservatively is zero, recentering happens anyway, so I
> don't see the point of adding this condition. Or is there a problem is
> if recentering happens twice (once directly from the display engine and
> once by explicitly calling recenter)? I don't notice any problem.
Why recenter twice? It's a waste of cycles.
> > . perhaps also scroll-margin being zero, because otherwise you get
> > several lines of context before point
>
> I tested scroll-margin and found no difference in the behavior of Info-up
> whether it is zero or non-zero; do you see something different?
Do you have the latest trunk? If so, you should see a difference:
when scroll-margin is N, typing 'u' puts the line with cursor N+1
lines from the top.
next prev parent reply other threads:[~2013-02-14 5:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 23:24 bug#13690: 24.3.50; scroll-conservatively and Info-up Stephen Berman
2013-02-12 16:14 ` Eli Zaretskii
2013-02-12 22:00 ` Stephen Berman
2013-02-13 4:02 ` Eli Zaretskii
2013-02-13 13:36 ` Stephen Berman
2013-02-13 17:41 ` Eli Zaretskii
2013-02-13 19:02 ` Dmitry Gutov
2013-02-13 21:48 ` Eli Zaretskii
2013-02-14 1:51 ` Dmitry Gutov
2013-02-14 5:16 ` Eli Zaretskii
2013-02-13 23:18 ` Stephen Berman
2013-02-14 5:12 ` Eli Zaretskii [this message]
2013-02-14 11:32 ` Stephen Berman
2020-08-25 11:31 ` Lars Ingebrigtsen
2020-08-25 18:02 ` Stephen Berman
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=83621v4gxl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13690@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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.