From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 3576@emacsbugs.donarmstrong.com
Subject: bug#3576: 23.0.94; scroll bar scrolls past eob - keeps scrolling
Date: Tue, 16 Jun 2009 17:34:56 -0700 [thread overview]
Message-ID: <8BA1212D193F486090CFAC50E0C100E3@us.oracle.com> (raw)
In-Reply-To: <83k53cavee.fsf@gnu.org>
> > > Yep. Emacs 21.4 stops on the last text line, Emacs 22.3
> > > and 23.0.94 stop on EOB.
> >
> > What do you mean by "stop on EOB"? If end of the buffer is
> > the newline immediately following the last line of non-newline
> > chars, then how can showing up to a screenful of blank vertical
> > space be considered "stopping at EOB"?
>
> EOB == (point-max)
>
> Emacs 21.4 stops when the last line of the buffer is at the topmost
> line of the window. Emacs 22 and 23 put EOB on the topmost line of
> the window.
Emacs 22/23 does not put the last non-whitespace line at the top of the window.
It apparently puts (point-max) at the top, which in most cases (e.g. Lisp
libraries) is a line with only a newline character.
Why should they put the last line (whitespace or not) at the _top_ of the
window, instead of the bottom of the window? Why would someone want to see an
extra screen of blank space, with the final newline at the top of the window?
That just doesn't seem very user friendly.
Do you know of a use case for that, which might justify that as the standard
behavior?
If not, I propose that this be fixed by returning to the Emacs 20/21 behavior.
> > Do you mean that it decides that the final newline has as a
> > right to be scrolled to the top of the screen? Is that what
> > "stopping at eob" means?
> >
> > If this is just an unfortunate result of the way things
> > happen to be currently implemented, that's one thing.
> > But I find it hard to believe that this would have been a
> > design goal - that someone would start out intentionally to
> > produce this behavior. What's the advantage or use case?
> >
> > I've never seen this behavior in any other app (though I'm
> > sure you'll come up with some other app that has the same
> > behavior). ;-)
>
> I was just stating the fact, not embracing it.
>
> Now, can you please stop shouting at me? My only sin is that I
> confirmed your report.
No one has shouted at you. Don't be so defensive.
This is not about you, at all. It's merely a bug report. Thank you for
confirming it.
next prev parent reply other threads:[~2009-06-17 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 16:34 bug#3576: 23.0.94; scroll bar scrolls past eob - keeps scrolling Drew Adams
2009-06-15 17:34 ` Eli Zaretskii
2009-06-15 17:44 ` Drew Adams
2009-06-15 18:39 ` Eli Zaretskii
2009-06-15 20:04 ` Drew Adams
2009-06-16 3:03 ` Eli Zaretskii
2009-06-16 3:10 ` Drew Adams
2009-06-16 18:25 ` Eli Zaretskii
2009-06-17 0:34 ` Drew Adams [this message]
2009-06-27 0:38 ` Stefan Monnier
2011-09-17 6:04 ` Lars Magne Ingebrigtsen
2011-09-17 14:01 ` Drew Adams
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=8BA1212D193F486090CFAC50E0C100E3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3576@emacsbugs.donarmstrong.com \
--cc=eliz@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).