emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export-current-backend variable and org-mode 8
Date: Sat, 03 Aug 2013 21:08:45 +0200	[thread overview]
Message-ID: <8761vmbnia.fsf@gmail.com> (raw)
In-Reply-To: <87y58iaccl.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 03 Aug 2013 19:55:06 +0200")

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> Nicolas Goaziou writes:
>> Applied a slightly different version. Thank you.
>
> Shouldn't d1d918100e be in maint?

No. Back-end as defstructs is only in the "master" branch.

> Also, I don't think that "nil" should mean both "export in progress with
> an anonymous backend" and "no export in progress".  You've been
> advertising the use of anonmous derived backends to customize exporting,
> so to me it would make more sense if somehow there was a way to detect
> that situation and then get the name of the parent backend instead.

A back-end, anonymous or not, may have no parent at all.

We can also store the full back-end object instead of its name. In this
case, an unnamed back-end is not the same as nil. Alas, this variable
was introduced for compatibility, which that solution kinda defeats.

Speaking about compatibility, previous export framework didn't have
anonymous back-ends. Handling the "nil" case would give us nothing more.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2013-08-03 19:08 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
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 [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=8761vmbnia.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --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).