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)
     *
byte-code("\300\301!\210\300\302!\210\303\304\305\306\307\310\311\312&\7\207"
[require doc-view ol org-link-set-parameters "docview" :follow
org-docview-open :export org-docview-export :store org-docview-store-link]
8)
     * require(doc-view)
     *
byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\305\306\307\310\311\312\313\314\315\316\315\317\315\320\321\322&\17\210\323\324\325\326\327DD\330\331\332\313\333&\7\210..."
[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,
Aaron

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
>