unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: Pankaj Jangid <pankaj@codeisgreat.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 48714@debbugs.gnu.org
Subject: bug#48714: 28.0.50; Inconsistent font after theme modus-operandi upgrade
Date: Sat, 29 May 2021 14:54:23 +0300	[thread overview]
Message-ID: <87a6odycuo.fsf@protesilaos.com> (raw)
In-Reply-To: <m2im31yhav.fsf@codeisgreat.org>

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

On 2021-05-29, 15:48 +0530, Pankaj Jangid <pankaj@codeisgreat.org> wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Note that "emacs -Q -l test.el" is NOT the same as having the contents
>> of text.el be the only stuff in your ~/.emacs init file.  So for the
>> definitive evidence try "emacs" without -Q and have your .emacs have
>> only the above as its contents.
>
> Thanks Eli. I could now isolate the problem by copying my big init.el
> bit by bit. Here is the file that reproduces the issue. It is the
> combination of the modus-theme, org-mode and the external package
> org-mime. If any one of the blocks is disabled, Emacs works fine.
>
> Note: I am using use-package for managing external packages.
>
> [...]

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?

-- 
Protesilaos Stavrou
https://protesilaos.com

[-- Attachment #2: Screenshot_2021-05-29_14-44-17.png --]
[-- Type: image/png, Size: 134852 bytes --]

  reply	other threads:[~2021-05-29 11:54 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 [this message]
2021-05-29 12:14                   ` Pankaj Jangid
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=87a6odycuo.fsf@protesilaos.com \
    --to=info@protesilaos.com \
    --cc=48714@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).