I gave up on Windows. Yes Tup was the straw that broke that camel's back.
Still not out of the woods though. Here's a Tupfile:
: |> touch %o |> pass.out
: |> bash -c "touch %o" |> pass2.out
: |> emacs --quick --batch --eval '(shell-command "touch %o")' |>
fail.out
: |> emacs --quick --batch --eval '(call-process "touch" nil nil nil
"%o")' |> fail2.out
The first two work; the others don't. Nothing gets written. However,
those commands work when I run them directly from the shell. And the lisp
expressions of course work when I run them directly from emacs.
So this is only a problem when I'm running them through Tup.
For the shell-command version, the output says "Shell command failed with
code 125 and no output". And Tup says that it "expected to write
"fail.out" but didn't.
The call-process version (which is just a stripped-down version of what
shell-command does), is the same but less verbose.
Am I doing something wrong? Should I expect things like this to work?
This is the minimum test case that I know how to make which demonstrates
my requirement, which in practice involves exporting org documents.
Any help is greatly appreciated.
Thanks,
Gavin
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
