unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Schroeder <alex@emacswiki.org>
Cc: Eli Zaretskii <eliz@gnu.org>, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Face color changes
Date: Wed, 29 Dec 2004 16:26:14 +0100	[thread overview]
Message-ID: <87u0q5ruqx.fsf@confusibombus.emacswiki.org> (raw)
In-Reply-To: <87k6r1r7bb.fsf@jurta.org> (Juri Linkov's message of "Wed, 29 Dec 2004 07:04:08 +0200")

Juri Linkov <juri@jurta.org> writes:

> All conditions should be preserved with changes
> made only in the condition for the current environment.

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.

You seem to argue that the users' customization will not make sense on
the new system, if we add the necessary code.

I claim, however, that this "magic" will be harder to understand for
users that don't want to delve into customizations.

Which of the two points is more important?

Note that we don't have to worry about users that know a lot about
faces: They can for example M-x customize-face RET isearch RET 
Choose "State" and select "7 - select all display specs" -- they can
then do the customizations they require and save.

The only thing I think we might add is a check when saving if "just
showing current attributes" and other display specs exist.  I'm not
sure we need this, however.  If we wanted to teach new users about
display specs, we should just default to "show all display specs" --
and I don't think we want that.

In my opinion, we don't need to change anything.

Alex.
-- 
.O.  http://www.emacswiki.org/alex/
..O  Schroeder's fifth law:
OOO  Never accept more work than you can handle in one night of hacking.

  reply	other threads:[~2004-12-29 15:26 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 [this message]
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
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=87u0q5ruqx.fsf@confusibombus.emacswiki.org \
    --to=alex@emacswiki.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --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).