all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Font setting issue in recent emacs dev version
Date: Sat, 29 Oct 2022 19:35:37 +1100	[thread overview]
Message-ID: <86ilk39euq.fsf@gmail.com> (raw)
In-Reply-To: <87ilk32gly.fsf@yahoo.com>


Po Lu <luangruo@yahoo.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> The only change since 83fbda715973f57dc49fe0 that could be somehow
>> relevant is the one that touches the support for XSETTINGS on some
>> configurations.  (If you had reported this as a bug, the bug report
>> would have included the details of your configuration, and I could
>> then see if those changes could be relevant, instead of
>> hypothesizing.)  If that is indeed the offending changeset, then I
>> guess the issue has something to do with your system-wide font
>> settings.
>>
>> In any case, bisection would be appreciated.
>
> Indeed.  If you haven't changed your display scale settings with Emacs
> running, I fail to see how the xsettings changes could be related.

This has turned out a little intriguing.

Based on Eli's suggestion it could be a local X setting issue, I
rebooted and ran 'fc-cache -v' and the issue seems to have gone away.

It would seem that something which has changed between revision
83fbda715973f5 and revision ce527464440ca070e752c has made Emacs more
'sensitive' to local font settings issues. Unfortunately, there is
nothing in the messages buffer or journalctl logs which sheds any light
on what the underlying issue was. 

Prior to the reboot, Emacs from the earlier revision had no problems
loading the font I was requesting (it is a font installed within the
user's local font directory).  However, later revisions failed and fell
back to a Noto font. I was able to reproduce this behaviour reliably
using an init.el file which only had the set-face-attribute setting.

Since the reboot and running of fc-cache, I can no longer reproduce the
issue, so I guess it will remain an unexplained mystery. 



      reply	other threads:[~2022-10-29  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29  3:10 Font setting issue in recent emacs dev version Tim Cross
2022-10-29  6:50 ` Eli Zaretskii
2022-10-29  7:20   ` Tim Cross
2022-10-29  8:12   ` Po Lu
2022-10-29  8:35     ` Tim Cross [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=86ilk39euq.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.