From: Ihor Radchenko <email@example.com>
To: Aaron Rea <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>, "Shibu N.V" <email@example.com>,
Subject: Re: Bug: Failed to render org file during first load on buffer emacs 27.1 windows binaries [9.3 (release_9.3 @ c:/ProgramFilesh/emacs-27.1-x86_64/share/emacs/27.1/lisp/org/)]
Date: Sat, 22 May 2021 21:33:48 +0800 [thread overview]
Message-ID: <878s46q4eb.fsf@localhost> (raw)
Aaron Rea <firstname.lastname@example.org> writes:
> As for the org version, I hit this issue even when running it out of the
I recall exactly same issue reported some time ago on Reddit. It appears
to be very rare and hard to debug from our side.
> Is there perhaps a different set of windows binaries I should be
I believe that you should have no problem if you use Linux subsystem and
install Linux version of Emacs there.
> Or is there a way to run a stack trace on the entire emacs session?
> It's not running into any actual error so debug isn't yielding anything.
If you are willing to debug it, I suggest running
1. M-x debug-on-entry <RET> org-mode <RET>
2. Opening the file (first time)
3. Stepping through debugger to figure out what part of the org-mode
startup is triggering the problem. See 19.1.8 Debugger Commands
section of the Emacs manual for guide how to use the debugger.
Hope it helps.
next prev parent reply other threads:[~2021-05-22 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 5:30 Bug: Failed to render org file during first load on buffer emacs 27.1 windows binaries [9.3 (release_9.3 @ c:/ProgramFilesh/emacs-27.1-x86_64/share/emacs/27.1/lisp/org/)] Aaron
2021-05-21 12:35 ` Ihor Radchenko
2021-05-21 14:34 ` Jeremie Juste
2021-05-21 15:08 ` Shibu N.V
2021-05-21 18:54 ` Aaron Rea
2021-05-22 13:33 ` Ihor Radchenko [this message]
2021-06-01 5:27 ` Aaron Rea
-- strict thread matches above, loose matches on Subject: below --
2020-09-17 7:56 Shibu N.V
2020-09-18 3:56 ` Ihor Radchenko
2020-09-18 4:38 ` Shibu N.V
2020-09-18 6:27 ` Ihor Radchenko
2020-09-18 11:26 ` Shibu N.V
2020-09-23 7:28 ` Bastien
2020-09-23 12:42 ` Palak Mathur
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).