> Hmmm...was there any other problem with the (mis)feature than a
> tendency to trip over leading blanks and try to Exec exec exec....?
> If not, then this little patch should fix it up.
The problem for me was mostly that I use ;s in a couple of commands.
exec causes the second command to get lost. Obviously I could run sh
-c "command1 ; command2", and frankly that would have been OK by me,
though it would have been nice if I'd been warned someplace other than
the ChangeLog (I don't even recall any discussion about it before the
2.0.42 release). A better solution, IMO, would be to have two
Exec's, one that uses the shell, one that directly forks and exec's
the given command.
--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 617-271-3887
Email: dsg_at_mitre.org
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Apr 04 1997 - 07:48:32 BST