emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 22:21:01 +0100	[thread overview]
Message-ID: <87li4mtohu.fsf@cantab.net> (raw)
In-Reply-To: 87siyuzcnm.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Christophe Rhodes <csr21@cantab.net> writes:
>
>> 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 :-/
>
> It is intentional. I tried to reduce the number of dynamically scoped
> variables.
>
> On the other hand, hooks and filters all get back-end's name, if any, as
> an argument, which limits the need for that variable. The only missing
> part is Babel. I thought the recently introduced `by-backend' feature
> was sufficient. Isn't it the case?

The `by-backend' macro in Brett Viren's message upthread?  Personally I
don't consider that sufficient, because it feels very fragile: a simple
renaming of org-mode internal variables, or turning on lexical binding,
and the macro will no longer work.  (If you mean some other
`by-backend', I haven't seen it).

In particular, I would like to have some kind of confidence that
documents that I wrote last year will still be exportable next year with
only minor modifications necessary, and to do that I think I need to
convince you that this is valuable, enough that you are willing to
commit to some stable way of accessing the information previously held
in org-export-current-backend.

> I also thought about reintroducing `org-export-current-backend', but
> that would be redundant with hooks and filters' arguments. Removing
> these is not an option either, as that would break every hook/filter in
> the wild.

Please don't remove hooks and filters, or change their arguments!  But
please consider reintroducing org-export-current-backend; I have just
checked, and the document that I am currently editing exports to latex
and html unmodified from the org-mode 7 version, apart from some trivial
variable renamings in the elisp setup and the reintroduction through
advice of org-export-current-backend.  And although that's fairly
straightforward for me to achieve, it's a cost, and one that I have to
pay every time I want to share a reproducible research document with a
colleague who hasn't upgraded to org-mode 8 yet, maybe because some of
/their/ documents don't yet build under org-mode 8...

Best wishes,

Christophe

  reply	other threads:[~2013-07-31 23:32 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
2013-07-31 20:40     ` Nicolas Goaziou
2013-07-31 21:21       ` Christophe Rhodes [this message]
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=87li4mtohu.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).