emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Torsten Wagner <torsten.wagner@gmail.com>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: [babel] Should babel be more error intolerant?
Date: Sun, 9 Oct 2011 00:32:03 +0900	[thread overview]
Message-ID: <CAPaq-gO65SNGKLcQn40Y8KVkz+X2LrbzJMNyJ7C4CWJMevffuw@mail.gmail.com> (raw)

Hi,

just playing around with a new aspect of org-mode and babel, I
noticed, that many of my typos and wrong syntax using are silently
accepted resp. ignored.
Even the message buffer keeps quite.
I just wonder if babel should be more error intolerant to tell users
that they are actually doing something wrong.
E.g., I don't see any error messages for (marked the typo by *):


#+begin_src latex :file*s* fig/mypicture.pdf :packages '(("" "tikz"))
:border 1em :fit  :results output silent
or
#+begin_src latex :file fig/mypicture.pdf :packages '(("" "tikz"))
:border 1em :fit  :*result* output silent
or
#+begin_src latex :file fig/mypicture.pdf :packages '(("" "tikz"))
:border 1em :fit  :results output *quite*

obviously the above errors might happen quickly just as typos or
because one tries to use commands from memory.

Trying something new, this might drive someone quickly crazy. One is
going to tackle the problem in many different ways and finally after
several minutes (or even hours) one notice its simply "silent" and not
"quite" ;)

I would prefer a bold
Error ":results output quite" is unknown to babel
in the minibuffer, maybe including jumping to the line in question.
Others might like to keep it quite (or silent), I guess it could be
easily set by an optional flag
like #+BABEL:debug:t

As a side note of this, I wonder if babel could use the same/similar
way like the TODO field in org-mode to switch between all possible
parameters for a certain code block?
I learned, different code blocks can have quite different possible
parameters. A bit difficult to remember esp., if you don't use them on
a daily basis.
If one could place the pointer to e.g., the :results keyword and hit
C-c C-t to switch between all possibilities for the :exports keyword
for this particular source code block, it would greatly simply the
usage and reduce errors. Parameters which require additional user
input like file names could indicate this (like in the manual) by
indicating it within brackets e.g., <filename>.

Thanks for all the help and support

Torsten

next             reply	other threads:[~2011-10-08 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 15:32 Torsten Wagner [this message]
2011-10-08 17:23 ` [babel] Should babel be more error intolerant? Eric Schulte
2011-10-08 22:47   ` Eric Schulte
2011-10-10  9:02     ` Rainer M Krug

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=CAPaq-gO65SNGKLcQn40Y8KVkz+X2LrbzJMNyJ7C4CWJMevffuw@mail.gmail.com \
    --to=torsten.wagner@gmail.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

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).