all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Wed, 13 Feb 2013 06:02:34 +0200	[thread overview]
Message-ID: <83txpg509x.fsf@gnu.org> (raw)
In-Reply-To: <87ip5xp4yv.fsf@rosalinde.fritz.box>

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 13690@debbugs.gnu.org
> Date: Tue, 12 Feb 2013 23:00:56 +0100
> 
> >   Scroll up to this many lines, to bring point back on screen.
> >   If point moves off-screen, redisplay will scroll by up to
> >   `scroll-conservatively' lines in order to bring point just barely
> >   onto the screen again.        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >   ^^^^^^^^^^^^^^^^^^^^^
> >
> > And this is what happens in the use case you describe.  So I'm unsure
> > why you regard this a bug.  What did you expect instead, and why?
> 
> I expected to see the whole node, or at least as much as possible while
> keeping the target line in view.  I expect this because to all
> appearances Info-up, like the other Info node navigation commands, is a
> jumping (or zapping, warping, i.e. movement in one fell swoop), not a
> scrolling, operation.

scroll-conservatively affects _any_ movement within a buffer, not just
to scrolling commands.  This is by popular demand; you can find my
questions about this and answers by others a year or two ago in the
archives.  E.g., scroll-conservatively affects commands such as
goto-char, even if you move far away in the buffer.

> I see that scroll_conservatively is only used in redisplay_window.
> Does calling Fnarrow_to_region entail calling redisplay_window?

redisplay_window is the workhorse of the display engine in GUI
sessions.  It is called for _any_ kind of redisplay of any window.

Narrowing only requires redisplay if it affects the portion of the
buffer shown in the window.

> > In general, setting scroll-conservatively to 1 tells Emacs that you
> > are prepared to see as little as 1 line of context.
> 
> But again, as a user, I'd expect this only if what I'm doing
> recognizably involves scrolling, which Info-up does not, from the user's
> point of view.

Alas, other users' expectations are different.

> Anyway, if you (and the other Emacs maintainers) agree with my
> arguments, would it be acceptable to add a call to recenter at the end
> of Info-up?

I don't mind.  But if you want that, why do you set
scroll-conservatively to a non-nil value at all?





  reply	other threads:[~2013-02-13  4:02 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 [this message]
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
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=83txpg509x.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.