From: Miles Bader <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, Eli Zaretskii <eliz@gnu.org>,
drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Face color changes
Date: Wed, 29 Dec 2004 20:27:47 -0500 [thread overview]
Message-ID: <20041230012747.GA29490@fencepost> (raw)
In-Reply-To: <87u0q5ruqx.fsf@confusibombus.emacswiki.org>
On Wed, Dec 29, 2004 at 04:26:14PM +0100, Alex Schroeder wrote:
> This sounds a lot like overengineering to me. Assume an innocent user
> who takes his face definitions from one system to the next. Depending
> on what kind of system it is, his faces will either look like what he
> customized them, or it will look like the default definitions for that
> kind of system.
...
> In my opinion, we don't need to change anything.
It seems that it's hard to do perfectly without using "show all display
specs" -- whether it changes only the current spec, or overwrites
everything, it's probably going to screw up half the time.
However, I've definitely been burned by the current rather destructive
behavior. I'll carefully customize several different specs (say tty and
default), and then _once_ I'll forget to use show-all-display-specs when
tweaking some minor detail, and -- whoops! -- all my other customizations
will be lost.
Perhaps a good method might be this: Default to show-all-display-specs _if_
the user has changed anything; if a face is still completely defaulted, just
show the current environment's spec case (as it does now). That way, the
first time the user customizes a face, it will overwrite all specs for that
face with a single case, applying in all environments. If he later wants to
change something, it will show all display specs, but that will be almost the
same as not doing so, because there will only be the single default entry due
to his previous customization. If he later adds a new display-spec case
(which will be easy, as the "add case" widget will already be active), it
will then be displayed and shown for subsequent customizations, but that will
presumably not be too confusing, as all specs shown will have been added by
the user.
Since on average, such behavior would be almost the same as the current
behavior, this wouldn't be a drastic change either.
-Miles
--
Is it true that nothing can be known? If so how do we know this? -Woody Allen
next prev parent reply other threads:[~2004-12-30 1:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 19:57 Face color changes Juri Linkov
2004-12-26 23:49 ` Miles Bader
2004-12-27 8:28 ` Eli Zaretskii
2004-12-27 8:47 ` Jan D.
2004-12-27 22:35 ` Richard Stallman
2004-12-27 8:50 ` Miles Bader
2004-12-27 11:15 ` Eli Zaretskii
2004-12-27 17:16 ` Drew Adams
2004-12-27 17:32 ` Eli Zaretskii
2004-12-27 17:44 ` Drew Adams
2004-12-27 21:49 ` Eli Zaretskii
2004-12-29 7:41 ` Drew Adams
2004-12-29 15:31 ` Alex Schroeder
2004-12-29 19:38 ` Robert J. Chassell
2004-12-29 20:00 ` Robert J. Chassell
2004-12-30 16:43 ` Richard Stallman
2004-12-28 2:52 ` Juri Linkov
2004-12-28 17:25 ` Richard Stallman
2004-12-28 20:16 ` Eli Zaretskii
2004-12-29 4:38 ` Richard Stallman
2004-12-29 5:04 ` Juri Linkov
2004-12-29 15:26 ` Alex Schroeder
2004-12-30 0:22 ` Richard Stallman
2004-12-30 14:18 ` Alex Schroeder
2004-12-30 20:59 ` Richard Stallman
2004-12-30 1:27 ` Miles Bader [this message]
2004-12-30 14:15 ` Alex Schroeder
2004-12-30 16:43 ` Richard Stallman
2004-12-30 21:16 ` Miles Bader
2005-01-01 5:24 ` Richard Stallman
2005-01-03 18:17 ` Kevin Rodgers
2005-01-04 3:36 ` Richard Stallman
2005-01-04 9:08 ` Juri Linkov
2004-12-27 22:35 ` Richard Stallman
2004-12-28 2:57 ` Juri Linkov
2004-12-27 18:06 ` Richard Stallman
2004-12-27 8:12 ` Eli Zaretskii
2004-12-28 4:57 ` Richard Stallman
2004-12-28 20:31 ` Eli Zaretskii
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=20041230012747.GA29490@fencepost \
--to=miles@gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).