1. Bash calls TCL, TCL calls Bash, 2nd Bash never reads input
in comp.unix.misc i read:
perhaps you should resolve these deficiencies -- not that there is anything
wrong with using tcl from bash or bash from tcl, but it doesn't appear
necessary in this case.
in terms of shell scripting you don't have much debugging experience, in
particular you don't appear to have used ``set -vx'' to expose the
operations occurring. which would lead to the real problem: you aren't
using enough quoting, which is causing ...
you have a test which expects certain arguments and they are not being
provided. you use bare variable expansion, which does not result in an
argument being created if the variable is unset or empty. let's look at
what that looks like using set -x.
my little test script, which is whittled down to just the problem, is:
[ $foo == 'Y' ]
executing this provides the following output:
+ '[' == Y ']'
./foo.sh: line 4: [: ==: unary operator expected
as you can see there is no argument before the == (which is non-standard
btw), because foo is empty. to ensure that an argument is created you need
to use quotes, i.e.,
[ "$foo" == 'Y' ]
which after expansion becomes:
+ '[' '' == Y ']'
there we see that there is an empty argument being provided.
3. Displaying system call buffers with dtrace?
4. Accelerated-X and Marimba stuff
5. Calling and display of aliases in a Kornshell script
6. remove csum_partial_copy
7. Displaying call stack
8. AIX 4.3.1 and Automounter
9. Display Call Stack
10. "can't open display" when I call xterm in crontab
11. system call/function to display free directory space
12. How to open/read a file during a function call in the networking kernel codes
13. Program hangs when calling read function