From: Diego Zamboni <diego@zzamboni.org>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: creating new #+KEYWORD: variables
Date: Mon, 12 Nov 2018 10:11:38 +0100 [thread overview]
Message-ID: <CAGY83Ef=SKLktEnAG+d9PDJiH2Rr8aSe_ygP=+UN0fp9F7O=2A@mail.gmail.com> (raw)
In-Reply-To: <87h8gpcs86.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
Hi Nicolas,
Thank you for this pointer! I have modified my own leanpub-multifile
backend (derived from leanpub) to use this instead of manually extracting
the keywords.
In case anyone is interested, my code is here:
https://github.com/zzamboni/dot-emacs/blob/master/init.org#publishing-to-leanpub
Best,
--Diego
On Sat, Nov 10, 2018 at 8:22 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Matt Price <moptop99@gmail.com> writes:
>
> > I am writing this interface to my university's learning management
> system:
> >
> https://github.com/titaniumbones/Org-Marking-Mode/tree/use-structured-course-def
> .
> > I am only using hte exporting system tangentially and I have not defined
> a
> > new exporter. However, I would really like to be able to set some
> variable
> > values in the header section of hte document, e.g.:
> >
> > #+ORG_LMS_COURSE: becomingmodern
>
> You can add keywords specific to a given export back-end in its
> definition, more precisely in :options-alist value. For example, in
> "ox-texinfo", there is
>
> (org-export-define-backend 'texinfo
> '((bold . org-texinfo-bold))
> ...
> :options-alist
> '((:texinfo-filename "TEXINFO_FILENAME" nil nil t)
> ...))
>
> which means `texinfo' back-end should recognize the "#+TEXINFO_FILENAME"
> keyword, and store its value in the :texinfo-filename property from
> "info" paramater, which is passed to each function.
>
> You can write a derived back-end using this new keyword, along with
> a template function that actually uses it. Look at the definition of
> `beamer' back-end for an example.
>
> HTH,
>
> --
> Nicolas Goaziou
>
>
[-- Attachment #2: Type: text/html, Size: 2529 bytes --]
prev parent reply other threads:[~2018-11-12 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 3:32 creating new #+KEYWORD: variables Matt Price
2018-11-09 9:29 ` Diego Zamboni
2018-11-10 2:24 ` Matt Price
2018-11-10 7:22 ` Nicolas Goaziou
2018-11-10 16:17 ` Matt Price
2018-11-10 17:11 ` John Kitchin
2018-11-10 18:58 ` Nicolas Goaziou
2018-11-15 12:15 ` Matt Price
2018-11-15 19:51 ` John Kitchin
2018-11-12 9:11 ` Diego Zamboni [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='CAGY83Ef=SKLktEnAG+d9PDJiH2Rr8aSe_ygP=+UN0fp9F7O=2A@mail.gmail.com' \
--to=diego@zzamboni.org \
--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).