<br><br><div><span class="gmail_quote">On 11/8/06, <b class="gmail_sendername">Fiona Darbyshire</b> <<a href="mailto:f.darbyshire@gmail.com">f.darbyshire@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>I'm not sure whether "run sh" would work,but one can certainly run executables and shell scripts from within a SAC macro. I think what you're missing is the dollar sign in front of the commands. <br></blockquote>
</div><br>Thanks, it works fine with the dollar signs. Maybe they should be added in the manual.<br><br><br><span class="gmail_quote">On 11/8/06, </span><span id="_user_jcalkins@email.arizona.edu">Josh Calkins</span> <font color="#5b1094">
<<a href="mailto:jcalkins@email.arizona.edu">jcalkins@email.arizona.edu</a>></font><span class="gmail_quote"></span><span class="gmail_quote"></span><span class="gmail_quote"> wrote:<br><br></span><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
In the end, I used a shell script that created a macro<br>on the fly so I could change the shell commands based on bb variables<br>that I would periodically write out to a text file.<br></blockquote><br>That sounds familiar, but my approach doing that with the following syntax
<br>for arg in "$@"; do <br>echo "$arg" > $SACTMPFILE<br>done<br><br>does not work as I would like it. Did you use something similar?<br><br>Thanks, <br>Andreas<br>