emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: Ista Zahn <izahn@psych.rochester.edu>,
	Konrad Hinsen <konrad.hinsen@fastmail.net>,
	nicholas.dokos@hp.com,
	emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Error when running org-babel-execute-buffer -- Wrong	type argument: consp, nil
Date: Wed, 17 Nov 2010 17:07:28 -0700	[thread overview]
Message-ID: <874obfjxz3.fsf@gmail.com> (raw)
In-Reply-To: <87lj4vvhup.wl%dmaus@ictsoc.de> (David Maus's message of "Sun, 14 Nov 2010 20:13:34 +0100")

Thanks for doing most of the debugging on this.

After much banging of my head, I stumbled onto this very nice page of
common problems with compiled Macros in Emacs Lisp [1], it looks like
this sort of thing has happened before. :)

I realized I was guilty of one of the macro sins specified above, and
after rectifying that design flaw I believe (at least for my simple test
case) this error should be fixed.  Please let me know if you continue to
run into this problem with the byte-compiled version of this macro.

Best -- Eric

David Maus <dmaus@ictsoc.de> writes:

> At Mon, 08 Nov 2010 09:45:25 -0500,
> Nick Dokos wrote:
>> Something to do with the compilation of the org-babel-map-src-blocks
>> macro, no doubt.  I don't see it with uncompiled files.
>
> Not a solution, but some debugging showed that
> `org-babel-get-src-block-info' fails to get the info of the source
> block when run byte-compiled.
>
> If I change the last sexp of the function
>
> (when info (append info (list name indent)))
>
> to
>
> (if info (append info (list name indent))
>  (error "EMPTY INFO"))
>
> And run byte-compiled Org, the EMPTY INFO error is thrown before the
> invalid argument.
>
> Best,
>   -- David
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de
> _______________________________________________
> 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

Footnotes: 
[1]  http://www.gnu.org/s/emacs/manual/html_node/elisp/Problems-with-Macros.html

  reply	other threads:[~2010-11-18  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 16:09 Error when running org-babel-execute-buffer -- Wrong type argument: consp, nil Ista Zahn
2010-11-08 13:35 ` Konrad Hinsen
2010-11-08 13:49   ` Eric Schulte
2010-11-08 13:58     ` Konrad Hinsen
2010-11-08 14:21       ` Eric S Fraga
2010-11-08 14:45       ` Nick Dokos
2010-11-08 14:53         ` Konrad Hinsen
2010-11-14 19:13         ` David Maus
2010-11-18  0:07           ` Eric Schulte [this message]
2010-11-18 18:58             ` Konrad Hinsen
2010-11-19  7:46             ` Nick Dokos
2010-11-19  8:19               ` Eric Schulte
2010-11-19  8:48                 ` Konrad Hinsen

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=874obfjxz3.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=izahn@psych.rochester.edu \
    --cc=konrad.hinsen@fastmail.net \
    --cc=nicholas.dokos@hp.com \
    /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).