Re: a minor patch to awk invocation

[Eric Schulte <schulte.eric@gmail.com>]

Achim Gratz <Stromeko@nexgo.de> writes:

> Eric Schulte writes:
>> I can't reproduce these problems.  Could you provide examples, and maybe
>> a stack traces?
>
> The tests have all been done with "make vanilla" and
> testing/examples/ob-awk-test.org.  The test failure is:
>
[...]
>
> I've no idea how to get at the command line.  It is clear that awk gets
> invoked and even delivers the right result, but somehow it is doing this
> differently than before in the case where it uses STDIN.  I can't
> reproduce with my own awk program on the command line.
>

Thanks for the additional information.

The only thing I can think of is that the ordering of the arguments on
the command line is somehow responsible for this error.  Here's the
command line executed by the ob-awk/input-src-block-1 awk test,

    $ awk -f /tmp/babel-66681az/awk-6668uW2

where /tmp/babel-66681az/awk-6668uW2 has the following content.

,----
| {
|     print 42+$1
| }
`----

The command is invoked with `call-process-shell-command'.

Are these failures only present *after* these recent changes to ob-awk?
I can't think of how these changes could be related to this STDIN error.

>
> The problem with "C-c C-v C-v" happens when invoking it on the
> #+BEGIN_SRC line only (which interestingly enough works without error
> once you've done it inside the source block first).
>

I would be surprised if this "C-c C-v C-v" is caused by my recent
changes to awk's variable handling.  Can you find the offend commit here
(or at least check if the problem is new)?

Thanks,

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)