On 03/22/2014 02:43 AM, Michael Brand wrote:
>
> For two reasons I would much prefer if there would be not yet another
> variable org-* but a header argument or a new value for e. g.
> ":results":
> - When someone would use org-babel-use-error-buffer then sharing Org
> source blocks would be les
Hi Ian
On Sat, Mar 22, 2014 at 4:59 AM, Ian Kelling wrote:
> I use babel mostly for shell scripts. I wrote a patch to allow toggling the
> handling of errors & std err. I prefer standard error just get printed with
> everything else, the same as calling a script from a terminal. Doing this
> pro
Ian Kelling writes:
> We've been in email contact less than a week ago. It shouldn't be
> too long.
Okay, this takes usually up to 6 weeks, so don't hold you breath!
--
Bastien
> Was it more than a month ago? If so, I'll ping them.
We've been in email contact less than a week ago. It shouldn't be too long.
Hi Ian,
Ian Kelling writes:
> I'd be happy to clean it up if there is interest in merging it. Also I've
> done the
> FSF paperwork a while ago, I'm just waiting on hearing confirmation.
Was it more than a month ago? If so, I'll ping them.
Let's wait for Eric's answer about whether the patch
On 03/22/2014 01:45 AM, Bastien wrote:
> Hi Ian,
>
> the idea behind the patch looks good, although the patch needs
> some clean-up (adding a Changelog entry, fixing the typos in the
> docstring, etc.)
>
> Also, the patch goes beyond the 15 lines: we cannot accept it
> until you sign the FSF copy
Hi Ian,
the idea behind the patch looks good, although the patch needs
some clean-up (adding a Changelog entry, fixing the typos in the
docstring, etc.)
Also, the patch goes beyond the 15 lines: we cannot accept it
until you sign the FSF copyright assignment. If you're willing
to do this, please
I use babel mostly for shell scripts. I wrote a patch to allow toggling the
handling of errors & std err. I prefer standard error just get printed with
everything else, the same as calling a script from a terminal. Doing this
properly
with header arguments etc. has been discussed before (google or
