From: David Kastrup <dak@gnu.org>
To: bob@rattlesnake.com
Cc: emacs-devel@gnu.org
Subject: Re: font-log
Date: Fri, 23 May 2008 13:03:32 +0200 [thread overview]
Message-ID: <85iqx5e0zf.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m1JzUvb-002K4NC@rattlesnake.com> (Robert J. Chassell's message of "Fri, 23 May 2008 10:55:15 +0000 (UTC)")
"Robert J. Chassell" <bob@rattlesnake.com> writes:
> I find it perfectly reasonable. "nil" does not mean "don't log
> the fonts" but rather "the font-log contains nothing yet". As you
> say: just like buffer-undo-list.
>
> As a user, I pay attention to the command, `font-show-log', and
> figure that the variable follows it.
Variables have DOC strings for a reason.
> The variable `buffer-undo-list' is wrong, too; nil should turn the
> feature off not on.
Logging is on iff (listp buffer-undo-list) is t.
> I understand the list contains nothing until you enable it; but that
> is irrelevant.
The list must contain nothing _after_ you enabled it. And that is
relevant. So it is natural to mark the list as inactive by not making
it a list. t accomplishes that. nil doesn't.
> Fortunately, neither variable is evaluated often and their default
> global values can get away with being t.
The default global value for buffer-undo-list is nil.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2008-05-23 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 10:54 -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds Robert J. Chassell
2008-05-22 12:06 ` Kenichi Handa
[not found] ` <m1JzGKI-002K4NC@rattlesnake.com>
2008-05-23 0:41 ` Kenichi Handa
2008-05-23 6:39 ` David Kastrup
2008-05-23 7:24 ` font-show-log facility Kenichi Handa
2008-05-23 17:41 ` Ted Zlatanov
2008-05-23 10:55 ` font-log [was Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds] Robert J. Chassell
2008-05-23 11:03 ` David Kastrup [this message]
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=85iqx5e0zf.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=bob@rattlesnake.com \
--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).