From: Kenichi Handa <handa@m17n.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: miles@gnu.org, emacs-devel@gnu.org
Subject: Re: fontset/font change
Date: Thu, 12 Mar 2009 15:40:41 +0900 [thread overview]
Message-ID: <E1Lheav-0006ed-QL@etlken> (raw)
In-Reply-To: <87eix32xfa.fsf@cyd.mit.edu> (message from Chong Yidong on Thu, 12 Mar 2009 00:10:49 -0400)
In article <87eix32xfa.fsf@cyd.mit.edu>, Chong Yidong <cyd@stupidchicken.com> writes:
> > 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?
I don't think so because I don't here any complaints about
it after I changed t for the default long ago in
emacs-unicode-2 branch. And even since the merge of about
one year ago, there's no complaint either.
So, if you maintainers think that the incompatible change
now is ok, I'll do (2) above quickly.
> As Miles mentioned, either way this needs to be documented in the
> docstring.
Sure.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-03-12 6:40 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
2009-03-12 6:40 ` Kenichi Handa [this message]
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
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=E1Lheav-0006ed-QL@etlken \
--to=handa@m17n.org \
--cc=cyd@stupidchicken.com \
--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).