emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Chris Malone <chris.m.malone@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Two questions about using a =#+begin_src emacs-lisp= block
Date: Tue, 22 Feb 2011 09:54:01 -0700	[thread overview]
Message-ID: <87aahodn7f.fsf@gmail.com> (raw)
In-Reply-To: AANLkTimPtyk+6gvB6fd8bGuFHwcjs5PwJSpH-2ZtYtO=@mail.gmail.com

Chris Malone <chris.m.malone@gmail.com> writes:

> Hi Eric,
>
> I removed all the compiled elisp files, and the problem still persists.
> Next step will be a completely fresh install from git; my current version is
> up to date, but maybe there was some conflict that git didn't complain
> about...
>

Before doing that could you re-send a minimal example with instruction
for how to reproduce the problem, and I'll give it another shot.

Thanks -- Eric

>
> Chris
>
> On Mon, Feb 21, 2011 at 2:48 PM, Eric Schulte <schulte.eric@gmail.com>wrote:
>
>> Chris Malone <chris.m.malone@gmail.com> writes:
>> [...]
>> >
>> > I added =(setq org-confirm-babel-evaluate nil)= to my =.emacs= file, and
>> indeed I am not asked about evaluating the code block, but I'm still getting
>> the invalid
>> > syntax error when =org-babel-exp= is called the second time on the
>> =emacs-lisp= code block.? I should mention that this is somewhere in the
>> byte-code, as the error
>> > is:
>> >
>> > byte-code: Invalid read syntax: "#"
>> >
>> > in the *Messages* buffer.? I still don't fully understand why it should
>> be evaluating that code block twice.
>> >
>>
>> Hmm, it may be worth cleaning out all compiled .elc files from within
>> Org-mode, the calling org-reload, and see if the problem persists.
>>
>> Best -- Eric
>>
>> >
>> > Chris
>>

  reply	other threads:[~2011-02-22 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 22:08 Two questions about using a =#+begin_src emacs-lisp= block Chris Malone
2011-02-21 17:17 ` Eric Schulte
2011-02-21 18:31   ` Chris Malone
2011-02-21 19:48     ` Eric Schulte
2011-02-22 15:06       ` Chris Malone
2011-02-22 16:54         ` Eric Schulte [this message]
2011-02-22 16:57         ` Chris Malone
2011-02-22 18:06           ` Eric Schulte
2011-02-22 18:23             ` chris.m.malone
2011-02-22 18:45             ` Achim Gratz
2011-02-21 22:19   ` Dan Davison
2011-02-21 22:34     ` 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=87aahodn7f.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=chris.m.malone@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).