emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Rea <area@alumni.nd.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "bzg@gnu.org" <bzg@gnu.org>, "Shibu N.V" <nvshibuse@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	"palakmathur@gmail.com" <palakmathur@gmail.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: Tue, 1 Jun 2021 00:27:21 -0500	[thread overview]
Message-ID: <CAKPXLbtS=y_8LaT43zpkZeNrU7n4JNgYPKnws=0nPoDom1TroA@mail.gmail.com> (raw)
In-Reply-To: <878s46q4eb.fsf@localhost>

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

Hello everyone,

I wanted to thank you guys for your guidance.
I was able to trace the issue through the debugger this far (27.2 binaries):
     * org-mode()
     * apply(#f(compiled-function () (interactive nil) #<bytecode
0x24511a1>) nil)
     * #f(compiled-function () (interactive nil) #<bytecode 0x24511a1>)
nil) ()
     * org-load-modules-maybe()
     * require(ol-docview)
[require doc-view ol org-link-set-parameters "docview" :follow
org-docview-open :export org-docview-export :store org-docview-store-link]
     * require(doc-view)
[require cl-lib dired image-mode jka-compr custom-declare-group doc-view
nil "In-buffer viewer for PDF, PostScript, DVI, and DJV..." :link
(function-link doc-view) :version "22.2" :group applications data
multimedia :prefix "doc-view-" custom-declare-variable
doc-view-ghostscript-program funcall function #f(compiled-function ()
#<bytecode 0x27ff6cd>) "Program to convert PS and PDF files to PNG." :type
file "27.1" doc-view-pdfdraw-program #f(compiled-function () #<bytecode
0x27ff6e5>) "Name of MuPDF's program to convert PDF files to PN..." "24.4"
doc-view-pdftotext-program-args #f(compiled-function () #<bytecode
0x27ff6f1>) "Parameters to give to the pdftotext command." (repeat string)
doc-view-pdf->png-converter-function #f(compiled-function () #<bytecode
0x27ff709>) "Function to call to convert a PDF file into a PNG ..." (radio
(function-item doc-view-pdf->png-converter-ghostscript :doc "Use
ghostscript") (function-item doc-view-pdf->png-converter-mupdf :doc "Use
mupdf") function) doc-view-ghostscript-options #f(compiled-function ()
#<bytecode 0x27ff719>) "A list of options to give to ghostscript." (repeat
string) doc-view-ghostscript-device #f(compiled-function () #<bytecode
0x27ff729>) "Output device to give to ghostscript." string
doc-view-resolution #f(compiled-function () #<bytecode 0x27ff739>) ...] 16)

Once I got that far, it started evaluating too quickly for me to catch the
"shell command succeeded with no output".

I was able to create a workaround by adding (require 'ol-docview) to my
.emacs though so everything is at least functional again.
I'll probably try to learn more about debugging to see if I can pinpoint
the exact spot that's acting up but if anyone sees this again I think the
workaround should do fine.

All good things,

On Sat, May 22, 2021 at 8:29 AM Ihor Radchenko <yantar92@gmail.com> wrote:

> Aaron Rea <area@alumni.nd.edu> writes:
> > As for the org version, I hit this issue even when running it out of the
> > box.
> 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
> > using?
> 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.
> Best,
> Ihor

[-- Attachment #2: Type: text/html, Size: 4581 bytes --]

  reply	other threads:[~2021-06-01  5:28 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
2021-06-01  5:27       ` Aaron Rea [this message]
  -- 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

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKPXLbtS=y_8LaT43zpkZeNrU7n4JNgYPKnws=0nPoDom1TroA@mail.gmail.com' \
    --to=area@alumni.nd.edu \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=nvshibuse@gmail.com \
    --cc=palakmathur@gmail.com \
    --cc=yantar92@gmail.com \


* 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).