unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: handa@m17n.org
Subject: Re: recent emacs font problems?
Date: Wed, 28 May 2003 09:55:18 -0400	[thread overview]
Message-ID: <E19L1Og-0002IM-Oi@fencepost.gnu.org> (raw)
In-Reply-To: <E19KtGx-0005tM-00@indigo.shootybangbang.com> (message from John Paul Wallington on Wed, 28 May 2003 06:14:48 +0100)

    Is this the right fix (not properly tested) ?

    --- /build/emacs/src/xfaces.c.~1.277.~	Wed May 28 06:00:50 2003
    +++ /build/emacs/src/xfaces.c	Wed May 28 06:10:40 2003
    @@ -6584,9 +6584,7 @@
	   frame_font = Fassq (Qfont, f->param_alist);
	   xassert (CONSP (frame_font) && STRINGP (XCDR (frame_font)));
	   frame_font = XCDR (frame_font);
    -      /* Specify 0 for FORCE_P here, so that we don't override
    -	 a :family attribute specified for `default' for new frames.  */
    -      set_lface_from_font_name (f, lface, frame_font, 0, 1);
    +      set_lface_from_font_name (f, lface, frame_font, 1, 1);
	 }
     #endif /* HAVE_WINDOW_SYSTEM */

That is not correct.  It would bring back a bug I fixed recently.  I
think it was the following bug.


Date: Thu, 15 May 2003 09:59:01 +0200 (CEST)
From: Klaus Straubinger <KSNetz@Arcor.DE>
To: bug-gnu-emacs@gnu.org

If the font family of the default face is changed with
(set-face-attribute 'default nil :family "fixed")
then this does not change the face's font for subsequent frames, as can
be seen with the evaluation of (face-font 'default) in the first frame
and in a second, created with C-x 5 2, respectively.

I found that that call to set_lface_from_font_name was
clobbering the family that had come from the new-frame default.

  parent reply	other threads:[~2003-05-28 13:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  1:14 recent emacs font problems? Miles Bader
2003-05-28  4:25 ` Kenichi Handa
2003-05-28  5:14   ` John Paul Wallington
2003-05-28  6:56     ` Miles Bader
2003-05-28 10:16       ` John Paul Wallington
2003-05-28 13:55     ` Richard Stallman [this message]
2003-05-30  0:47       ` Kim F. Storm
2003-05-30 17:13         ` Richard Stallman
2003-05-28  5:13 ` Karl Eichwalder
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 12:06 Jan D.
2003-06-10  0:17 ` Kim F. Storm
2003-06-10 18:18   ` Jan D.
2003-06-12 14:03     ` Richard Stallman
2003-06-12 16:29       ` Jan D.
2003-06-13 22:03         ` Richard Stallman
2003-06-26 21:32       ` Jan D.
2003-06-26 22:20         ` Sam Steingold
2003-07-07 21:51           ` David Abrahams
2003-07-07 22:16             ` Jason Rumney
2003-07-08 13:40               ` Sam Steingold
2003-07-09  1:31                 ` Miles Bader
2003-07-11 20:33               ` David Abrahams
2003-07-11 21:51                 ` Jason Rumney
2003-06-11  0:24   ` Richard Stallman
2003-06-15 15:59 ` Richard Stallman

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=E19L1Og-0002IM-Oi@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=handa@m17n.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).