The problem was that
a) I'm using tcsh.
b) Some part of the system-wide csh.cshrc related to Emacs' shell-mode
was also run for non-interactive shell invocation while only
appropriate for interactive use (that's where the errors from tset
and stty came from).
c) Your second patch 6fb03
thanks -- nice!
Eric Schulte writes:
> 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.
Yes, they've just started with the second commit (the first one broke
the tests in a different way as you may know).
> I would
Achim Gratz 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 c
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:
--8<---cut here---start->8---
(("tset:
Achim Gratz writes:
> Eric Schulte writes:
>> Thanks for pointing out this shortcoming and for suggesting the
>> command-line variable assignment option. I've just pushed up a patch
>> which changes the behavior of awk code blocks to assign variables on the
>> command line, so the following now
Greg Minshall writes:
> though, in the spirit of "no good deed goes unpunished":
>
> #+name: foo
> | a | b | c |
> #+begin_src awk :var a=foo
> BEGIN{ print a; }
> #+end_src
>
> gives an error (and, ':var a="this is a test"' doesn't behave as one
> might expect). i haven't looked at ob
Eric Schulte writes:
> Thanks for pointing out this shortcoming and for suggesting the
> command-line variable assignment option. I've just pushed up a patch
> which changes the behavior of awk code blocks to assign variables on the
> command line, so the following now work.
For whatever reason I
though, in the spirit of "no good deed goes unpunished":
#+name: foo
| a | b | c |
#+begin_src awk :var a=foo
BEGIN{ print a; }
#+end_src
gives an error (and, ':var a="this is a test"' doesn't behave as one
might expect). i haven't looked at ob-*.el enough to know the patterns
used to w
very nice -- thanks!
> I've just pushed up a patch which changes the behavior of awk code
> blocks to assign variables on the command line, so the following now
> work.
> #+begin_src awk :var a=2
> BEGIN{ print a; }
> #+end_src
> #+RESULTS:
> : 2
Greg Minshall writes:
> hi. i just wandered down a rathole others could avoid. the following
> program fails in (what was to me) a mysterious way:
>
> #+BEGIN_SRC awk :var a=2
> BEGIN{print $a;}
> #+END_SRC
>
>
> it turns out values for variables to awk need to be strings (rather than
hi. i just wandered down a rathole others could avoid. the following
program fails in (what was to me) a mysterious way:
#+BEGIN_SRC awk :var a=2
BEGIN{print $a;}
#+END_SRC
it turns out values for variables to awk need to be strings (rather than
a number, as above). below is a patch t
12 matches
Mail list logo
