From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?)
Date: Tue, 27 Dec 2022 14:18:49 +0000 [thread overview]
Message-ID: <87wn6d0w1i.fsf@localhost> (raw)
In-Reply-To: <tnkkpn$11am$1@ciao.gmane.io>
As Max proposed, it may be a good idea to extend the concept of org-lint
to export.
We may unify the LaTeX errors, some errors/warnings potentially signalled
by export backend, and maybe some warnings from org-lint during the
export process. These errors can ideally be displayed just like in
org-lint, with ability to jump to the problematic LoCs in
Org/intermediate file.
This is a medium task and one will need to:
1. Generalize org-lint interactive interface (list of errors) to work
with other code. Extract it into a separate library.
2. Accumulate export issues into a list to be displayed. For example,
broken links can be displayed
3. Make functions like `org-latex-compile' accumulate LaTeX errors as
well. (Optionally) associate LaTeX buffer lines with Org source.
4. Display the list of errors/warnings at the end of successful or
failed export.
Each step if fairly simple, except optional part in 3.
Patches welcome!
Max Nikulin <manikulin@gmail.com> writes:
> ... Exporter may issue warnings, they are
> collected and presented to user in a temporary window with buffer names
> and line numbers as in compilation-minor-mode. The user may see that
> something goes wrong, but if their does not switch to the warnings
> window then it disappears. It would be great if exporters and lint share
> code generating warnings. Another issue that mature development tools
> usually allows to suppress particular warning for a specific line. It
> may be a problem taking into account specific of Org syntax.
>
> As to `org-lint', I believe, it is hard to discover for new users and
> there should be a reason to run it. It easy to forget about it even when
> some problem is faced. It is mentioned in the manual, but
> - https://orgmode.org/manual/Feedback.html does not request to run
> org-lint before reporting a bug
> - `org-submit-bug-report' neither suggest `org-lint' nor runs it as a
> check. Likely it should be suppressed (with appropriate report) for
> large buffers.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-12-27 14:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 21:40 [BUG] ox-html does not export captions of source blocks without language Johan Bolmsjö
2022-12-14 21:51 ` Kaushal Modi
2022-12-14 22:05 ` Johan Bolmsjö
2022-12-15 9:31 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Ihor Radchenko
2022-12-15 10:32 ` Kaushal Modi
2022-12-15 11:32 ` Max Nikulin
2022-12-15 14:29 ` Tim Cross
2022-12-15 15:07 ` Ihor Radchenko
2022-12-17 5:17 ` Tom Gillespie
2022-12-18 1:33 ` Tim Cross
2022-12-17 14:47 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? Max Nikulin
2022-12-18 13:35 ` [BUG] org-latex-src-block-backend is directly used as variable instead of querying export option (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?) Ihor Radchenko
2022-12-18 13:40 ` Timothy
2022-12-21 12:14 ` Ihor Radchenko
2022-12-27 14:18 ` Ihor Radchenko [this message]
2022-12-27 18:39 ` [FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does " Tim Cross
2022-12-17 9:56 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Ihor Radchenko
2022-12-15 13:32 ` Timothy
2022-12-27 14:08 ` [BUG] ox-html does not export captions of source blocks without language Ihor Radchenko
2023-01-16 10:09 ` Ihor Radchenko
2023-01-16 10:31 ` [ANN] orgtbl-fit tbanelwebmin
2023-01-24 19:55 ` Ihor Radchenko
2023-01-25 15:02 ` tbanelwebmin
2023-01-26 10:35 ` Ihor Radchenko
2023-01-26 19:13 ` tbanelwebmin
2023-02-20 10:50 ` Ihor Radchenko
2023-03-01 11:48 ` tbanelwebmin
2023-03-03 15:13 ` Ihor Radchenko
2023-03-05 18:46 ` tbanelwebmin
2023-01-23 13:32 ` [BUG] ox-html does not export captions of source blocks without language Ihor Radchenko
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=87wn6d0w1i.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).