From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: Protesilaos Stavrou <info@protesilaos.com>,
48714@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#48714: 28.0.50; Inconsistent font after theme modus-operandi upgrade
Date: Fri, 15 Jul 2022 13:21:00 +0200 [thread overview]
Message-ID: <87bktqlizn.fsf@gnus.org> (raw)
In-Reply-To: <m2eedpybxu.fsf@codeisgreat.org> (Pankaj Jangid's message of "Sat, 29 May 2021 17:44:05 +0530")
Pankaj Jangid <pankaj@codeisgreat.org> writes:
> This problem could be platform specific. I am on macos. And with older
> version of the theme i.e. older commit from ‘master’ branch of Emacs,
> the fonts were working perfectly fine. So the font files are ok.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
This was a year ago, and skimming this bug report, it's unclear whether
there's anything to be done on the Emacs side, or whether this was just
a local configuration oddity. Are you still seeing this issue in recent
Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-15 11:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 12:43 bug#48714: 28.0.50; Inconsistent font after theme modus-operandi upgrade Pankaj Jangid
2021-05-28 12:55 ` Eli Zaretskii
2021-05-28 13:46 ` Pankaj Jangid
2021-05-28 14:06 ` Eli Zaretskii
2021-05-28 15:49 ` Protesilaos Stavrou
2021-05-29 3:35 ` Pankaj Jangid
2021-05-29 6:57 ` Protesilaos Stavrou
2021-05-29 7:41 ` Pankaj Jangid
2021-05-29 7:56 ` Protesilaos Stavrou
2021-05-29 9:00 ` Eli Zaretskii
2021-05-29 10:18 ` Pankaj Jangid
2021-05-29 11:54 ` Protesilaos Stavrou
2021-05-29 12:14 ` Pankaj Jangid
2022-07-15 11:21 ` Lars Ingebrigtsen [this message]
2022-07-16 3:00 ` Pankaj Jangid
2022-07-16 10:38 ` Lars Ingebrigtsen
2022-07-17 5:27 ` Richard Stallman
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=87bktqlizn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48714@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=info@protesilaos.com \
--cc=pankaj@codeisgreat.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 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).