emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Thu, 12 Jan 2017 06:46:13 +0000	[thread overview]
Message-ID: <87lguglqru.fsf@ucl.ac.uk> (raw)
In-Reply-To: <bb5689915c80452f90a3bbe6f3c8651c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Nicolas Goaziou's message of "Wed, 11 Jan 2017 20:02:13 +0000")

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

On Wednesday, 11 Jan 2017 at 20:02, Nicolas Goaziou wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> 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!
>
> Of course. Fixed. Thank you.

Excellent!  Works perfectly.  Many thanks.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-189-ge46676

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

      parent reply	other threads:[~2017-01-12  7:00 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
2017-01-11 20:02     ` Nicolas Goaziou
     [not found]     ` <bb5689915c80452f90a3bbe6f3c8651c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-12  6:46       ` Eric S Fraga [this message]

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=87lguglqru.fsf@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).