On Sun, 18 Aug 2002, Mikhael Goikhman wrote:
> Funny, the following is incorrect in bash and ksh:
>
> % xterm &; xterm
>
> But this is correct in tcsh, zsh, ash and csh. If you put a command
> with & in parentheses it should work in all shells:
>
> Exec (xterm &); (xterm &); (xterm &)
>
Yeah. I've seen the above "% xterm &; xterm" fail a million
times and never learn because it doesn't make any sense to
me. I think its a bug. Heres a line from a script where I use
the semi-colon which works just fine:
cd /usr/src; rm -rf $GCC; tar -zxvf $GCC.tar.gz;
I guess the & confuses it. Somebody should send a report
to bug-bash@gnu.org to get clarifition. ( not me. I already
got a bug report pending) I quickly tried this
set -o monitor # enable jobs
set -b # enable immediate reporting of SIGCHLD
xterm &; xterm
to enable job control and it still doesn't like it.
Anyway the second form "Exec (xterm &); (xterm &); (xterm &)"
does the trick. Sometimes something is funny is happening on
the net like somebody trying to use your machine as a relay
when they have no business doing so and I want to fire up a
whole bunch of tails on the logs really quick. Now I can do it.
Bruce
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
