From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-trunk-diffs] Changes to emacs/etc/NEWS
Date: Wed, 08 Dec 2004 23:42:25 -0500 [thread overview]
Message-ID: <E1CcG8H-0007dm-PT@fencepost.gnu.org> (raw)
In-Reply-To: <87acsps7qw.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 08 Dec 2004 00:06:50 -0500)
I don't find the merged behavior we have right now unclean at all:
The `t' simply means: "default from now on".
That is quite unusual, for Emacs Lisp, and is certainly not what
t should mean.
In contrast your proposal of nil would mean "default even for those things
written before".
Right; the ordering of a default definition and a specific definition
that inherits from that default should not make any difference.
Furthermore by splitting the thing into t and nil you'll not only make the
code bigger,
A small amount of implementation code more or less is a minor issue
when the question is one of making things clear to users.
, but you'll also lose flexibility since it won't be possible to
specify a default for a subset of the face spec.
How much is that flexibility worth, in practice?
Which cases use it?
next prev parent reply other threads:[~2004-12-09 4:42 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 ` [Emacs-trunk-diffs] Changes to emacs/etc/NEWS Richard Stallman
2004-12-08 5:06 ` Stefan Monnier
2004-12-09 4:42 ` Richard Stallman [this message]
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
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=E1CcG8H-0007dm-PT@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 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).