On Wed, Feb 3, 2010 at 10:15 PM, Eric Schulte wrote:
> Hi Rainer,
>
> Rainer M Krug writes:
>
> > Hi Eric
>
> [...]
>
> > So yes, I think it would be very useful to define the two additional
> header arguments for each
> > block:
> >
> > :shebang NIL for default, other string for the shebang line
Hi Rainer,
Rainer M Krug writes:
> Hi Eric
[...]
> So yes, I think it would be very useful to define the two additional header
> arguments for each
> block:
>
> :shebang NIL for default, other string for the shebang line
> :headers NIL for default, NONE for no headers, other string for custom
Hi Eric
On Wed, Feb 3, 2010 at 7:22 PM, Eric Schulte wrote:
> Hi Rainer,
>
> I just responded to your other email with a global solution to this
> problem.
Thanks - I'll look at it in detail tomorrow.
> Do you think this is the sort of thing that would need to be
> customized on a per-block
Hi Rainer,
I just responded to your other email with a global solution to this
problem. Do you think this is the sort of thing that would need to be
customized on a per-block or per-file/subtree basis?
If so we may want to move this customization behind a header argument.
Thanks -- Eric
Rainer
Hi
I am sure I can customize it, but I could not find it.
When tangling R code, I would like to skip (or customize) the first line of
the resulting R file. It reads "#!/usr/bin/env Rscript" and I would either
like to exclude it completely, or replace it with e.g. "## R"
I am sourcing the files an
