all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Font settings ignored on new frames
Date: Fri, 06 Jun 2008 22:07:32 +0900	[thread overview]
Message-ID: <E1K4bfI-0004mO-GJ@etlken.m17n.org> (raw)
In-Reply-To: <jwv7id4hbbh.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 04 Jun 2008 22:22:22 -0400)

In article <jwv7id4hbbh.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>>> If I start me Emacs as:
>>>>> src/emacs -Q --eval '(custom-set-faces (quote (default ((t (:height 60 :width semi-condensed :family "DejaVu Sans Mono"))))))'

[...]
> It doesn't matter how it works: it's the command output by customize.
> The call is typically in the user's .emacs as a result of M-x
> customize-face.

I was almost lost in the labyrinth of codes to set the
default face attributes, but I at least found this prolem:

With Emacs 23 (pre-unicode-merge and the trunk),
  (custom-set-faces '(default ((t (:family "courier")))))
instantly change the current frame to use courier, but
  (face-attribute 'default :family t)
returns `unspecified'.

On the other hand, with Emacs 22,
  (custom-set-faces '(default ((t (:family "courier")))))
doesn't change the current frame, and
  (face-attribute 'default :family t)
returns "courier".

Which is the correct behaviour?

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-06-06 13:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 20:59 Font settings ignored on new frames Stefan Monnier
2008-06-04 11:05 ` Kenichi Handa
2008-06-04 16:26   ` Stefan Monnier
2008-06-05  0:36     ` Kenichi Handa
2008-06-05  1:39       ` Miles Bader
2008-06-05  2:22       ` Stefan Monnier
2008-06-06 13:07         ` Kenichi Handa [this message]
2008-06-06 18:16           ` Glenn Morris
2008-06-10 19:17     ` Stefan Monnier

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=E1K4bfI-0004mO-GJ@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.