From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: "François Pinard" <pinard@iro.umontreal.ca>,
"Org Mode Mailing List" <emacs-orgmode@gnu.org>
Subject: Re: Export to Texinfo
Date: Fri, 20 Jul 2012 15:42:27 +0200 [thread overview]
Message-ID: <87a9yupn0c.fsf@gmail.com> (raw)
In-Reply-To: <CAEWDx5dA1J07x2f4QhcT75hm0CJZ43hucMBO6_EaQ1yf9Pk+1g@mail.gmail.com> (Jonathan Leech-Pepin's message of "Fri, 20 Jul 2012 09:34:37 -0400")
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> Can I define the export-snippet using:
>
> (add-to-list 'org-export-snippet-translation-alist
> '("e-info" . "e-texinfo"))
>
> Or should that be left up to the discretion of the user?
This is an user-oriented variable (customizable).
Though, you have full control over which export snippets you accept. In
the following example, you accept both @@info:...@@ and @@texinfo:...@@
snippets:
(defun org-e-latex-export-snippet (export-snippet contents info)
"Blah..."
(when (memq (org-export-snippet-backend export-snippet) '(info texinfo))
(org-element-property :value export-snippet)))
Just specify it in package's documentation.
next prev parent reply other threads:[~2012-07-20 13:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 0:29 Export to Texinfo Jonathan Leech-Pepin
2012-07-20 9:32 ` Nicolas Goaziou
2012-07-20 13:34 ` Jonathan Leech-Pepin
2012-07-20 13:42 ` Nicolas Goaziou [this message]
2012-07-31 21:03 ` Jonathan Leech-Pepin
2012-07-31 21:18 ` Nicolas Goaziou
2012-07-31 22:35 ` Jonathan Leech-Pepin
2012-07-31 23:45 ` Jonathan Leech-Pepin
2012-08-02 15:34 ` Bastien
[not found] ` <CAHRqSkQTzE-OYmTFs+BRjrER=jgS3=2BE5Yi4A6v8ipaZ1kWQA@mail.gmail.com>
2012-08-02 22:24 ` Fwd: " Jonathan Leech-Pepin
2012-08-03 7:29 ` Bastien
2012-08-03 8:41 ` Nicolas Goaziou
2012-08-03 13:30 ` Jonathan Leech-Pepin
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=87a9yupn0c.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
--cc=pinard@iro.umontreal.ca \
/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).