From: Miles Bader <miles@lsi.nec.co.jp>
Cc: abraham@dina.kvl.dk, emacs-devel@gnu.org
Subject: Re: reducing defface redundancy
Date: 09 Jul 2002 10:25:37 +0900 [thread overview]
Message-ID: <buohej9bsku.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <200207081820.g68IKkT12950@aztec.santafe.edu>
Richard Stallman <rms@gnu.org> writes:
> So basically the rewritten face spec will look like the original
> face-spec except with the user's changes integrated.
>
> I think users will find this surprising and inconsistent.
Can you say why you think this? I think it gets about as close as we
can to `doing the intuitive thing' when a someone uses the simple face
customization -- it's really impossible to always do things correctly,
since we'd have to read the user's mind.
Remember that the way I suggest integrating the user's changes follows
the structure set up by the face creator, and possible user
customizations are one thing to think about when creating the face.
> In addition, we want to have buffer-local face definitions, and that
> will make this issue even more complex.
It depends on how buffer-local face definitions are implemented. My
feeling is that there _shouldn't_ be real buffer-specific faces, but
rather a way of remapping faces within a buffer. For instance foo-mode
could make the `foo-default' be used as the default face within its
buffers; if the user want's to change it, they'd have customize
`foo-default', not `default' (though the customization widget could
notice that there's a buffer-local remapping, and ask the user `do you
want to edit the global `default' face, or the `foo-default' face being
used in this buffer').
> You can customize a face for the current display, for the current
> session, looking at a simple list of attributes, but you cannot save
> this. Or you can customize the conditional commands that define the
> face, by looking at the whole structure of them. That kind of
> customization you can save if you wish.
Well that would certainly get rid of the ambiguity, but I suspect that
most users would absolutely hate it (I certainly would) -- it attempts
to solve a fairly rare problem (face customizations that have surprising
results on other display types) by making the _normal case_ more
inconvenient and confusing!
I think this is a case where it's possible to do a good job
automatically most of the time. Since the problems that might arise are
fairly minor (the face looks a bit funny), I think they're well
justified by the extra convenience and utility for users in the common
case from doing things automatically.
-Miles
--
The secret to creativity is knowing how to hide your sources.
--Albert Einstein
next prev parent reply other threads:[~2002-07-09 1:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 3:12 reducing defface redundancy Miles Bader
2002-04-20 7:14 ` Eli Zaretskii
2002-04-20 15:59 ` Per Abrahamsen
2002-04-20 17:35 ` Eli Zaretskii
2002-04-21 9:12 ` Per Abrahamsen
2002-04-20 17:41 ` Alex Schroeder
2002-04-21 2:00 ` Miles Bader
2002-04-21 9:17 ` Per Abrahamsen
2002-04-21 9:34 ` Miles Bader
2002-04-22 7:47 ` Richard Stallman
2002-04-22 7:47 ` Richard Stallman
2002-04-22 8:15 ` Miles Bader
2002-04-23 0:24 ` Richard Stallman
2002-04-23 1:36 ` Miles Bader
2002-04-24 17:54 ` Richard Stallman
2002-04-24 20:06 ` Miles Bader
2002-04-25 9:52 ` Per Abrahamsen
2002-04-26 3:18 ` Richard Stallman
2002-07-03 6:38 ` Miles Bader
2002-07-03 9:31 ` Kai Großjohann
2002-07-03 14:50 ` Kim F. Storm
2002-07-08 18:20 ` Richard Stallman
2002-07-09 1:25 ` Miles Bader [this message]
2002-07-09 18:51 ` Richard Stallman
2002-07-09 18:51 ` Richard Stallman
2002-07-09 20:52 ` Stefan Monnier
2002-07-10 19:20 ` Richard Stallman
2002-07-11 17:01 ` Stefan Monnier
2002-07-12 1:28 ` Miles Bader
2002-07-12 17:37 ` Richard Stallman
2002-04-21 20:02 ` Richard Stallman
2002-04-22 0:28 ` Miles Bader
2002-04-22 22:37 ` Richard Stallman
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=buohej9bsku.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=abraham@dina.kvl.dk \
--cc=emacs-devel@gnu.org \
--cc=miles@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).