Thanks to you both for the quick solution and the upstream fix.
Hello,
Nick Dokos writes:
> Kaushal Modi writes:
>
>> @Nick Dokos Are you are on a commit before or after this lexical binding
>> change? http://orgmode.org/
>> cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
>>
>> The failure symtoms in my backtrace look like they co
Thanks Nick. That patch resolves the issue for now. At least, all my pdf
exports are working fine as before.
Nick Dokos writes:
> Kaushal Modi writes:
>
>> @Nick Dokos Are you are on a commit before or after this lexical binding
>> change? http://orgmode.org/
>> cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
>>
>> The failure symtoms in my backtrace look like they could be r
Kaushal Modi writes:
> @Nick Dokos Are you are on a commit before or after this lexical binding
> change? http://orgmode.org/
> cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
>
> The failure symtoms in my backtrace look like they could be related to this
> change.
I
> The "g" stands for "git" and it's not part of the SHA1: 4ca117 are the
first six digits of the SHA1 at the HEAD of the branch
Ah, now that you spell it out, it's obvious. I swear I kept staring at the
git hash to find the "117" in "g4ca117" in
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=
Kaushal Modi writes:
> Some more info:
>
> I cannot recreate this error when using
> - my emacs config
> - the same emacs build from git
> - BUT the latest org-plus-contrib from org elpa: Org-mode version 8.3.2
> (8.3.2-10-g00dacd-elpaplus @ /
> home/kmodi/.emacs.d/elpa_25_0/org-plus-contrib-201
@Nick Dokos Are you are on a commit before or after this lexical binding
change?
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=8bccb2131374bba8c82c2774abb34af488826ce4
The failure symtoms in my backtrace look like they could be related to this
change.
Kaushal Modi writes:
>> Although some people can make sense of a backtrace produced with
> compiled code, it is far more useful to provide a backtrace produced
> with *uncompiled* code.
>
> Apologies, I was unaware of that. I should have read that Info node first.
> Below is a gist link to the fu
Some more info:
I cannot recreate this error when using
- my emacs config
- the same emacs build from git
- BUT the latest org-plus-contrib from org elpa: Org-mode version 8.3.2
(8.3.2-10-g00dacd-elpaplus @
/home/kmodi/.emacs.d/elpa_25_0/org-plus-contrib-20151005/)
So it is some change between:
-
Also, I am on the latest org-mode and emacs builds:
org-mode version: Org-mode version 8.3.2 (release_8.3.2-251-g4ca117 @
/home/kmodi/usr_local/apps/6/emacs/master/share/emacs/site-lisp/org/)
emacs-version:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=5401bb8645f955b6fde8c0a5e5c8cf5ec1cab
> Although some people can make sense of a backtrace produced with
compiled code, it is far more useful to provide a backtrace produced
with *uncompiled* code.
Apologies, I was unaware of that. I should have read that Info node first.
Below is a gist link to the full backtrace with uncompiled code
Thank you for providing the backtrace, but ... You knew there was
a "but" coming, right? :-)
Although some people can make sense of a backtrace produced with
compiled code, it is far more useful to provide a backtrace produced
with *uncompiled* code. What you have to do is
C-u M-x org-reload RET
Hi,
I updated my copy of org-mode from git master after about 2-3 weeks. The
ox-latex export used to work fine but now it is failing due to something in
the tables I have in my .org files. If I comment out those tables, the
ox-latex export works fine. Else it errors out due to (void-function nil)
14 matches
Mail list logo