From: Andrew Kurn <kurn@sfu.ca>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>
Cc: 32002@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#32002: 24.4; Scroll bar start, end not correct
Date: Wed, 4 Jul 2018 00:49:22 -0700 [thread overview]
Message-ID: <20180704074922.GA25658@sfu.ca> (raw)
In-Reply-To: <11717.1530681181@alto>
Eli wrote:
> I think we support both those who share this opinion and
> those who don't. It sounds like you want to set
> scroll-bar-adjust-thumb-portion to nil.
Yes!! This is the answer I've been looking for, how to
disable the feature.
Many thanks.
. . . and have you got any idea why the author used 'thumb'
in the name? I suppose who the author is is lost in the
mists of time.
[and see below]
On Tue 3 Jul 2018 22:13 -0700, Mike Kupfer wrote:
> Andrew Kurn wrote:
>
> > Anyhow, my contention is that, since the whole buffer is on display,
> > the scroll bar should extend over the whole window. The length of the
> > scroll bar, as a fraction of the window height, is supposed to be the
> > fraction of the buffer on display. Its top is the character (line,
> > usually) where the display starts. Its bottom is where it stops.
>
> That's what I would expect, too. The current behavior was explained to
> me as deliberate, to account for differences in scrolling behavior when
> comparing Emacs to GTK apps like gedit. That is, when you get to the
> end of a file in gedit, the last line of the file is at the bottom of
> the window. If you get to the bottom of the file and continue to press
> PgDown or the down arrow key, gedit just beeps at you.
As the queen says, we never notice what other women are wearing.
Comparing emacs and gedit . . .
>
> With Emacs, though, it is possible, using PgDown or C-v, to scroll down
> so that the last line of the file appears higher up in the window,
> possibly even at the very top of the window.
>
> There does seem to be an inconsistency between the scrollbar and
> scrolling using keypresses. For example, in the attached screenshot, if
> I try to scroll using PgDown, C-v, or down arrow, I get an "End of
> buffer" error. Yet I can scroll down using the down-stepper on the
> scrollbar. And if I drag the scrollbar marker down as far as it will
> go, the text scrolls off the top, leaving me with a blank window.
>
> Personally, I find the gap below the scrollbar marker disorienting; I
> can't trust the scrollbar to show me when I'm at the end of the file.
> This is annoying enough that I try to avoid Emacs+GTK.
>
> mike
Goodness! Don't throw out the baby with the bath-water. With
its faults, emacs is still emacs.
I almost said "with all its faults," but, really, I find so few
problems with emacs that even such a minor one as this one (now
understood not to be a bug at all) seems worth reporting.
Andrew
next prev parent reply other threads:[~2018-07-04 7:49 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 7:36 bug#32002: 24.4; Scroll bar start, end not correct Andrew Kurn
2018-06-29 8:53 ` Eli Zaretskii
[not found] ` <20180629162402.GA21197@sfu.ca>
2018-06-29 17:24 ` Eli Zaretskii
2018-07-01 1:30 ` Andrew Kurn
2018-07-02 18:16 ` Glenn Morris
2018-07-02 18:20 ` Glenn Morris
2018-07-03 12:58 ` Andrew Kurn
2018-07-04 2:00 ` Noam Postavsky
2018-07-04 3:45 ` Andrew Kurn
2018-07-04 4:59 ` Eli Zaretskii
2018-07-04 5:13 ` Mike Kupfer
2018-07-04 5:34 ` Eli Zaretskii
2018-07-04 16:32 ` Mike Kupfer
2018-07-04 23:36 ` Mike Kupfer
2018-07-04 23:44 ` Noam Postavsky
2018-07-04 23:56 ` Mike Kupfer
2018-07-05 2:36 ` Eli Zaretskii
2018-07-05 5:28 ` Mike Kupfer
2018-07-05 6:27 ` Eli Zaretskii
2018-07-05 15:05 ` Mike Kupfer
2018-07-06 3:58 ` Mike Kupfer
2018-07-06 6:10 ` Eli Zaretskii
2018-07-06 10:32 ` Robert Pluim
2018-07-06 12:56 ` martin rudalics
2018-07-06 13:31 ` Eli Zaretskii
2018-07-07 7:15 ` martin rudalics
2018-07-07 7:35 ` Eli Zaretskii
2018-07-07 7:47 ` martin rudalics
2018-07-07 15:19 ` Mike Kupfer
2018-07-07 15:59 ` Eli Zaretskii
2018-07-07 23:05 ` Mike Kupfer
2018-07-08 3:00 ` Mike Kupfer
2018-07-07 16:00 ` Mike Kupfer
2018-07-08 8:11 ` martin rudalics
2018-07-09 1:42 ` Mike Kupfer
2018-07-09 2:53 ` Mike Kupfer
2018-07-09 8:34 ` martin rudalics
2018-07-09 8:34 ` martin rudalics
2018-07-09 14:39 ` Mike Kupfer
2018-07-10 7:30 ` martin rudalics
2018-07-14 4:31 ` Mike Kupfer
2018-07-14 8:00 ` martin rudalics
2018-07-21 0:28 ` Mike Kupfer
2018-07-21 7:44 ` martin rudalics
2018-07-14 4:13 ` Mike Kupfer
2018-07-06 15:02 ` Mike Kupfer
2018-07-06 16:02 ` Robert Pluim
2018-07-07 7:17 ` martin rudalics
2018-07-04 7:49 ` Andrew Kurn [this message]
2018-07-04 9:30 ` Stephen Berman
2018-07-04 12:10 ` Noam Postavsky
2018-07-04 16:34 ` Mike Kupfer
2018-07-10 19:16 ` Andrew Kurn
2018-07-11 3:02 ` Eli Zaretskii
2018-07-12 7:11 ` Andrew Kurn
2018-07-12 13:29 ` Eli Zaretskii
2018-07-12 15:57 ` Stephen Berman
2018-07-12 16:35 ` Eli Zaretskii
2018-07-14 4:56 ` Mike Kupfer
2018-07-14 6:49 ` Eli Zaretskii
2018-07-14 8:01 ` martin rudalics
2018-07-21 13:50 ` Eli Zaretskii
2018-07-22 7:25 ` martin rudalics
2018-07-22 14:55 ` Eli Zaretskii
2018-07-23 6:51 ` martin rudalics
2018-07-27 8:30 ` Eli Zaretskii
2018-07-27 9:23 ` martin rudalics
2018-07-27 11:03 ` Andrew Kurn
2018-07-27 12:27 ` Eli Zaretskii
2018-07-28 7:22 ` martin rudalics
2018-07-29 2:51 ` Mike Kupfer
2018-07-16 1:47 ` Mike Kupfer
2018-07-21 13:53 ` Eli Zaretskii
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=20180704074922.GA25658@sfu.ca \
--to=kurn@sfu.ca \
--cc=32002@debbugs.gnu.org \
--cc=mkupfer@alum.berkeley.edu \
--cc=npostavs@gmail.com \
/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).