From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: 48714@debbugs.gnu.org
Subject: bug#48714: 28.0.50; Inconsistent font after theme modus-operandi upgrade
Date: Sat, 29 May 2021 17:44:05 +0530 [thread overview]
Message-ID: <m2eedpybxu.fsf@codeisgreat.org> (raw)
In-Reply-To: <87a6odycuo.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Sat, 29 May 2021 14:54:23 +0300")
Protesilaos Stavrou <info@protesilaos.com> writes:
> I could not reproduce this. I saved your file as ".emacs" in a pristine
> environment. Installed the external packages and started Emacs. Then I
> visited the .emacs to get the result in the attached screenshot.
>
> The font family in the screenshot is DejaVu Sans Mono. Could it be that
> this is not a problem with how those packages interact but rather with
> font files that are not available on your system?
>
> Or maybe I have missed something?
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.
next prev parent reply other threads:[~2021-05-29 12:14 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 [this message]
2022-07-15 11:21 ` Lars Ingebrigtsen
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=m2eedpybxu.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=48714@debbugs.gnu.org \
--cc=info@protesilaos.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).