From: Carsten Dominik <carsten.dominik@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Filtering in export hooks
Date: Tue, 6 Sep 2011 11:49:58 +0200 [thread overview]
Message-ID: <74E04FF8-94AD-4A44-AEC1-9D5217317269@gmail.com> (raw)
In-Reply-To: <CAMXnza2AZnamS3X16Jq8SJsekyyiXS69c_jS=mTO6amU+vq26A@mail.gmail.com>
On Sep 6, 2011, at 11:08 AM, suvayu ali wrote:
> Hi Carsten,
>
> On Tue, Sep 6, 2011 at 10:58 AM, Carsten Dominik
> <carsten.dominik@gmail.com> wrote:
>>>
>>> But this only works when tags: is non-nil. Any hints on how I could
>>> achieve something that "works always"?
>>
>> May be I do not understand, but how about
>>
>> (let ((match "tag1|tag2"))
>> (when match
>> (org-map-entries (lambda () (my-preprocess-function))
>> match)))
>>
>
> Sorry after going through my email again I realised it was ambiguous.
> When I say it doesn't work, I don't mean Org throws an error when
> tags:nil is set. The preprocessing gets skipped.
Which of the preprocessing hooks are you using? I am still confused
by your description, maybe you can make a small example and show exactly what works and what does not work?
- Carsten
>
> To restate my intentions more clearly; I want to preprocess headlines
> that match the tags list "tag1|tag2" during latex export irrespective
> of how the tags: option is setup. If this is not possible by a tags
> match, what are my alternatives?
>
>> - Carsten
>
> Thanks a lot. :)
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
- Carsten
next prev parent reply other threads:[~2011-09-06 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 8:49 Filtering in export hooks suvayu ali
2011-09-06 8:58 ` Carsten Dominik
2011-09-06 9:08 ` suvayu ali
2011-09-06 9:49 ` Carsten Dominik [this message]
2011-09-06 10:16 ` suvayu ali
2011-09-06 11:33 ` suvayu ali
2011-09-06 22:39 ` suvayu ali
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=74E04FF8-94AD-4A44-AEC1-9D5217317269@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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).