From: Nick Dokos <nicholas.dokos@hp.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: nicholas.dokos@hp.com, emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Re: eval: Invalid read syntax: "#"Error during redisplay: (void-function -mode)
Date: Sat, 11 Dec 2010 13:51:14 -0500 [thread overview]
Message-ID: <3161.1292093474@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bernt Hansen <bernt@norang.ca> of "Sat, 11 Dec 2010 13:04:29 EST." <87r5dow5hu.fsf@norang.ca>
Bernt Hansen <bernt@norang.ca> wrote:
> "Thomas S. Dye" <tsd@tsdye.com> writes:
>
> > So, Seb and I have two things that others can't reproduce: the error
> > in the OP, and the version string for the latest Org-mode.
> >
> >>>
> >>> I'm using Org-mode version 7.3 (release_7.4.2.g32f816.dirty)
> >>>
> >>
> >>
> >> FWIW, I cannot reproduce it:
> >>
> >> GNU Emacs 23.2.50.1 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of
> >> 2010-10-27 on gamaville.dokosmarshall.org
> >> Org-mode version 7.4 (release_7.4.5.gb0844.dirty)
>
> The version string problem is reproducible. At commit 32f816 (2 commits
> after the release_7.4 tag) the version number is 7.3 even though it is
> after the release_7.4 tag.
>
> In b0844 (5 commits after the release_7.4 tag) this problem has been
> fixed which is why Nick doesn't see it.
>
I was really talking about the latex-export/eval problem that Tom is
seeing, not the version string problem.
Speaking of the eval problem, I notice in the backtrace[fn:1] that Tom
posted that org-babel-exp-src-blocks is called with
"#+end_src\n#+begin_src emacs-lisp :var lst=a-list :results list" as
argument:
org-babel-exp-src-blocks(#("#+end_src\n#+begin_src emacs-lisp :var lst=a-list :results list" ...)
But when I latex-export the same blocks through my setup (I edebug
org-babel-exp-src-blocks and when it stops, I evaluate the variable
``body''), org-babel-exp-src-blocks is called twice with the *body* of
each of the blocks as argument:
o the first time I get: #("\"code block results\"" 0 20 (fontified nil font-lock-fontified t))
o the second time I get: #("(reverse lst)" 0 13 (fontified nil font-lock-fontified t))
So it looks as if the parsing somehow gets out of sync in Tom's case,
but I don't understand why or how. In my case, the latex export goes
through with no problems.
Nick
Footnotes:
[fn:1] A backtrace of Tolstoian proportions...
next prev parent reply other threads:[~2010-12-11 18:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 17:56 eval: Invalid read syntax: "#"Error during redisplay: (void-function -mode) Thomas S. Dye
2010-12-10 18:15 ` Nick Dokos
2010-12-10 18:27 ` Thomas S. Dye
2010-12-10 18:34 ` Nick Dokos
2010-12-10 18:55 ` Thomas S. Dye
2010-12-11 18:04 ` Bernt Hansen
2010-12-11 18:51 ` Nick Dokos [this message]
2010-12-11 20:26 ` Sébastien Vauban
2010-12-11 22:14 ` Thomas S. Dye
2010-12-11 23:06 ` Nick Dokos
2010-12-12 0:03 ` Sébastien Vauban
2010-12-12 0:42 ` Thomas S. Dye
2010-12-12 22:57 ` Nick Dokos
2010-12-13 19:42 ` Eric Schulte
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=3161.1292093474@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=bernt@norang.ca \
--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).