From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: [feature request] more informative error message when calling an undefined src block
Date: Wed, 11 Jan 2017 15:33:02 +0000 [thread overview]
Message-ID: <877f61a9xt.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: 96762a273fe0404fb647c95179e9f1bd@HE1PR01MB1898.eurprd01.prod.exchangelabs.com
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Tuesday, 10 Jan 2017 at 12:26, Nicolas Goaziou wrote:
[...]
> Could you provide an ECM?
Yes, of course:
#+begin_src org
,* Simple illustration of nil link error message
In table [[mytable]], there are some numbers
,** the table :noexport:
,#+name: mytable
| x | y |
|---+---|
| 1 | 1 |
| 2 | 4 |
,#+TBLFM: $2=$1^2
#+end_src
There is a reference to a table which is in a subtree that is not to be
exported. The error message is
user-error: Unable to resolve link: nil
This ECM may appear contrived but, when working with a large document,
it is easy to comment out or exclude sections that, it turns out, have
material within that is referenced from elsewhere. This is difficult to
track down when exporting. If the error message had "nil" above
replaced by "mytable", it would make all the difference!
Many thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.2-104-gf5b7de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-01-11 18:45 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
[not found] ` <96762a273fe0404fb647c95179e9f1bd@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-11 15:33 ` Eric S Fraga [this message]
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=877f61a9xt.fsf@delle7240.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).