From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: new exporter / org-element
Date: Thu, 25 Oct 2012 22:37:25 +0200 [thread overview]
Message-ID: <87r4omjnju.fsf@gmail.com> (raw)
In-Reply-To: <871ugm1g6l.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 25 Oct 2012 21:53:54 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> Thanks for the suggestion, but again I'm using this just as an
> example.
I understand, but this example doesn't help, since it can't justify the
need for any additional mechanism you're suggesting.
>> There's already such a mechanism: it's called "filters". I'm just
>> pointing out that, in your situation, it's not worth relying on this
>> kind of tool.
>
> IIUC, you are talking about a mechanism to implement exporters.
Absolutely not. Filters are end-user tools used to tweak output from
back-ends (that is a string to string process).
> I'm vying for a way to syntactically tie stuff that needs to go before
> the element (and maybe wrap around it) so that it's recognized as part
> of that element and not part of another, unrelated element.
That's too vague. It depends on the type of element, the level at which
you want to tie stuff (in Org buffer, in the parse tree, just before
export) and the frequency at which you'll need it.
In most cases, I imagine adding #+LATEX: (or any other appropriate
keyword) around the element is enough.
Regards,
prev parent reply other threads:[~2012-10-25 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 18:54 new exporter / org-element Achim Gratz
2012-10-24 20:39 ` Nicolas Goaziou
2012-10-25 7:14 ` Achim Gratz
2012-10-25 12:18 ` Nicolas Goaziou
2012-10-25 19:53 ` Achim Gratz
2012-10-25 20:37 ` Nicolas Goaziou [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=87r4omjnju.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@nexgo.de \
--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).