From: Christophe Rhodes <csr21@cantab.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-export-current-backend variable and org-mode 8
Date: Wed, 31 Jul 2013 20:09:02 +0100 [thread overview]
Message-ID: <87y58mtult.fsf@cantab.net> (raw)
In-Reply-To: ir4bo5izi5c.fsf@lycastus.phy.bnl.gov
[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]
Brett Viren <bv@bnl.gov> writes:
> Christophe Rhodes <csr21@cantab.net> writes:
>
>> In org-mode 7, I was able to use the (documented) variable
>> org-export-current-backend to test what the current backend is, allowing
>> me to dynamically produce and include images of different formats
>> depending on whether I was exporting to latex (tikz) or html (png).
>>
>> In org-mode 8, I cannot find this variable, or any documented variable
>> of a similar nature. What is the recommended way for dispatching at the
>> emacs-lisp level when exporting a document on the export backend?
>
> I don't know if this is exactly what you are asking for but I hit on the
> following a few weeks ago. It defines an elisp macro inside the org
> file and then calls it later in the header of a code block to switch the
> output file names based on which backend (if any) is in effect. I hope
> it helps.
Thanks. Well, it proves at least that I'm not going mad :-(
> If you have a better way to do these kind of output switches, I'd like
> to know.
> #+begin_src emacs-lisp :results silent
> (defmacro by-backend (&rest body)
> `(case (if (boundp 'backend) backend nil) ,@body))
> #+end_src
It's funny -- I felt queasy using the bare backend variable in the olden
6.x days, and was very happy when org-export-current-backend showed up.
Now, there's a real reason to be worried about using backend: it's
fairly clearly used as an internal variable, and all it would take would
be for lexical binding to be turned on for ox.el and this would
(probably) stop working.
If we're grubbing around in internals, I might be tempted instead by
something like [untested]
#+begin_src emacs-lisp :exports results :results silent
(unless (boundp 'org-export-current-backend)
(defadvice org-export-as (around oecb-around)
(let ((org-export-current-backend (ad-get-arg 0)))
ad-do-it)))
#+end_src
so that if (as I hope) org-export-current-backend makes a later
reappearance, my documents can work with both org-mode 7 and 8, and
maybe 9? I'm hoping that the disappearance of the variable is an
oversight rather than intentional :-/
Cheers,
Christophe
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-07-31 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 16:27 org-export-current-backend variable and org-mode 8 Christophe Rhodes
2013-07-31 18:41 ` Brett Viren
2013-07-31 19:09 ` Christophe Rhodes [this message]
2013-07-31 20:40 ` Nicolas Goaziou
2013-07-31 21:21 ` Christophe Rhodes
2013-08-02 10:01 ` Christophe Rhodes
2013-08-03 7:50 ` Nicolas Goaziou
2013-08-03 17:55 ` Achim Gratz
2013-08-03 19:08 ` Nicolas Goaziou
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=87y58mtult.fsf@cantab.net \
--to=csr21@cantab.net \
--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).