From: David De La Harpe Golden <david@harpegolden.net>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Filipe Cabecinhas <filcab@gmail.com>,
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>,
emacs-devel@gnu.org
Subject: Re: Native scrollbars? [was: visible-bell patch for Mac OS X]
Date: Sat, 13 Feb 2010 05:45:21 +0000 [thread overview]
Message-ID: <4B763C71.7060807@harpegolden.net> (raw)
In-Reply-To: <873a15x02e.fsf@uwakimon.sk.tsukuba.ac.jp>
Stephen J. Turnbull wrote:
> David De La Harpe Golden writes:
>
> > Emacs could make the scrollbars native and this would make sure
> > they weren't overdrawn
>
[Just to be clear, I was quoting the gtk page, gtk+ guys wrote the above
not me ]
> I suspect that going to native scrollbars would annoy a lot of users.
>
I'm not clear that's what the gtk+ guys mean in context by "native",
however. That wouldn't make sense in context, because there'd be no
gtk+ drawn scrollbars for emacs to stomp on?
GNU Emacs indeed has a compile-time choice of "toolkit" (native as you
[Stephen T.] mean it) scrollbars, or the emacs-internal ones. The
toolkit ones are significantly disliked, yes, however I think they're
quite widely used, perhaps unlike the xemacs case.
So I think the gtk+/emacs bug may show up (I don't actually see it on my
system, but my gtk+ might be too old) with the _toolkit_ scrollbars
from the emacs perspective, since emacs thinks they're a child X11
window and thinks it's okay to clear the parent window, which perhaps
eats the gtk+ drawn scrollbar which isn't in a separate X11 child window
anymore in recent gtk.
So I think gtk+ guys mean there's a way for emacs to request
gtk to continue to use "native" (real X11 child) windows at the gtk/gdk
level:
Well, there is a way to do it app-globally- set env var GDK_NATIVE_WINDOWS=1
http://blogs.gurulabs.com/dax/2009/10/what-gdk-native.html
I'm not familiar enough with gtk to know if it's possible for emacs
to ask for only the gtk+ toolkit scrollbars to be "native" in the sense
gtk+ guys seem to mean it, at least based on my current potentially
incorrect understanding as above.
next prev parent reply other threads:[~2010-02-13 5:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 13:34 visible-bell patch for Mac OS X Filipe Cabecinhas
2010-01-31 3:34 ` Chong Yidong
2010-02-01 0:41 ` YAMAMOTO Mitsuharu
2010-02-01 15:56 ` Chong Yidong
2010-02-01 23:33 ` YAMAMOTO Mitsuharu
2010-02-02 1:40 ` YAMAMOTO Mitsuharu
2010-02-02 1:45 ` YAMAMOTO Mitsuharu
2010-02-02 8:47 ` Leo
2010-02-13 1:30 ` YAMAMOTO Mitsuharu
2010-02-13 1:51 ` David De La Harpe Golden
2010-02-13 3:54 ` Native scrollbars? [was: visible-bell patch for Mac OS X] Stephen J. Turnbull
2010-02-13 5:45 ` David De La Harpe Golden [this message]
2010-02-13 6:45 ` David De La Harpe Golden
2010-02-13 7:32 ` YAMAMOTO Mitsuharu
2010-02-13 13:32 ` Jan Djärv
2010-02-13 9:00 ` Native scrollbars? David Kastrup
2010-02-13 10:02 ` Eli Zaretskii
2010-02-13 12:23 ` Jan Djärv
2010-02-13 12:46 ` David Kastrup
2010-02-13 13:40 ` Jan Djärv
2010-02-13 14:26 ` David Kastrup
2010-02-13 13:50 ` Stephen J. Turnbull
2010-02-13 6:45 ` visible-bell patch for Mac OS X YAMAMOTO Mitsuharu
2010-02-13 7:01 ` David De La Harpe Golden
2010-02-13 7:54 ` Jan Djärv
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=4B763C71.7060807@harpegolden.net \
--to=david@harpegolden.net \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=filcab@gmail.com \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=stephen@xemacs.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 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.