From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44316@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#44316: 26.3; Faces `fixed-pitch' and `fixed-pitch-serif' are opposite what they should be
Date: Sat, 31 Oct 2020 10:51:10 +0200 [thread overview]
Message-ID: <83r1pehj7l.fsf@gnu.org> (raw)
In-Reply-To: <877dr7hlkf.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 30 Oct 2020 14:48:00 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 30 Oct 2020 14:48:00 +0100
> Cc: 44316@debbugs.gnu.org
>
> Stefan Kangas <stefankangas@gmail.com> writes:
>
> > I'm also on Debian bullseye. I wonder what causes the different things
> > we are seeing. Sounds likely that we have different font related
> > packages installed, right?
>
> Yup. This is with "emacs -Q", by the way, which I failed to mention
> the last time, but it seems like I'm getting the same in my normal Emacs.
I think one part of the problem here is that "Mono" family (which is
what fixed-pitch uses) doesn't say whether the result will be with or
without serifs. So you can get a font either with or without the
serifs, depending on what fonts are installed and perhaps also on some
local configuration.
The other part of the problem, which could be Windows-specific, is
that the MS-Windows font back-ends don't know about "Mono Serif"
family. Do you always get a font with serifs when the family is "Mono
Serif"? If so, we could perhaps teach MS-Windows do the same. But
the result might be that both faces get the same font -- are we okay
with that? One place where that could matter is in Info.
next prev parent reply other threads:[~2020-10-31 8:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 21:00 bug#44316: 26.3; Faces `fixed-pitch' and `fixed-pitch-serif' are opposite what they should be Drew Adams
2020-10-29 21:27 ` Drew Adams
2020-10-31 8:52 ` Eli Zaretskii
2020-10-29 22:10 ` Stefan Kangas
2020-10-29 22:22 ` Drew Adams
2020-10-29 22:31 ` Stefan Kangas
2020-10-29 22:50 ` Drew Adams
2020-10-30 0:45 ` Stefan Kangas
2020-10-30 12:55 ` Lars Ingebrigtsen
2020-10-30 13:26 ` Eli Zaretskii
2020-10-30 13:45 ` Stefan Kangas
2020-10-30 13:48 ` Lars Ingebrigtsen
2020-10-31 8:51 ` Eli Zaretskii [this message]
2020-11-01 12:41 ` Lars Ingebrigtsen
2020-11-01 15:27 ` Eli Zaretskii
2020-11-02 15:09 ` Lars Ingebrigtsen
2020-11-02 16:03 ` Eli Zaretskii
2020-11-03 14:36 ` Lars Ingebrigtsen
2020-11-03 15:53 ` Eli Zaretskii
2020-11-05 14:57 ` Lars Ingebrigtsen
2020-11-05 15:39 ` Eli Zaretskii
2020-11-03 15:32 ` Stefan Kangas
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=83r1pehj7l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44316@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@gmail.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 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).