From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: [feature request] more informative error message when calling an undefined src block
Date: Tue, 10 Jan 2017 13:26:25 +0100 [thread overview]
Message-ID: <87wpe33xu6.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871swcl2bq.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 09 Jan 2017 14:45:13 +0000")
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> I have been trying to track down a nil link on export [1]. I have been
> bisecting a long document. As part of this, I commented out a src block
> used elsewhere in the document. The error trace [abridged] I get upon
> export is:
>
> Debugger entered--Lisp error: (wrong-type-argument consp nil)
> org-babel-exp-code(nil lob)
> org-babel-exp-do-export(nil lob)
> org-babel-exp-process-buffer()
> org-export-as(latex nil nil nil (:output-file "t.tex"))
>
> which was luckily just enough for me to figure out what I had done but I
> think it could be more informative? E.g. it would be nice if it said
> which code it tried to invoke?
>
> Thanks,
> eric
>
> Footnotes:
> [1] related problem: "Unable to resolve link: nil" is not very
> informative either and it's driving me crazy! I've not yet tracked down
> what the problem is but it has something to do with using my own labels
> for tables. More later when I figure it out.
Could you provide an ECM?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-01-10 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 14:45 [feature request] more informative error message when calling an undefined src block Eric S Fraga
2017-01-10 12:26 ` Nicolas Goaziou [this message]
[not found] ` <96762a273fe0404fb647c95179e9f1bd@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-11 15:33 ` Eric S Fraga
2017-01-11 20:02 ` Nicolas Goaziou
[not found] ` <bb5689915c80452f90a3bbe6f3c8651c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-12 6:46 ` Eric S Fraga
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=87wpe33xu6.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).