I'm still encountering this bug. Org-mode version 7.4 (release_7.4.418.g373c)
This looks like an old release, which is odd. I'm using Eric Schulte's starter kit, and anyway just switched to the org master branch and pulled down the latest commits. 'make clean', 'make info', and 'make lisp/org-install.el' were my next steps. Is it right to take the last 6 chars and search for a commit through the web interface? It isn't turning up anything, and that string is starting look familiar to me. On Thu, Feb 17, 2011 at 5:50 AM, Jambunathan K <kjambunat...@gmail.com> wrote: > Andreas Leha <andreas.l...@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 <dandavis...@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 > > _______________________________________________ > 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 > -- Jeffrey Horn http://www.failuretorefrain.com/jeff/ _______________________________________________ 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
