all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	winkler@gnu.org, 53550@debbugs.gnu.org
Subject: bug#53550: 29.0.50; bitmap fonts
Date: Wed, 26 Jan 2022 13:53:18 -0600	[thread overview]
Message-ID: <87mtjiuvdd.fsf@gnu.org> (raw)
In-Reply-To: <83v8y6fnbg.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Jan 2022 18:56:19 +0200")

On Wed, Jan 26 2022, Eli Zaretskii wrote:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> So Emacs 29 is choosing a "ko" variant for the font?  I guess that's a
>> Russian font?  It sounds like a variation on the other font selection
>> problems we've been seeing on the trunk, which we're still debugging, I
>> think.
>
> Perhaps some side effect of changing the default font from medium to
> regular weight?

All this is not my area of expertise.  For the longest time I have used

  -misc-fixed-medium-r-normal-*-20-*-*-75-*-*-*-*

and it gave me the font I wanted not only with emacs, but also with a
good number of other applications.  (I cannot go back anymore to the old
system that motivated me to pick this.)  Now using debian 10, I have
changed this to

  -misc-fixed-*-*-*-*-20-*-*-*-*-*-*-*

and it seems to work not only with older versions of emacs and other
applications (I need to check this more carefully!), but also Emacs 29
is then picking the font I want.





      reply	other threads:[~2022-01-26 19:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 14:36 bug#53550: 29.0.50; bitmap fonts Roland Winkler
2022-01-26 14:39 ` Lars Ingebrigtsen
2022-01-26 15:10   ` Roland Winkler
2022-01-26 15:23     ` Lars Ingebrigtsen
2022-01-26 15:33       ` Roland Winkler
2022-01-26 16:12         ` Andreas Schwab
2022-01-26 16:59           ` Roland Winkler
2022-01-26 16:56       ` Eli Zaretskii
2022-01-26 19:53         ` Roland Winkler [this message]

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=87mtjiuvdd.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=53550@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 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.