Ihor Radchenko writes:
> Thanks!
> Now applied onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=192742c9c5a4c6a1470674343a09e5ba1f1bc440
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8901fd2261a8a16917b32eb9e43c7ea43b51
Thank you for all your h
Rudolf Adamkovič writes:
>> (I'd like this patches to be tested on real export first as it is
>> touching on very basic export routines).
>
> For what is worth, I have tried the patch. With the patch, Org exports
> my elaborate notebook as fast as without it (+/- 1 second) and the tests
> pass o
Ihor Radchenko writes:
> The patch is only working by accident because [...]
TIL!
> (I'd like this patches to be tested on real export first as it is
> touching on very basic export routines).
For what is worth, I have tried the patch. With the patch, Org exports
my elaborate notebook as fast
Rudolf Adamkovič writes:
>>> (1) re-opening the file after export always re-opens it, and
>>
>> I am not sure how to test this part.
>
> How about the attached patch?
>
> It mirrors the manual steps (find-file, export, kill-buffer, find-file),
> except it calls just the 'org-export-copy-buffer' p
Ihor Radchenko writes:
> I do not see how it is related. Do you see the error with your config
> or with clean Emacs?
Good point. Just with my config. Ignoring for now!
> Oops. Another side-effect of `buffer-file-name'. Fixed now.
Thank you!
>> (2) no corruption happens to the original fil
Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> Rudolf, please kindly confirm that the export performance is back to
>> satisfactory on the latest main.
>
> Performance back to normal! Though, I noticed two issues.
>
> *** ISSUE 1: Error when exporting. ***
>
> While exporting, I see the
Ihor Radchenko writes:
> Rudolf, please kindly confirm that the export performance is back to
> satisfactory on the latest main.
Performance back to normal! Though, I noticed two issues.
*** ISSUE 1: Error when exporting. ***
While exporting, I see the error:
"Org mode fontification error in
After further off-list discussion and online debugging, we have managed
to find out the culprit.
Thanks, Rudolf, for the kind assistance with debugging!
The slowdown mostly came from the new version of `org-html-format-latex'
that copies the parent Org buffer environment when generating LaTeX
i
Ihor Radchenko writes:
> Can you execute [...] after loading org and try exporting again?
* EXPERIMENT 1 - TREATMENT *
*** VERSIONS:
- Emacs 29 (adaa2fc90e)
- Org (ebbc2ffaa)
*** CONFIGURATION:
;;; -*- lexical-binding: t; -*-
;;; .ema
Rudolf Adamkovič writes:
>> May you try with Emacs version that is not bleeding edge? Like Emacs
>> 28.
>
> So, I did the following:
>
> + removed Emacs 29
> + installed Emacs 28.2
> ...
> + waited for 1 minute and 35 seconds
> + saved 'emacs-28-org-export.profile'
Thanks!
Can you execute
(def
Rudolf Adamkovič writes:
> All right, I did the following 10 experiments.
Thanks again!
> RESULT:
>
> Exporting crashes Emacs.
*shrug*
May you try with Emacs version that is not bleeding edge? Like Emacs 28.
> *
> *** EXPERIMENT 10 ***
> *
>
> CONFIG
Rudolf Adamkovič writes:
> UPDATE.
>
> I tried exporting again (after some document clean up; most probably
> unrelated); and I found that exporting sometimes works!
>
> Four attempts, chronologically:
>
> 1. New Org, nil cache + core overlays -- 3 minutes 21 seconds
> 2. New Org -- 3 minutes 22
Rudolf Adamkovič writes:
> No luck!
UPDATE.
I tried exporting again (after some document clean up; most probably
unrelated); and I found that exporting sometimes works!
Four attempts, chronologically:
1. New Org, nil cache + core overlays -- 3 minutes 21 seconds
2. New Org -- 3 minutes 22 sec
Ihor Radchenko writes:
Thank you for helping me, Ihor.
> Let's try to approach this problem from another direction.
>
> Can you please set org-element-use-cache to nil and org-fold-core-style
> to 'overlays in your config and try the export again?
No luck! I used the following configuration in
On 28/09/2022 19:55, Rudolf Adamkovič wrote:
Rudolf Adamkovič writes:
Also, I forgot to mention that Org mode from Org/Git 'main' quietly
deletes all COMMENT headings from my notebook, including their content
(!), and inlines all macros. I have no idea why, but if I did not use
Git, I would hav
Rudolf Adamkovič writes:
Also, I forgot to mention that Org mode from Org/Git 'main' quietly
deletes all COMMENT headings from my notebook, including their content
(!), and inlines all macros. I have no idea why, but if I did not use
Git, I would have lost important data. Scary!
Rudy
--
"I lo
Ihor Radchenko writes:
Thank you for helping me out.
Context:
With all this talk about Emacs 29 around the corner, I became scared
that the upcoming Org will render my Org notes unusable. Hence, I
decided to ask now, before it happens.
> Can you
> 1. M-x debug-on-entry org-export--generate-c
Rudolf Adamkovič writes:
> Rudolf Adamkovič writes:
>
> Also, I forgot to mention that Org mode from Org/Git 'main' quietly
> deletes all COMMENT headings from my notebook, including their content
> (!), and inlines all macros. I have no idea why, but if I did not use
> Git, I would have lost i
Rudolf Adamkovič writes:
>> Can you
>> 1. M-x debug-on-entry org-export--generate-copy-script
>> 2. Start export
>> 3. Step into the function (use "d", not "c" binding)
>> 4. Try to identify which part (if any) is being slow
>
> FYI: I had to do "(require 'ox)" before this worked.
>
> I spent a
Rudolf Adamkovič writes:
> "Fraga, Eric" writes:
>
>> Try M-x toggle-debug-on-quit RET and then export, hitting C-g when it
>> gets stuck. That'll give you a backtrace which might help debug this.
>
> Thank you Eric. I tried it and stopped after more than 3 minutes of
> waiting. The output:
>
Ihor Radchenko 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(h
"Fraga, Eric" writes:
> Try M-x toggle-debug-on-quit RET and then export, hitting C-g when it
> gets stuck. That'll give you a backtrace which might help debug this.
Thank you Eric. I tried it and stopped after more than 3 minutes of
waiting. The output:
;; Debugger entered--Lisp error: (qui
Rudolf Adamkovič writes:
> When I attach the profiler before exporting and then abort with C-g, the
> profiler reports that Org spends almost all of the time in
> 'org-export--generate-copy-script'.
Profiler reports after C-g are not reliable.
> Any ideas?
In addition to debug-on-quit, you can
On Sunday, 25 Sep 2022 at 18:40, Rudolf Adamkovič wrote:
> When I attach the profiler before exporting and then abort with C-g, the
> profiler reports that Org spends almost all of the time in
> 'org-export--generate-copy-script'.
Try M-x toggle-debug-on-quit RET and then export, hitting C-g when
Hello smart people!
The Org mode from Git does not export my notebook, while the Org mode
that comes with Emacs 29 does. Is that normal? My 1.6 MB notebook
contains 2078 headings and lots of prose, mathematics, code, citations,
tables, ... virtually everything.
The minimal configuration used fo
25 matches
Mail list logo
