emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <dandavison7@gmail.com>
To: mail@christianmoe.com
Cc: Org <emacs-orgmode@gnu.org>, Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: [BUG] htmlp and latexp
Date: Wed, 16 Feb 2011 10:07:31 +0000	[thread overview]
Message-ID: <m1ipwkpa1o.fsf@gmail.com> (raw)
In-Reply-To: <4D5B8E60.4070307@christianmoe.com> (Christian Moe's message of "Wed, 16 Feb 2011 09:44:16 +0100")

Christian Moe <mail@christianmoe.com> writes:

> On 2/15/11 11:23 PM, Dan Davison wrote:
>> Commit ed6d6760268 removed variables htmlp and latexp from
>> `org-export-preprocess-string'. Nothing wrong with that, but I think it
>> has broken export for those using org-special-blocks
>
> Confirmed. Exporting the following example stops with a void-variable 
> error in org-special-blocks-make-special-cookies.

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).

Dan

>
> --------------------
>
> Some text.
>
> #+begin_sidebar
>    Some details left out of the main text.
> #+end_sidebar
>
> --------------------
>
> (Incidentally -- org-special-blocks.el still says it's "not currently 
> part of GNU Emacs", but as of Org-mode 7.4 it is, isn't it?)
>
> CM
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2011-02-16 10:07 UTC|newest]

Thread overview: 25+ 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 [this message]
2011-02-16 10:44     ` Bastien
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
  -- strict thread matches above, loose matches on Subject: below --
2011-02-15 23:39 Kieran Healy

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=m1ipwkpa1o.fsf@gmail.com \
    --to=dandavison7@gmail.com \
    --cc=bastien.guerry@wikimedia.fr \
    --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).