Ludovic CourtÃs <ludovic.courtes@xxxxxxxx> writes: > Well, for each of those proprietary shells listed before, execution of > the script will _really_ halt when "unset ENV" is interpreted, > ie. "hello" will never show up on the screen. Did you try the script on one of those shells? Here it is again. If it doesn't print "hello", what is the output of "sh -x script? #!/bin/sh ENV=sdf readonly ENV as_unset=unset for as_var in ENV MAIL MAILPATH do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var done echo "hello" > running something like "unset ENV || echo failed" won't work. But the script doesn't do that; it does something more complicated than that. > IOW, it's not just a matter of hiding the message that says "this > variable is read-only". The message is being hidden, but the exit status is being followed. Or are you saying that the exit status of "(unset ENV)" is zero? _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
