From: Karl Voit <devnull@Karl-Voit.at>
Subject: Re: Publishing only sub-hierarchies with a given tag
Date: Mon, 24 Dec 2012 16:00:32 +0100 [thread overview]
Message-ID: <2012-12-24T15-56-09@devnull.Karl-Voit.at> (raw)
* Bastien <firstname.lastname@example.org> wrote:
> Hi Karl,
> Karl Voit <devnull@Karl-Voit.at> writes:
>> The publishing methods are quite capable. I wonder whether or not it
>> is possible (or easy to implement) to limit content to
>> sub-hierarchies that are tagged for publishing.
>> So if I have multiple Org-mode files in «base-directory», publish
>> only the (few) things that are tagged with e.g. «:publish:».
> Can't you achieve (part of) this with :export: and :noexport: ?
In theory you are probably right.
But in practice I'd have to tag every heading. Additionally, I want
to use the export/noexport-mechanism independent from publishing for
blogging. And this is my use-case I was referring to.
Anyway. I have to implement my blogging system in Python I guess.
There are too many things I would like to "have it my way" :-)
Let's see, what I can accomplish in the next two months.
next prev parent reply other threads:[~2012-12-24 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 12:54 Publishing only sub-hierarchies with a given tag Karl Voit
2012-12-23 18:00 ` Bastien
2012-12-24 15:00 ` Karl Voit [this message]
2012-12-25 3:20 ` Bastien
2012-12-26 10:05 ` Karl Voit
2013-01-09 15:37 ` Nicolas Goaziou
2013-01-09 15:52 ` Karl Voit
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).