From: Ihor Radchenko <yantar92@posteo.net>
To: Thomas Ingram <thomas@taingram.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Prevent files with excluded FILETAGS from being exported
Date: Mon, 12 Dec 2022 13:37:29 +0000 [thread overview]
Message-ID: <87y1rcg2ue.fsf@localhost> (raw)
In-Reply-To: <87zgbzrs0t.fsf@taingram.org>
Thomas Ingram <thomas@taingram.org> writes:
> Currently when trying to export an org file with FILETAGS set to
> "noexport" (or any value in `org-export-exclude-tags') the file is still
> exported with the title and top level text. I propose that be changed
> so files with FILETAGS in `org-export-exclude-tags' are completely
> skipped by the exporter.
> This would be extremely useful in combination with ox-publish, as it
> would allow users to easily exclude files from publishing from within
> the file. Currently this can only be done by adjusting the ':exclude'
> value to match the filename in the `org-publish-project-alist' settings.
With current implementation, `org-export-exclude-tags' does not imply
that nothing is done during export. Source blocks inside excluded
subtrees are still executed, for example. The trees are only removed
from the exported Org AST after all the pre-processing is completed,
giving user a chance to set noexport tags dynamically.
In-buffer export settings are also applied, even when set inside
noexport trees.
So, producing an output even when everything is excluded is logically
expected. At least, in a form of empty export template.
That said, I do think that it will make sense to exclude top-level
section if #+FILETAGS contain :noexport:.
In addition, we can introduce a new export option that will make Org
skip exporting empty files (empty after pre-processing).
Then, you will be able to get the described publishing behaviour.
--
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>
prev parent reply other threads:[~2022-12-12 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 17:43 Prevent files with excluded FILETAGS from being exported Thomas Ingram
2022-12-12 13:37 ` 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=87y1rcg2ue.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=thomas@taingram.org \
/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).