From: "Rudolf Adamkovič" <salutis@me.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "Fraga, Eric" <e.fraga@ucl.ac.uk>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: The Org mode in the Org Git does not export
Date: Fri, 07 Oct 2022 11:10:11 +0200 [thread overview]
Message-ID: <m2k05c579o.fsf@me.com> (raw)
In-Reply-To: <875ygwmc74.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> 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 #<buffer *temp*> at 10"
The error does not bother me, but I mention it in the case it relates to
the next issue.
*** ISSUE 2: Problems re-opening the notebook. ***
Reproduction steps:
1. open 'notebook.org' (C-x C-f ~/notebook.org RET)
2. export to HTML and open (C-c C-e h o)
3. kill the notebook buffer (C-x k RET)
4. re-open notebook (C-x C-f ~/notebook.org RET)
Expected:
'notebook.org' opens
Actual:
*Org HTML Export LaTeX* opens, with the following content:
\begin{align*}
\frac{dy}{dx}
& = y \left( -1 - 2 \tan x - \frac{2x + 1}{x^2 + x + 1} \right)
\\
& = \frac{e^{-x} {\cos}^2 x}{x^2 + x + 1}
\left( -1 - 2 \tan x - \frac{2x + 1}{x^2 + x + 1} \right)
\end{align*}
P.S. The original file remains intact, but given the way we implement
exports in Org, I think we should add two tests to the test suite to
verify that:
(1) re-opening the file after export always re-opens it, and
(2) no corruption happens to the original file after export.
Rudy
--
"Genius is 1% inspiration and 99% perspiration."
-- Thomas Alva Edison, 1932
Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia
next prev parent reply other threads:[~2022-10-07 9:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 16:40 The Org mode in the Org Git does not export Rudolf Adamkovič
2022-09-25 17:06 ` Fraga, Eric
2022-09-27 22:19 ` Rudolf Adamkovič
2022-09-28 3:06 ` Ihor Radchenko
2022-09-28 12:45 ` Rudolf Adamkovič
2022-09-28 12:55 ` Rudolf Adamkovič
2022-09-28 13:24 ` Ihor Radchenko
2022-09-28 15:49 ` Max Nikulin
2022-09-28 13:14 ` Ihor Radchenko
2022-09-28 15:56 ` Rudolf Adamkovič
2022-09-28 17:29 ` Rudolf Adamkovič
2022-09-29 2:30 ` Ihor Radchenko
2022-09-29 13:37 ` Rudolf Adamkovič
2022-09-29 13:56 ` Ihor Radchenko
2022-09-30 12:01 ` Rudolf Adamkovič
2022-10-01 3:02 ` Ihor Radchenko
2022-10-01 18:04 ` Rudolf Adamkovič
2022-10-07 5:31 ` Ihor Radchenko
2022-10-07 9:10 ` Rudolf Adamkovič [this message]
2022-10-07 10:24 ` Ihor Radchenko
2022-10-07 14:18 ` Rudolf Adamkovič
2022-10-09 6:36 ` Ihor Radchenko
2022-10-09 15:29 ` Rudolf Adamkovič
2022-10-10 10:15 ` Ihor Radchenko
2022-10-10 22:08 ` Rudolf Adamkovič
2022-09-26 4:39 ` Ihor Radchenko
2022-09-27 22:30 ` Rudolf Adamkovič
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=m2k05c579o.fsf@me.com \
--to=salutis@me.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).