emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#52905: closed (29.0.50; "fixed-pitch" face doesn't respect the font


From: GNU bug Tracking System
Subject: bug#52905: closed (29.0.50; "fixed-pitch" face doesn't respect the font in "default-frame-alist")
Date: Sat, 01 Jan 2022 20:34:01 +0000

Your message dated Sat, 01 Jan 2022 12:32:53 -0800
with message-id <87k0fj9ox9.fsf@secretsauce.net>
and subject line Re: bug#52905: 29.0.50; "fixed-pitch" face doesn't respect the 
font in "default-frame-alist"
has caused the debbugs.gnu.org bug report #52905,
regarding 29.0.50; "fixed-pitch" face doesn't respect the font in 
"default-frame-alist"
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52905: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52905
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 29.0.50; "fixed-pitch" face doesn't respect the font in "default-frame-alist" Date: Thu, 30 Dec 2021 12:17:44 -0800
Hi. I'm running a very recent emacs snapshot from 2021/12/19:
0bc2900bbcb. I'm on Debian GNU/Linux, using the GTK-based build on X.

In the last few months I've been observing some font handling updates in
emacs that cause an inconsistency with the way things are displayed. As
suggested by the emacs documentation, I set the font I want by touching
default-frame-alist. The docs are here:

  https://www.gnu.org/software/emacs/manual/html_node/emacs/Fonts.html

I've had this setting in my .emacs for many years. Today this isn't
respected everywhere. A recipe:

  emacs -Q --eval \
  "(progn
     (setf (alist-get 'font default-frame-alist)
       \"-adobe-courier-medium-r-*-*-14-*-*-*-*-*-iso8859-*\")
   (org-mode)
   (insert \"abc\\n#+begin_\"))"

Here I start up emacs without .emacs, but with some default-frame-alist
setting. I enter org-mode and insert some text.

Invoking C-u C-x = on any of "abc" tells me that no particular face is
active there, and that my default font is being used.

Invoking C-u C-x = on any of "#+begin_" tells me that the org-meta-line
face is active there. This face ultimately derives from the fixed-pitch
face, which uses a different monospace font: ftcrhb:-Bits-Bitstream Vera
Sans Mono-regular-normal-normal-*-14-*-*-*-m-0-iso10646-1.

But I already selected a monospaced font in default-frame-alist, so I
expect to get the same font here, which was the case for many years. The
fixed-pitch face is defined like this in faces.el:

  (defface fixed-pitch
    '((t :family "Monospace"))
    "The basic fixed-pitch face."
    :group 'basic-faces)

I can "fix" this by resetting the fixed-pitch face to use the default:

  (defface fixed-pitch
    '((t))
    "The basic fixed-pitch face."
    :group 'basic-faces)


So is this a "bug"? Is this a documentation problem? Setting the default
font to a monospace font, as described by the emacs docs should end up
being picked up by the fixed-pitch face.

Thanks!



--- End Message ---
--- Begin Message --- Subject: Re: bug#52905: 29.0.50; "fixed-pitch" face doesn't respect the font in "default-frame-alist" Date: Sat, 01 Jan 2022 12:32:53 -0800 User-agent: mu4e 1.6.10; emacs 29.0.50
Eli Zaretskii <eliz@gnu.org> writes:

> Yes, I think it is fine to see 2 different fonts in this case. Once
> again, the reason is that the fixed-pitch face specifies its own font.

Alright. I'll fix this on my end. I'm closing the issue. Thanks for
discussing it.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]