Ihor Radchenko <yanta...@gmail.com> writes: > Profiler reports after C-g are not reliable.
TIL! > In addition to debug-on-quit, you can M-x debug-on-entry org-export-as > and try to identify which part of that function is lagging. I tried it and it says ... Debugger entered--entering a function: * org-export-as(html nil nil nil (:output-file "notebook.html")) org-export-to-file(html "notebook.html" nil nil nil nil nil) org-html-export-to-html(nil nil nil nil) (org-open-file (org-html-export-to-html nil s v b)) (if a (org-html-export-to-html t s v b) (org-open-file (org-html-export-to-html nil s v b))) (lambda (a s v b) (if a (org-html-export-to-html t s v b) (org-open-file (org-html-export-to-html nil s v b))))(nil nil nil nil) org-export-dispatch(nil) funcall-interactively(org-export-dispatch nil) call-interactively(org-export-dispatch nil nil) command-execute(org-export-dispatch) ... and then just "Continuing." and nothing else. I waited for more than 3 minutes. Rudy -- "The whole science is nothing more than a refinement of everyday thinking." -- Albert Einstein, 1879-1955 Rudolf Adamkovič <salu...@me.com> [he/him] Studenohorská 25 84103 Bratislava Slovakia
