From: Chong Yidong <cyd@stupidchicken.com>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: fontset/font change
Date: Thu, 12 Mar 2009 00:10:49 -0400 [thread overview]
Message-ID: <87eix32xfa.fsf@cyd.mit.edu> (raw)
In-Reply-To: <E1Lhb3H-0005xo-8S@etlken> (Kenichi Handa's message of "Thu, 12 Mar 2009 11:53:43 +0900")
Kenichi Handa <handa@m17n.org> writes:
> In Emacs 22, `nil' was for "fontset-default", but while working on
> emacs-unicode-2 branch, someone suggested that nil usually should mean
> the currently selected one. I thought that was a good idea, and was
> going to change `t' for the default fontset, and `nil' for the the
> fontset of the current frame.
>
> Sorry for the confusion, but what should I do now?
>
> (1) Just recover the behaviour of Emacs 22: nil for the default
> (2) Make nil for the currently selected fontset, and t for the default
> (3) (1) and make t for the currently selected one.
It seems a little cleaner to have nil specify the current fontset rather
than fontset-default, but only a little. In your estimation, is there a
significant amount of outside code (e.g. user customizations) that rely
on the old behavior? If so, I don't think it's profitable to make this
change.
As Miles mentioned, either way this needs to be documented in the
docstring.
next prev parent reply other threads:[~2009-03-12 4:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 13:50 fontset/font change Miles Bader
2009-03-11 14:05 ` Jason Rumney
2009-03-11 14:36 ` Miles Bader
2009-03-12 1:16 ` Kenichi Handa
2009-03-12 13:19 ` Jason Rumney
2009-03-13 5:18 ` Kenichi Handa
2009-03-12 0:57 ` Kenichi Handa
2009-03-12 1:05 ` Miles Bader
2009-03-12 2:53 ` Kenichi Handa
2009-03-12 4:01 ` Miles Bader
2009-03-12 4:10 ` Chong Yidong [this message]
2009-03-12 6:40 ` Kenichi Handa
2009-03-12 13:39 ` Chong Yidong
2009-03-13 5:10 ` Kenichi Handa
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=87eix32xfa.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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 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.