From: Carsten Dominik <carsten.dominik@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: [Orgmode] Re: Automatic noexport tag based on rules?
Date: Tue, 29 Mar 2011 23:15:45 +0200 [thread overview]
Message-ID: <22D23BD3-D73D-45F7-B7A5-E34BBD6E9788@gmail.com> (raw)
In-Reply-To: <62A8413A-58B4-4566-9717-859DC7CBAE45@gmail.com>
On 29.3.2011, at 23:05, Carsten Dominik wrote:
>
> On 29.3.2011, at 20:40, Matt Lundin wrote:
>
>> John Hendy <jw.hendy@gmail.com> writes:
>>
>>> On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales <samologist@gmail.com> wrote:
>>>> That is indeed an excellent solution if you want to add a tag for a
>>>> todo kw. However, I wonder if there is a direct approach, where the
>>>> exporter simply does not export if it is a certain todo kw. Is the
>>>> solution to have the exporter delete anything with that todo kw? Or
>>>> is there a way to have it skip?
>>>
>>> I think that was Carsten's suggestion a bit back, but I'm not sure. I
>>> think I asked if it was just deleting as it channeled through the
>>> export function but didn't get a response. Looking back, though, I'm
>>> sure that's what it was and my question was probably a bit silly :)
>>
>> You are correct. The export hook that Carsten provided deletes items in
>> a temporary buffer, not in your org files. In fact, you can use the
>> export hooks to do almost anything to this temporary buffers before they
>> are exported; your original org files will not be touched.
>>
>>> And yes, I have turned this off as I find adding :noexport: to ever
>>> todo in addition to whatever tags I already use to ID the project/task
>>> is annoying and ugly. I've toyed with simply having a * Tracking
>>> headline at the beginning of each file where I dump todos via capture
>>> and track time and then having that have a top level noexport tag to
>>> take care of things. That's pretty much nice, but I still like todos
>>> created during meeting minutes or in the context of some other project
>>> notes to stay where they make sense rather than separating them from
>>> their location and putting them elsewhere.
>>>
>>> So.... I've got some solutions but am not quite happy yet. I should
>>> re-visit Carsten's solution to strip it on export. That would probably
>>> be the ticket.
>>
>> Yes, that would be the easiest solution, requiring no additional
>> markup.
>
> I have a good patch for this lined up - will check it in tomorrow.
In fact, I just now pushed it.
To export without DONE tasks, use
#+OPTION: donetasks:nil
- Carsten
next prev parent reply other threads:[~2011-03-29 21:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 0:29 Automatic noexport tag based on rules? John Hendy
2011-02-09 1:58 ` Jeff Horn
2011-02-09 2:39 ` John Hendy
2011-02-09 2:53 ` Jeff Horn
2011-02-09 7:40 ` Eric S Fraga
2011-02-09 15:18 ` John Hendy
2011-02-09 16:58 ` John Hendy
2011-02-09 18:13 ` Nicolas Goaziou
2011-02-09 18:46 ` John Hendy
2011-02-09 9:36 ` Automatic noexport tag based on rules? (and a possible bug) Nick Dokos
2011-02-11 8:34 ` Automatic noexport tag based on rules? Carsten Dominik
2011-02-11 15:33 ` John Hendy
2011-02-25 22:37 ` John Hendy
2011-03-27 19:37 ` [Orgmode] " Samuel Wales
2011-03-27 20:10 ` John Hendy
2011-03-29 18:40 ` Matt Lundin
2011-03-29 21:05 ` Carsten Dominik
2011-03-29 21:15 ` Carsten Dominik [this message]
2011-03-29 21:48 ` John Hendy
2011-03-29 22:49 ` Carsten Dominik
2011-03-29 22:50 ` John Hendy
2011-03-30 3:30 ` Carsten Dominik
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=22D23BD3-D73D-45F7-B7A5-E34BBD6E9788@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).