From: Richard G Riley <rileyrgdev@googlemail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: org-mode <emacs-orgmode@gnu.org>,
Richard G Riley <rileyrgdev@googlemail.com>
Subject: Re: exporting - filtering
Date: Mon, 15 Sep 2008 12:57:15 +0200 [thread overview]
Message-ID: <q51vzly8vo.fsf@development.richardriley.net> (raw)
In-Reply-To: <AC5ADD0B-09A0-4244-BABF-32D00E155F21@uva.nl> (Carsten Dominik's message of "Mon, 15 Sep 2008 10:22:48 +0200")
Carsten Dominik <dominik@science.uva.nl> writes:
> Hi Richard,
>
> On Jul 22, 2008, at 1:06 AM, Richard G Riley wrote:
>
>>
>> When publishing/exporting can I limit certain sections to only
>> exported
>> if they are tagged for export? e.g I have a normal org mode hierarchy
>> for my web page but then import a task based org file and then only
>> have
>> some of those published? If not I think it would be nice addition some
>> time in the future.
>
> I have finally been able to get to this message, and I am wondering
> what the logic should be. I think it is rather straight forward to
> mark subtrees that should be *excluded* from export. You can, in
> fact, already do so by starting a tree with the COMMENT keyword, which
How does this affect agenda generation?
> has exactly this purpose. Granted, a tag or property might be more
> appropriate - the fact that it is a keyword at the beginning of the
> entry has more historic than practical reasons.
>
> The logic for only selecting some trees for inclusion is harder, if
> you think about subtrees that are not top-level. If you mark a level
> 5 subtree for export, what should happen to the hierarchy above it?
> his can get quickly very complex, so I was wondering if you have been
> thinking about a reasonable logic for this.
The way I personally see the html export is for publication of facts,
figures and ideas. And I tend to find very few of my entries in my org
files are of enough quality in terms of content and format to be
published.
Assuming we mark/tag for export and to answer your final question:
If you mark a level five level item for export then you simply export
all headers for its level the other levels before hand.
Tagging for export is nice since you can have a section where the top
level is tagged for export and all items inherit it too. So two tags
would be ideal export and no_export (or something more ORGish since you
might with to temporarily repress the publication of certain items in an
exported block (all tagged as export thanks to the tags inheritance
mechanism).
> - Carsten
--
next prev parent reply other threads:[~2008-09-15 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 23:06 exporting - filtering Richard G Riley
2008-07-21 23:20 ` Russell Adams
2008-07-21 23:36 ` Richard G Riley
2008-07-23 23:22 ` Carsten Dominik
2008-09-15 8:22 ` Carsten Dominik
2008-09-15 10:57 ` Richard G Riley [this message]
2008-09-16 12:07 ` Carsten Dominik
2008-09-17 11:49 ` Carsten Dominik
2008-09-17 12:42 ` Giovanni Ridolfi
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=q51vzly8vo.fsf@development.richardriley.net \
--to=rileyrgdev@googlemail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.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).