unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "grischka" <grishka@gmx.de>
To: <emacs-devel@gnu.org>
Subject: Re: gtk scroll bar deficiency
Date: Thu, 14 Jun 2007 19:21:10 +0200	[thread overview]
Message-ID: <00b701c7aea8$72403de0$4a42fe91@j4f3n1> (raw)
In-Reply-To: 87lkemki35.fsf@ambire.localdomain

> > Cheap propaganda. The truth is that current emacs' idea of scrolling 
> > is just too simple minded than that it could drive a standard scrollbar 
> > correctly. 

> Cheap troll.  [Surely you can do better than that?]

> -miles

Yep, sorry, bad education. 

Anywho, for the records, this thread started with an user 
reporting that in recent emacs scrolling down on the last 
page ends up with an empty window which he summarized as:
    "it looks like a bug to me..."

This user then could learn that it's not emacs' fault but
    "...because toolkit writers are boneheaded"
and anyway it is his
    "...kind of wrong question that leads to the arbitrary 
     braindead limitations in current GUI toolkits."

Now I don't mind clear statements, I just was trying to point 
out that these are essentially incorrect. [was this good?]

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. 

--- grischka

  parent reply	other threads:[~2007-06-14 17:21 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 [this message]
2007-06-14 18:22     ` David Reitter
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

  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='00b701c7aea8$72403de0$4a42fe91@j4f3n1' \
    --to=grishka@gmx.de \
    --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).