From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] htmlp and latexp
Date: Thu, 17 Feb 2011 16:20:23 +0530 [thread overview]
Message-ID: <81y65fq6j4.fsf@gmail.com> (raw)
In-Reply-To: <4D5CE060.2070104@med.uni-goettingen.de> (Andreas Leha's message of "Thu, 17 Feb 2011 09:46:24 +0100")
Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
> Hi all,
>
> to make this explicit: I can not export to latex any more, but instead
> I get
> Exporting to LaTeX...
> when: Symbol's value as variable is void: htmlp
>
> Org HEAD
> GNU emacs 23.2.1 (debian squeeze)
>
> This is my failing org-file:
> * Test
> test
>
Have you tried recent head?
Enable stacktrace: M-x toggle-debug-on-error
Also include M-x org-version?
Jambunathan K.
> - Andreas
>
>
> Am 16.02.2011 11:03, schrieb Bastien:
>> Hi Dan,
>>
>> Dan Davison <dandavison7@gmail.com> writes:
>>
>>
>>> 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, which contains
>>>
>>> #+begin_src emacs-lisp
>>> (defvar htmlp)
>>> (defvar latexp)
>>> (defun org-special-blocks-make-special-cookies ()
>>> "Adds special cookies when #+begin_foo and #+end_foo tokens are
>>> seen. This is run after a few special cases are taken care of."
>>> (when (or htmlp latexp)
>>> (goto-char (point-min))
>>> ...
>>> #+end_src
>>>
>> Fixed thanks.
>>
>>
>>> IIuc htmlp and latexp occur occasionally in org code as somewhat
>>> unofficial ways to test "am I in the middle of export?".
>>>
>> Now there is a uniform and official (!) way of getting the backend the
>> user is currently exporting to:
>>
>> (eq backend 'html)
>>
>> ...
>>
>>
>>> They also occur in org-exp-blocks, but in deprecated code, so not a
>>> priority to fix.
>>>
>> I fixed them there too.
>>
>> Thanks for reporting this!
>>
>>
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2011-02-17 10:50 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
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 [this message]
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=81y65fq6j4.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--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).