emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Lisp code blocks fail
Date: Fri, 15 Nov 2013 13:20:30 -1000	[thread overview]
Message-ID: <m1ob5ll0ap.fsf@tsdye.com> (raw)
In-Reply-To: <87vbzv8vsp.fsf@gmail.com> (Eric Schulte's message of "Wed, 13 Nov 2013 14:33:35 -0700")

Hi Eric,

An edebug adventure :)

AFAICT, the error is thrown by this call to a macro:
(org-babel-result-cond ("replace") (car result)), where result has been
set to "2" by the long (funcall) in (let).

Specifically, (org-babel-lisp-vector-to-list "2") appears to trigger the
(error)--at least that is the last code line edebug stops at before
getting to the (error) line. The modeline says Result: "2" just before
the error.

Does this help?

Tom

Eric Schulte <schulte.eric@gmail.com> writes:

> Hi Tom,
>
> That example works for me.  Perhaps you could edebug (C-u C-M-x) the
> `org-babel-execute:lisp' function and then run that code block again to
> see at which statement the error is thrown.
>
> I'm not sure what the problem could be.
>
> Best,
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Eric,
>>
>> #+begin_src lisp
>> (+ 1 1)
>> #+end_src
>>
>> Debugger entered--Lisp error: (wrong-type-argument listp "2")
>>   byte-code("\b\211A@)\207" [result x] 2)
>>   org-babel-execute:lisp("(+ 1 1)" ((:comments . "") (:shebang . "")
>> (:cache . "no") (:padline . "") (:noweb . "yes") (:tangle . "no")
>> (:exports . "code") (:results . "replace") (:session . "none")
>> (:hlines . "no") (:result-type . value) (:result-params "replace")
>> (:rowname-names) (:colname-names)))
>>   org-babel-execute-src-block(nil)
>>   org-babel-execute-src-block-maybe()
>>   org-babel-execute-maybe()
>>   org-babel-execute-safely-maybe()
>>   run-hook-with-args-until-success(org-babel-execute-safely-maybe)
>>   org-ctrl-c-ctrl-c(nil)
>>   ad-Orig-call-interactively(org-ctrl-c-ctrl-c nil nil)
>>   (with-no-warnings (ad-Orig-call-interactively function record-flag keys))
>>   (setq ad-return-value (with-no-warnings
>> (ad-Orig-call-interactively function record-flag keys)))
>>   (let ((ido-ubiquitous-next-override
>> (ido-ubiquitous-get-command-override function))) (setq ad-return-value
>> (with-no-warnings (ad-Orig-call-interactively function record-flag
>> keys))))
>>   (ido-ubiquitous-with-override (ido-ubiquitous-get-command-override
>> function) (setq ad-return-value (with-no-warnings
>> (ad-Orig-call-interactively function record-flag keys))))
>>   (let (ad-return-value) (ido-ubiquitous-with-override
>> (ido-ubiquitous-get-command-override function) (setq ad-return-value
>> (with-no-warnings (ad-Orig-call-interactively function record-flag
>> keys)))) ad-return-value)
>>   call-interactively(org-ctrl-c-ctrl-c nil nil)
>>
>> Org-mode version 8.2.3b (release_8.2.3b-200-gb6522a @
>> /Users/dk/.emacs.d/src/org-mode/lisp/)
>>
>> All the best,
>> Tom
>>
>> Eric Schulte <schulte.eric@gmail.com> writes:
>>
>>> Hi Tom,
>>>
>>> Could you provide a minimal example?  I'm unable to debug from the stack
>>> trace alone.

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

  reply	other threads:[~2013-11-15 23:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13  5:04 Lisp code blocks fail Thomas S. Dye
2013-11-13 14:18 ` Eric Schulte
2013-11-13 21:18   ` Thomas S. Dye
2013-11-13 21:33     ` Eric Schulte
2013-11-15 23:20       ` Thomas S. Dye [this message]
2013-11-17 20:08         ` Thomas S. Dye
2013-11-19 16:09           ` Eric Schulte
2013-11-19 18:50             ` Thomas S. Dye

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=m1ob5ll0ap.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.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).