From: David Kastrup <dak@gnu.org>
Subject: Re: Compiling Emacs with GTK
Date: Thu, 24 Feb 2005 13:12:08 +0100 [thread overview]
Message-ID: <x5vf8idunb.fsf@lola.goethe.zz> (raw)
In-Reply-To: cvkf0q$46b$02$1@news.t-online.com
Hendrik Sattler <sattler2000@gmx.de> writes:
> David Kastrup wrote:
>
>> And that's because the ergonomics of almost all toolkit scrollbars
>> suck.
>>
>> To change the direction of moving, I have to move the
>> mouse. I can't control the size of the move except by dragging (a
>> recipe for RSI). When scrolling in one direction repeatedly, the
>> moment the scroll "thumbmark" gyrates under the mouse cursor, it
>> stops working.
>
> Mouse wheels are a great invention. Instead of mouse1/mouse2 to
> scroll, you use scroll_up/scroll_down, nothing is more intuitive
> than that. And at least with QT, you can use that on a horizontal
> scrollbar, too, if you place the mouse cursor over it. Some mice
> offer a real button instead of the wheel (I like this even better).
>
> And since this is about a text editor: PgUp/PgDown exist ;)
All those are arguments for not using the scrollbar at all. While you
can turn it off with Emacs easily, it is somewhat pointless to discuss
what scrollbar type is the best when not used.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-02-24 12:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1362.1109200883.32256.help-gnu-emacs@gnu.org>
2005-02-23 23:26 ` Compiling Emacs with GTK David Kastrup
2005-02-24 0:44 ` August
2005-02-24 10:25 ` Peter Dyballa
2005-02-24 15:07 ` August
[not found] ` <mailman.1374.1109208216.32256.help-gnu-emacs@gnu.org>
2005-02-24 8:12 ` Hendrik Sattler
2005-02-24 11:33 ` David Kastrup
2005-02-24 11:49 ` Hendrik Sattler
2005-02-24 12:12 ` David Kastrup [this message]
2005-02-24 14:37 ` Hendrik Sattler
2005-02-24 14:58 ` David Kastrup
2005-02-24 15:22 ` Lee Sau Dan
2005-02-24 15:53 ` Hendrik Sattler
2005-03-16 17:02 ` David Combs
2005-03-16 17:46 ` Stefan Monnier
2005-03-16 18:48 ` Kevin Rodgers
2005-02-25 13:46 ` Stefan Monnier
2005-02-25 14:18 ` David Kastrup
2005-02-25 17:50 ` August
[not found] ` <mailman.1673.1109355702.32256.help-gnu-emacs@gnu.org>
2005-02-25 18:36 ` David Kastrup
2005-02-25 23:28 ` August
2005-02-26 0:13 ` nfreimann
2005-02-26 1:40 ` August
2005-02-26 13:29 ` Eli Zaretskii
[not found] ` <mailman.1725.1109384617.32256.help-gnu-emacs@gnu.org>
2005-02-26 8:22 ` Thien-Thi Nguyen
2005-02-26 13:23 ` Eli Zaretskii
2005-02-26 15:09 ` nfreimann
2005-02-26 16:02 ` Eli Zaretskii
2005-02-26 15:06 ` David Hansen
2005-02-26 16:05 ` nfreimann
[not found] ` <mailman.1792.1109435067.32256.help-gnu-emacs@gnu.org>
2005-02-26 16:38 ` David Hansen
2005-02-26 17:02 ` David Kastrup
[not found] ` <mailman.1777.1109425933.32256.help-gnu-emacs@gnu.org>
2005-02-26 19:40 ` Stefan Daschek
[not found] <mailman.1721.1109377814.32256.help-gnu-emacs@gnu.org>
2005-02-26 0:49 ` Hendrik Sattler
2005-02-26 1:17 ` David Kastrup
2005-02-26 1:57 ` August
[not found] ` <mailman.1728.1109384621.32256.help-gnu-emacs@gnu.org>
2005-02-26 2:58 ` David Kastrup
[not found] ` <cvugmg$4ks$1@news.sap-ag.de>
2005-02-28 17:13 ` Kevin Rodgers
2005-02-26 1:12 ` David Kastrup
2005-02-23 23:01 August
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=x5vf8idunb.fsf@lola.goethe.zz \
--to=dak@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.
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).