%% Alexander Kotelnikov <[EMAIL PROTECTED]> writes: ak> LIE. Read standards, please.
Paul> Single UNIX says: Paul> Paul> If the process image file is not a valid executable object, execlp() Paul> and execvp() use the contents of that file as standard input to a Paul> command interpreter conforming to system(). In this case, the Paul> command interpreter becomes the new process image. ak> are execlp and execvp all exec's you know? For heaven's sake. The standard doesn't say that _only_ these exec's must work that way, it says _at least_ these exec's must work that way. I've been using UNIX systems of various flavors for 17+ years and I can't remember _ever_ using one that didn't handle this properly (where if you invoked a script from a shell and the script didn't have a legal "#!" interpreter line, it wasn't given to sh). The current code works, and works everywhere it's been tried. If you have a situation where it doesn't work, file a bug. If you just don't like the way it looks, get over it. -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ------------------------------------------------------------------------------- These are my opinions---Nortel Networks takes no responsibility for them. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
