From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: new export question: how to add a new option to an existing backend
Date: Thu, 21 Nov 2013 21:02:36 -0700 [thread overview]
Message-ID: <87eh69jczb.fsf@gmail.com> (raw)
In-Reply-To: 87siup5poe.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> I'd like to add a new option to the LaTeX backend from a contrib/
>> package so that it can be set with a #+ keyword. Is this possible? If
>> so how would one go about making this change. If not what's the best
>> way to add a new optional value to an existing backend (to be used by a
>> new link exporting function and/or the
>> org-export-before-parsing-hook).
>
> It really depends on what you need. I don't get your example. What would
> that option do?
>
> Anyway, you can use defadvice (see "ox-bibtex.el") to alter the
> behaviour of an existing back-end.
>
Hi Nicolas,
Thanks! I was not aware that ox-bibtex.el existed, this accomplishes
exactly the use case I had in mind. I've just pushed up two very small
changes to ox-bibtex.
1. The cite link following function falls back to obe-goto-citation if
ebib is not fbound, and
2. `org-bibtex-process-bib-files' is only called on HTML export, so
bibtex2html is not a requirement of ox-bibtex if used for latex
export only.
Best,
>
>
> Regards,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
prev parent reply other threads:[~2013-11-22 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 22:02 new export question: how to add a new option to an existing backend Eric Schulte
2013-11-21 22:10 ` Yujie Wen
2013-11-21 23:34 ` Eric Schulte
2013-11-21 22:57 ` Nicolas Goaziou
2013-11-22 4:02 ` Eric Schulte [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh69jczb.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.