From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Scrolling change
Date: Mon, 02 May 2005 13:41:52 +0200 [thread overview]
Message-ID: <m3oebtlurj.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1CtF7f-000197-5K@fencepost.gnu.org> (Richard Stallman's message of "Mon, 24 Jan 2005 20:03:59 -0500")
Richard Stallman <rms@gnu.org> writes:
> * Lisp Changes in Emacs 21.4
>
> +++
> + ** The line-move, scroll-up, and scroll-down functions will now
> + modify the window vscroll to scroll through display rows that are
> + taller that the height of the window, for example in the presense of
> + large images. To disable this feature, Lisp code may bind the new
> + variable `auto-window-vscroll' to nil.
>
> This seems like mainly a user-level change, so it should be described
> in the user changes section. Also, I think the new scrolling feature
> may needs to be in the Emacs Manual.
Vscrolling is not a user-controlled feature as such, and the current
description in NEWS is about Lisp functions behaving differently, but
with a user visible effect to fix short-comings of previous releases.
Also, I do not envision that a user would want to disable
auto-window-vscroll (so it is not a defcustom).
So I suggest to keep the above entry as is.
>
> Could you DTRT with NEWS?
I have added the following description to the user visible changes:
** Moving or scrolling through images (and other lines) taller that
the window now works sensible, by automatically adjusting the window's
vscroll property.
>
> Also maybe the Emacs Manual, but if you
> just add the new item to NEWS, that will serve as a reminder to update
> the Emacs Manual.
IMO, the new functionality is "obvious", so I don't think it is
necessary to mention this in the Emacs Manual - and I don't know
what to write or where...
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
parent reply other threads:[~2005-05-02 11:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1CtF7f-000197-5K@fencepost.gnu.org>]
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=m3oebtlurj.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).