From: Bastien <bastien.guerry@wikimedia.fr>
To: Dan Davison <dandavison7@gmail.com>
Cc: Org <emacs-orgmode@gnu.org>, mail@christianmoe.com
Subject: Re: Re: [BUG] htmlp and latexp
Date: Wed, 16 Feb 2011 11:44:31 +0100 [thread overview]
Message-ID: <871v38s1gw.fsf@gnu.org> (raw)
In-Reply-To: <m1ipwkpa1o.fsf@gmail.com> (Dan Davison's message of "Wed, 16 Feb 2011 10:07:31 +0000")
Hi Dan,
Dan Davison <dandavison7@gmail.com> writes:
> I was about to make a temporary fix but I see Bastien's just fixed
> it. Bastien -- should we give that `backend' variable a name within the
> org-* namespace (and maybe defvar it in org.el?) so that it is a more
> respectable way to test for "am I doing export now?"? (This issue just
> came up in a separate babel thread).
backend is dynamically scoped, so I think there is no need to defvar it
in org.el -- only in org-*-blocks.el, to avoid compilation warnings.
Let me know if you think otherwise.
But it's a good idea to rename it to org-export-backend. Can you do it?
--
Bastien
next prev parent reply other threads:[~2011-02-16 16:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 22:23 [BUG] htmlp and latexp Dan Davison
2011-02-16 8:44 ` Christian Moe
2011-02-16 10:01 ` Bastien
2011-02-16 10:01 ` Bastien
2011-02-16 10:07 ` Dan Davison
2011-02-16 10:44 ` Bastien [this message]
2011-02-16 17:11 ` Dan Davison
2011-02-18 9:49 ` Bastien
2011-02-22 19:08 ` [PATCH] " Dan Davison
2011-03-01 19:06 ` Bastien
2011-03-01 19:09 ` Bastien
2011-03-02 2:01 ` Dan Davison
2011-03-07 15:32 ` Bastien
2011-02-16 10:03 ` Bastien
2011-02-17 8:46 ` Andreas Leha
2011-02-17 10:19 ` Sébastien Vauban
2011-02-17 10:50 ` Jambunathan K
2011-02-17 23:14 ` Jeff Horn
2011-02-17 23:32 ` Nick Dokos
2011-02-17 23:44 ` Bastien
2011-02-18 8:09 ` Christian Moe
2011-02-18 8:22 ` Andreas Leha
2011-02-18 8:49 ` Bastien
2011-02-18 22:52 ` Jeff Horn
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=871v38s1gw.fsf@gnu.org \
--to=bastien.guerry@wikimedia.fr \
--cc=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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 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).