unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: fontset/font change
Date: Thu, 12 Mar 2009 11:53:43 +0900	[thread overview]
Message-ID: <E1Lhb3H-0005xo-8S@etlken> (raw)
In-Reply-To: <87ab7rwny3.fsf@catnip.gol.com> (message from Miles Bader on Thu,  12 Mar 2009 10:05:08 +0900)

In article <87ab7rwny3.fsf@catnip.gol.com>, Miles Bader <miles@gnu.org> writes:

> Kenichi Handa <handa@m17n.org> writes:
>>> (set-fontset-font t 'unicode "Droid Sans Fallback")
> >
> > Here `t' is the same as "fontset-default".  This facility is
> > kept just for backward compatibility.

> Isn't it useful?  Is there a reason not to keep it as a feature...?

Ah, wait, I recalled the history.  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.

But, before finishing it (it seems that I just changed `t'
for the default), I forget about this matter when I got very
busy for the other tasks.  :-(

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.

---
Kenichi Handa
handa@m17n.org




  reply	other threads:[~2009-03-12  2:53 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 [this message]
2009-03-12  4:01       ` Miles Bader
2009-03-12  4:10       ` Chong Yidong
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

  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=E1Lhb3H-0005xo-8S@etlken \
    --to=handa@m17n.org \
    --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).