From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: info@protesilaos.com, 48714@debbugs.gnu.org
Subject: bug#48714: 28.0.50; Inconsistent font after theme modus-operandi upgrade
Date: Sat, 29 May 2021 15:48:16 +0530 [thread overview]
Message-ID: <m2im31yhav.fsf@codeisgreat.org> (raw)
In-Reply-To: <831r9p7w4g.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 May 2021 12:00:15 +0300")
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
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.
[-- Attachment #2: init-err.el --]
[-- Type: application/emacs-lisp, Size: 1231 bytes --]
next prev parent reply other threads:[~2021-05-29 10:18 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 [this message]
2021-05-29 11:54 ` Protesilaos Stavrou
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=m2im31yhav.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=48714@debbugs.gnu.org \
--cc=eliz@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).