From: tsd@tsdye.com (Thomas S. Dye)
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Lisp code blocks fail
Date: Tue, 12 Nov 2013 19:04:00 -1000 [thread overview]
Message-ID: <m1fvr051vj.fsf@tsdye.com> (raw)
Aloha all,
With a recent pull, Lisp code blocks that I'm fairly certain were
working previously started to fail. There is a backtrace below. The Lisp
code executes correctly, but Babel doesn't appear to get the results in
the form it expects (if I'm reading the backtrace correctly).
Have I mucked up somehow?
Debugger entered--Lisp error: (wrong-type-argument listp "((\"t2\" \"b\"))")
byte-code("\b\211A@)\207" [result x] 2)
org-babel-execute:lisp("(unless (boundp '*cycle-graph*)\n (defvar *cycle-graph*))\n(setq *cycle-graph* (populate (make-instance 'digraph)))\n(let ((r)\n (flag))\n (dolist (e edges r)\n (add-edge *cycle-graph*\n (list (read-from-string (first e))\n (read-from-string (second e))))\n (when (and (not flag) (setf flag (cycles *cycle-graph*))) (push e r))))" ((:comments . "") (:shebang . "") (:cache . "no") (:padline . "") (:noweb . "yes") (:tangle . "no") (:exports . "code") (:results . "silent") (:var edges ("t1" "a") ("a" "t2") ("b" "t1") ("t2" "b")) (:colnames . "yes") (:hlines . "no") (:session . "none") (:result-type . value) (:result-params "silent") (:rowname-names) (:colname-names (edges "older" "younger"))))
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)
All the best,
Tom
--
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
next reply other threads:[~2013-11-13 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 5:04 Thomas S. Dye [this message]
2013-11-13 14:18 ` Lisp code blocks fail 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
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=m1fvr051vj.fsf@tsdye.com \
--to=tsd@tsdye.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).