Thanks to Andreas, Christian, Bastien, and Nick. I didn't know about
org-reload, so that bit is handy. Faster than restarting emacs.
This bug is gone now. My backtrace also indicated org-ex-bibtex.el was
the culprit for me.
On Fri, Feb 18, 2011 at 3:49 AM, Bastien wrote:
> Hi Andreas,
>
> Andrea
Hi Andreas,
Andreas Leha writes:
> I did not send to the list, so I resend my last email below. But for me
> I found the issue: org-exp-bibtex.el is the problem.
Fixed, thanks.
--
Bastien
___
Emacs-orgmode mailing list
Please use `Reply All' to
Hi all,
I did not send to the list, so I resend my last email below. But for me
I found the issue: org-exp-bibtex.el is the problem.
Regards,
Andreas
PS: Here my last email:
Thanks for looking into this. But just pulled before asking.
I am pulling from git://repo.or.cz/org-mode.git
The l
Hi, Jeff,
Check if you've got an old version of org-special-blocks somewhere on
your loadpath. I did, and it kept me running in circles for a bit.
Yours,
Christian
On 2/18/11 12:14 AM, Jeff Horn wrote:
I'm still encountering this bug.
Org-mode version 7.4 (release_7.4.418.g373c)
This look
Hi Jeff,
Jeff Horn writes:
> 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/
Jeff Horn wrote:
> I'm still encountering this bug.
Works fine here.
>
> Org-mode version 7.4 (release_7.4.418.g373c)
>
That's the latest (as of two minutes ago).
> This looks like an old release, which is odd. I'm using Eric Schulte's
> starter kit, and anyway just switched to the org mast
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-ins
Hi Dan,
Dan Davison 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?
