all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-trunk-diffs] Changes to emacs/etc/NEWS
Date: Tue, 07 Dec 2004 23:40:39 -0500	[thread overview]
Message-ID: <E1Cbtd1-0003xK-By@fencepost.gnu.org> (raw)
In-Reply-To: <E1CbXz1-0001DK-AA@lists.gnu.org> (message from Stefan Monnier on Tue, 07 Dec 2004 00:33:55 -0500)

    ** An unconditional face specification in defface (one where the DISPLAY part
    is just t) applies to all cases and does not override subsequent entries.

This feature does not seem cleanly designed to me.  The first slot in
the spec is supposed to be a condition, and t as a condition has a
very clear meaning in Lisp.  To use t for any other meaning seems very
wrong.

It also seems that this change wasn't fully implemented,
because the code in cus-edit.el that interprets face specs
doesn't know about it.

I think we should replace this with a clean feature before
releasing it.  Here's one idea for a clean feature:

t as the condition means "or else", as it used to, as
people would expect.  nil as the condition means "default",
attributes to be shared by all the conditions.

It should not be very hard to implement this in faces.el instead of
the current code.  However, it needs to be implemented also in
cus-edit.el, which is harder, and in the Lisp manual.
Also, someone needs to check all 500-odd deffaces, but that
probably needs to be done anyway, and most of them will take
only a few seconds to see there's no issue.

Can you or someone please undertake to do this?

       reply	other threads:[~2004-12-08  4:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CbXz1-0001DK-AA@lists.gnu.org>
2004-12-08  4:40 ` Richard Stallman [this message]
2004-12-08  5:06   ` [Emacs-trunk-diffs] Changes to emacs/etc/NEWS Stefan Monnier
2004-12-09  4:42     ` Richard Stallman
2004-12-09  4:59       ` Stefan Monnier
2004-12-09  9:17         ` Kim F. Storm
2004-12-09 14:06           ` Stefan Monnier
2004-12-10 23:15         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Cbtd1-0003xK-By@fencepost.gnu.org \
    --to=rms@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 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.