From: David Reitter <david.reitter@gmail.com>
To: grischka <grishka@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: gtk scroll bar deficiency
Date: Thu, 14 Jun 2007 19:22:39 +0100 [thread overview]
Message-ID: <1088867D-4306-4391-B0D0-E9CF971AE82B@gmail.com> (raw)
In-Reply-To: <00b701c7aea8$72403de0$4a42fe91@j4f3n1>
On 14 Jun 2007, at 18:21, grischka wrote:
> Fact is that the toolkits don't enforce neither the one nor
> the other behaviour, but also that no scrollbar toolkit ever
> will magically be able to adjust for the last line of the file
> to stay on bottom of the window if the editor machinery can't
> tell in advance (!) where in the file the last page starts.
And similarly, keeping the editor at a constant size is pretty much
impossible when the total number of lines in a buffer is unknown.
That is, of course, very confusing to many users who consider
switching to Emacs from another editor. To them, the vertical scroll-
bar has to do with the vertical position in the buffer and the
vertical dimensions of the window and the buffer. (The horizontal
scroll-bar, if necessary, handles the horizontal dimensions.) The
number of characters on each line and shown in the window isn't
really perceptually salient.
That's something that has been discussed earlier, and it hasn't been
solved, which was fine when 22.1 was overdue. But now it would be
nice to have the number of lines available. For the scroll-bar, a
reasonable estimate would do the job (count line lengths in various
randomly sampled portions of the buffer if the buffer is big): the
scroll-bar is a visual tool and not an exact science. The number of
characters on the last page(s) may need to be precisely determined,
though
next prev parent reply other threads:[~2007-06-14 18:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 8:52 gtk scroll bar deficiency grischka
2007-06-14 9:20 ` Thien-Thi Nguyen
2007-06-14 11:56 ` grischka
2007-06-14 17:21 ` grischka
2007-06-14 18:22 ` David Reitter [this message]
2007-06-14 20:30 ` Jason Rumney
2007-06-15 11:41 ` grischka
2007-06-15 14:48 ` Stefan Monnier
2007-06-18 13:32 ` grischka
2007-06-14 19:05 ` Stefan Monnier
2007-06-15 11:46 ` grischka
2007-06-15 14:56 ` Stefan Monnier
2007-06-15 15:56 ` Sam Steingold
2007-06-15 18:35 ` Stefan Monnier
2007-06-15 18:58 ` Sam Steingold
2007-06-14 9:24 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2007-06-11 18:05 Sam Steingold
2007-06-11 19:25 ` Stefan Monnier
2007-06-11 19:54 ` Sam Steingold
2007-06-11 21:09 ` Stefan Monnier
2007-06-12 5:52 ` Jan Djärv
2007-06-12 5:57 ` Ralf Angeli
2007-06-12 6:06 ` Jan Djärv
2007-06-12 6:12 ` Ralf Angeli
2007-06-12 7:40 ` Jan Djärv
2007-06-15 20:51 ` Ralf Angeli
2007-06-12 11:09 ` David Reitter
2007-06-12 8:49 ` Andreas Schwab
2007-06-12 9:10 ` Jan Djärv
2007-06-12 13:04 ` Sam Steingold
2007-06-12 13:11 ` David Kastrup
2007-06-12 13:19 ` Sam Steingold
2007-06-12 15:13 ` Stefan Monnier
2007-06-12 22:38 ` Davis Herring
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=1088867D-4306-4391-B0D0-E9CF971AE82B@gmail.com \
--to=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=grishka@gmx.de \
/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.