From: Marcin Borkowski <mbork@mbork.pl>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: How to export to the simplest possible HTML?
Date: Sat, 24 Jun 2023 15:25:14 +0200 [thread overview]
Message-ID: <87v8fd6lhh.fsf@mbork.pl> (raw)
In-Reply-To: <87ttvpkkks.fsf@localhost>
On 2023-06-03, at 10:37, Ihor Radchenko <yantar92@posteo.net> wrote:
> Marcin Borkowski <mbork@mbork.pl> writes:
>
>>> You can loop over links in the exported subtree and export any extra if
>>> necessary. For example, in the `org-export-filter-parse-tree-functions'.
>>
>> Interesting. The main problem with it is that the docstring is rather
>> concise and I don't understand it well enough to use it.
>
> Org export passes the actual parsed and filtered AST that will be
> exported to `org-export-filter-parse-tree-functions'. You can modify and
> traverse the parse tree as you need.
Yeah, that I do understand. Problem is, I don't know how the AST is
structured, what functions operate on it etc. I am aware that I could
learn all of that from the source and experimenting, but it would
probably be a bit time-consuming, and other ways turned out to be much
easier (which means better for me – I want something simple).
As an aside, inspecting deeply nested structures in Elisp seems a pain
in the neck. Does anyone know a good method of interactively inspecting
them? My usual approach (Edebug) is next to useless when the value
displayed in the minibuffer is a deeply nested list with dozens or
hundreds of elements at different levels...
TIA,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-06-24 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 3:47 How to export to the simplest possible HTML? Marcin Borkowski
2023-05-30 6:21 ` Ihor Radchenko
2023-05-30 18:45 ` Marcin Borkowski
2023-06-03 3:36 ` Marcin Borkowski
2023-06-03 5:08 ` Ihor Radchenko
2023-06-03 6:24 ` Marcin Borkowski
2023-06-03 8:37 ` Ihor Radchenko
2023-06-24 13:25 ` Marcin Borkowski [this message]
2023-06-24 13:34 ` Ihor Radchenko
2023-06-24 13:48 ` Marcin Borkowski
2023-05-30 15:32 ` Max Nikulin
2023-05-30 18:48 ` Marcin Borkowski
2023-06-08 15:18 ` Thomas Redelberger
2023-06-24 15:04 ` Max Nikulin
2023-06-25 19:56 ` Marcin Borkowski
2023-06-27 11:00 ` Max Nikulin
2023-06-28 9:03 ` Marcin Borkowski
-- strict thread matches above, loose matches on Subject: below --
2023-06-10 8:25 Thomas Redelberger
2023-06-24 13:16 ` Marcin Borkowski
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=87v8fd6lhh.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).