From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Changing the no-toolkit scrollbar thumb color. (minor issue)
Date: Sun, 28 Sep 2003 18:47:14 -0500 (CDT) [thread overview]
Message-ID: <200309282347.h8SNlEi12333@raven.dms.auburn.edu> (raw)
In-Reply-To: <m1A3jFm-000IeAC@rattlesnake.com> (bob@rattlesnake.com)
Once we know exactly what the situation is for the Xaw3d,
Lesstif/Motif and GTK scroll bars, we can rewrite the documentation
string. I do not believe that there is a need for a non-standard
"State" message or a mini-buffer error message. I guess the user will
see that it has no effect. Then he _will_ read the documentation.
The user could have legitimate reasons to customize the face, even if
he is using GTK. He could be using several builds of Emacs with
different scroll bar types and want to use the same .emacs for all of
them. Also, he might want to set that variable to look like his de
facto GTK face, anyway. Then, for instance, if he is asked to specify
a face for something that looks somewhat similar to a scroll bar, he
can use scroll-bar.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-09-28 23:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 20:13 Changing the no-toolkit scrollbar thumb color. (minor issue) Rob Browning
2003-09-26 21:23 ` Luc Teirlinck
2003-09-26 21:32 ` Rob Browning
2003-09-27 18:16 ` Robert J. Chassell
2003-09-27 21:55 ` Luc Teirlinck
2003-09-28 13:08 ` Robert J. Chassell
2003-09-28 16:38 ` Jan D.
2003-09-28 21:17 ` Robert J. Chassell
2003-09-29 16:01 ` Jan D.
2003-09-29 19:05 ` Robert J. Chassell
2003-09-29 19:23 ` Jan D.
2003-09-28 16:42 ` Luc Teirlinck
2003-09-28 18:01 ` Luc Teirlinck
2003-09-28 21:38 ` Robert J. Chassell
2003-09-28 23:47 ` Luc Teirlinck [this message]
2003-09-29 0:52 ` Robert J. Chassell
2003-09-29 1:30 ` Luc Teirlinck
2003-09-29 11:58 ` Robert J. Chassell
2003-09-30 12:22 ` Richard Stallman
2003-09-29 19:31 ` Richard Stallman
2003-09-30 0:11 ` Luc Teirlinck
2003-09-30 13:55 ` Stefan Monnier
2003-09-30 14:25 ` Miles Bader
2003-09-30 15:16 ` Stefan Monnier
2003-10-04 18:29 ` Jan D.
2003-09-30 20:25 ` Richard Stallman
2003-10-04 18:36 ` Jan D.
2003-10-05 3:24 ` Richard Stallman
2003-10-05 17:56 ` Luc Teirlinck
2003-10-05 18:12 ` Jan D.
2003-10-05 18:27 ` Luc Teirlinck
2003-10-05 19:16 ` Luc Teirlinck
2003-10-05 20:57 ` Jan D.
2003-10-05 22:09 ` Luc Teirlinck
2003-10-06 0:14 ` Miles Bader
2003-10-06 2:22 ` Miles Bader
2003-10-06 4:15 ` Luc Teirlinck
2003-10-06 4:34 ` Luc Teirlinck
2003-10-12 15:04 ` Jan D.
2003-09-30 0:27 ` Robert J. Chassell
2003-09-30 20:24 ` Richard Stallman
2003-10-01 0:35 ` Danilo Segan
2003-10-04 0:35 ` Robert J. Chassell
2003-10-04 18:55 ` Jan D.
2003-10-04 18:43 ` Jan D.
2003-10-04 19:35 ` Danilo Segan
2003-10-04 18:11 ` Jan D.
2003-10-05 0:25 ` Miles Bader
2003-10-05 7:23 ` Jan D.
2003-10-05 7:59 ` Miles Bader
2003-09-28 21:25 ` Robert J. Chassell
2003-09-28 17:37 ` Luc Teirlinck
2003-09-28 21:33 ` Robert J. Chassell
2003-09-28 22:03 ` Luc Teirlinck
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=200309282347.h8SNlEi12333@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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).