From: Yu <yu_icq@gmx.at>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Syntax error warnings? (Especially important with :noweb-ref's)
Date: Thu, 12 Jan 2012 22:38:16 +0100 [thread overview]
Message-ID: <CANtbJLFVaJfJ7m4AKauu6kE+W2bsg6PnNPv5o=Wa1PuShpFPdA@mail.gmail.com> (raw)
Hello!
I was wondering, if there is a way to get warnings for typos (e.g.
when specifying invalid properties or header arguments). It can just
easily happen that I mix up e.g. ":exports" and ":export" (though
that's probably a very harmless example).
More important it gets though, when trying to use the literate
programming facilities.
Say I have a source code
#+begin_src sh :noweb tangle :tangle foo.sh
<<foo>>
#+end_src
#+begin_src sh :noweb-ref fo
echo '... how are you?';
#+end_src
then tangling would run through without any indication of the typo in
the name of the "foo" block. Such errors might be hard to debug,
because there is no indication of the error, maybe nothing other than
runtime errors.
An error message for the /use/ of undefined references only wouldn't
avoid such problems either, e.g. consider
#+begin_src sh :noweb tangle :tangle foo.sh
<<foo>>
#+end_src
#+begin_src sh :noweb-ref foo
echo 'Hello World...';
#+end_src
#+begin_src sh :noweb-ref fo
echo 'Hello World...';
#+end_src
where the only detectable error is, that "fo" was never used anywhere.
A similiar question (though without the second part) was asked here:
http://lists.gnu.org/archive/html/emacs-orgmode/2009-11/msg00273.html
As far as I can tell, it stands unanswered.
On a side note: What is the customary way to mention the
noweb-relevant name of a source block in the html/pdf export? After
all, if a code-block states
: <<task1>>
: <<task2>>
the reader needs to know, which code blocks define these.
kind regards, Yu
next reply other threads:[~2012-01-12 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 21:38 Yu [this message]
2012-01-14 17:49 ` Syntax error warnings? (Especially important with :noweb-ref's) Eric Schulte
2012-01-21 15:21 ` Yu
2012-01-23 18:04 ` Eric Schulte
[not found] ` <CANtbJLEo-Bb3erMVRivdQYa=au81ExDJdSYRbQzXqx9F5V=VVw@mail.gmail.com>
[not found] ` <87ehuphy7a.fsf@gmx.com>
[not found] ` <CANtbJLH65=-mhZO0U0Snys=4xEDxL1mFm4JR+Gy7RDHFBTGsgw@mail.gmail.com>
[not found] ` <87sjixyx7m.fsf@gmx.com>
2012-01-30 17:59 ` Yu
2012-01-31 1:10 ` Eric Schulte
2012-01-22 21:25 ` Sebastien Vauban
2012-01-23 18:07 ` Eric Schulte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANtbJLFVaJfJ7m4AKauu6kE+W2bsg6PnNPv5o=Wa1PuShpFPdA@mail.gmail.com' \
--to=yu_icq@gmx.at \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.