From: Eric Schulte <email@example.com>
To: Torsten Wagner <firstname.lastname@example.org>
Cc: Org Mode Mailing List <email@example.com>
Subject: Re: [babel] Should babel be more error intolerant?
Date: Sat, 08 Oct 2011 16:47:25 -0600 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Eric Schulte's message of "Sat, 08 Oct 2011 11:23:41 -0600")
>> 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>.
> This is a very good idea and shouldn't be too difficult to implement for
> all of those header arguments which are common across all languages.
> I'll place this on my todo list...
I've just pushed up a simple implementation of the above. The new
function `org-babel-insert-header-arg' bound to C-c C-v j will insert a
header argument and its value using completing read in the minibuffer.
I'm sure the current functionality has room for improvement but it seems
to work well in my initial tests.
Let me know what you think.
Best -- Eric
next prev parent reply other threads:[~2011-10-08 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 15:32 [babel] Should babel be more error intolerant? Torsten Wagner
2011-10-08 17:23 ` Eric Schulte
2011-10-08 22:47 ` Eric Schulte [this message]
2011-10-10 9:02 ` Rainer M Krug
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).