From: Ihor Radchenko <yantar92@posteo.net>
To: Nikolaos Chatzikonstantinou <nchatz314@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Some hacks on top of org-publish
Date: Fri, 27 Dec 2024 17:32:49 +0000 [thread overview]
Message-ID: <874j2p58vy.fsf@localhost> (raw)
In-Reply-To: <CAAQmekdGjp2KOFJcGzpRHEGOM4CQacRh3DS-39UK=jKr5OvusA@mail.gmail.com>
Nikolaos Chatzikonstantinou <nchatz314@gmail.com> writes:
>> > Finally a highlight of the hacks I had to pull off: apparently
>> > #+INCLUDE: will strip away inline backend information such as
>> > @@html:<b>@@. I figured out that if I write something like
>> > @@html@@a:@@:<b>@@, only the inner @@a:@@ is recognized and stripped,
>> > which leaves me with what I originally wanted! (see
>> > <https://github.com/createyourpersonalaccount/blog-v2/blob/main/content/publish.el#L14-L20>)
>>
>> May you show more concrete example?
>> #+INCLUDE by itself does not remove export snippets.
>
> It must not be #+INCLUDE then, but sitemap.org generation itself, I
> misremembered when I wrote the e-mail. Here's a reproducer, see
> attachment. Have this index.org file in its own directory and publish
> it. Then view public/sitemap.html. You will see that the @@BACKEND:@@
> stuff has been stripped away in the first sitemap entry instance,
> while in the second it is there. When inspecting the generated
> sitemap.org you will see the following line:
I see.
What happens here is double export:
1. The default `org-publish-sitemap-default' first exports the sitemap
items to Org file
2. The resulting Org file is exported to html
During the first step, @@html:...@@ is stripped because we export to
org.
You may want to use a custom :sitemap-function.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
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>
prev parent reply other threads:[~2024-12-27 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 17:45 Some hacks on top of org-publish Nikolaos Chatzikonstantinou
2024-12-25 13:48 ` Ihor Radchenko
2024-12-26 15:48 ` Nikolaos Chatzikonstantinou
2024-12-27 17:32 ` Ihor Radchenko [this message]
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=874j2p58vy.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=nchatz314@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).