all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, 57962@debbugs.gnu.org
Subject: bug#57962: 29.0.50; Odd font choices
Date: Fri, 14 Oct 2022 16:00:18 +0300	[thread overview]
Message-ID: <83a65y8srh.fsf@gnu.org> (raw)
In-Reply-To: <87r0za8tbf.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  14 Oct 2022 14:48:20 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: luangruo@yahoo.com,  57962@debbugs.gnu.org
> Date: Fri, 14 Oct 2022 14:48:20 +0200
> 
> >> (defface fixed-pitch
> >>   '((t :family "Monospace" :spacing mono))
> >>   "The basic fixed-pitch face."
> >>   :group 'basic-faces)
> >
> > "No effect" in the sense that if the default face uses a proportional
> > font, fixed-pitch defined as above still uses a proportional font?
> 
> It makes no difference either way, whether `default' uses a fixed-width
> font or not -- the `fixed-pitch' font uses "Monospace", which is a
> fixed-width font.

But it produces a font different from the default face's font, which
AFAIU was what you wanted?  That's what happens for me: if I start
Emacs with "emacs -fn FOO" where FOO is a variable-pitch font, then
using the defface form I suggested makes fixed-pitch use a monospaced
font.

> >   (defface fixed-pitch
> >     `((t :font ,(font-spec :spacing 'M)))
> >     "The basic fixed-pitch face."
> >     :group 'basic-faces)
> 
> That leads to:
> 
> Don't know how to purify: #<font-spec nil nil nil nil nil nil nil nil nil nil 100 nil nil>

I only tried that in a running Emacs session, and with a face whose
name is different from fixed-pitch.  I haven't tried bootstrapping
with the above in faces.el.  I'm sure we can avoid the problem, if the
effect is what we want: for example, we could have the defface in
startup.el or something.





  reply	other threads:[~2022-10-14 13:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 22:16 bug#57962: 29.0.50; Odd font choices Lars Ingebrigtsen
2022-09-21  2:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 10:43   ` Lars Ingebrigtsen
2022-10-14 11:41     ` Lars Ingebrigtsen
2022-10-14 11:53       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:02         ` Lars Ingebrigtsen
2022-10-14 12:05           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:13             ` Lars Ingebrigtsen
2022-10-14 12:20               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:07       ` Eli Zaretskii
2022-10-14 12:18         ` Lars Ingebrigtsen
2022-10-14 12:37           ` Eli Zaretskii
2022-10-14 12:48             ` Lars Ingebrigtsen
2022-10-14 13:00               ` Eli Zaretskii [this message]
2022-10-14 13:06                 ` Lars Ingebrigtsen
2022-10-14 13:09                   ` Eli Zaretskii
2022-10-16 10:58                     ` Lars Ingebrigtsen
2022-10-16 11:17                       ` Eli Zaretskii
2022-10-16 12:19                         ` Lars Ingebrigtsen
2022-10-16 13:53                           ` Eli Zaretskii
2022-10-17  9:57                             ` Lars Ingebrigtsen
2022-10-17 10:22                               ` Eli Zaretskii
2022-10-17 11:35                                 ` Lars Ingebrigtsen
2022-10-17 12:58                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 14:26                                   ` Eli Zaretskii
2022-10-17 14:20                               ` Stefan Kangas
2022-10-17 14:34                                 ` Eli Zaretskii
2022-10-17 15:40                                   ` Stefan Kangas
2022-10-18  0:38                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83a65y8srh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57962@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    /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.