unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Buffer Boundary Problem
Date: Sat, 31 Jan 2004 19:13:17 -0500	[thread overview]
Message-ID: <20040201001317.GD16423@fencepost> (raw)
In-Reply-To: <401C36D3.4050609@ig.com.br>

On Sat, Jan 31, 2004 at 09:14:27PM -0200, Vinicius Jose Latorre wrote:
> But it has a problem, suppose you're visiting a file bigger than the window
> in Emacs.  So, the vertical scroll bar looks like:
...
> Now, type several C-n (next-line) until the window scrolls up.
> The vertical scroll bar now looks like:

By `it' I presume you mean the scrollbars have a problem, and that you're
using GTK scrollbars.

If so, the problem is that the GTK scrollbars are missing some functionality
that emacs needs to work optimally, so as a work-around emacs scrollbars are
little funny near the end of a buffer.  Basically there's some extra space
at the end so you can use the scrollbar to scroll the last line to the top
of the window.

[While I understand the reason for this problem, I wonder if it might be
useful to have a variable which controls that behavior -- by setting it to a
different value, you could make scrollbars display `correctly' but lose the
ability to scroll the last line to the window top... is this possible?]

-Miles
-- 
Somebody has to do something, and it's just incredibly pathetic that it
has to be us.  -- Jerry Garcia

  reply	other threads:[~2004-02-01  0:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31 23:14 Buffer Boundary Problem Vinicius Jose Latorre
2004-02-01  0:13 ` Miles Bader [this message]
2004-02-01  0:36   ` Jan D.
2004-02-01  1:06     ` Vinicius Jose Latorre
2004-02-01  1:04   ` Vinicius Jose Latorre
2004-02-01 11:52     ` Matt Hodges
2004-02-01 12:30       ` Jan D.
2004-02-01 12:54         ` Jan D.
2004-02-02  9:46           ` Kim F. Storm
2004-02-01 21:32       ` Vinicius Jose Latorre
2004-02-01 21:38       ` Kim F. Storm
2004-02-01 12:26 ` Jan D.

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=20040201001317.GD16423@fencepost \
    --to=miles@gnu.org \
    --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).