From: Eric Schulte <firstname.lastname@example.org>
To: Andreas Leha <email@example.com>
Subject: Re: Is it possible to run shell script src blocks as root or to export individual blocks?
Date: Mon, 05 Mar 2012 08:24:46 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Andreas Leha <email@example.com> writes:
> Eric Schulte <firstname.lastname@example.org> writes:
>> Leo Alekseyev <email@example.com> writes:
>>> I was wondering if there was an easy way to execute some shell
>>> commands contained in a src block as root. Alternatively, is there a
>>> quick way to export _just_ that one source block to a temp file so
>>> that I could run it as root manually?
>> Just call org-babel-tangle with a prefix argument and it only tangles
>> the current block
> I did not know this either. Thanks for the hint!
> Shouldn't this be mentioned in the manual (14.4)?
> I have two questions/issues about this:
> (1) Can I get noweb-references to be expanded by this? Or how would I
> tangle one block with noweb references expanded?
There was a conflict between the narrowing to a single code block caused
by the prefix argument, and the code which searches for replacements to
noweb elements. I've just pushed up a fix so noweb elements should now
expand as normal.
> (2) I am asked for a filename. But the header argument :tangle somefile
> is overruling my input, which is un-expected.
This is now fixed as well.
next prev parent reply other threads:[~2012-03-05 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 4:40 Is it possible to run shell script src blocks as root or to export individual blocks? Leo Alekseyev
2012-03-03 8:55 ` Nick Dokos
2012-03-03 9:19 ` org-babel-execute-src-block deletes its src block Daimrod
2012-03-03 9:42 ` Nick Dokos
2012-03-03 9:54 ` Daimrod
2012-03-03 14:46 ` Eric Schulte
2012-03-03 15:11 ` Daimrod
2012-03-03 14:25 ` Is it possible to run shell script src blocks as root or to export individual blocks? Eric Schulte
2012-03-03 16:43 ` Andreas Leha
2012-03-05 15:24 ` Eric Schulte [this message]
2012-03-06 9:11 ` Andreas Leha
2012-03-19 8:42 ` Leo Alekseyev
2012-03-19 14:46 ` Eric Schulte
2012-03-04 17:29 ` Sylvain Rousseau
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).