Ruby

=begin
Moving this to the feature request tracker.

Kernel#system's invoking /bin/sh is not 1.8.7 specific.
=end

=begin
Hi

SUS says

The environment of the executed command shall be as if a child process were created using fork(), and the child process invoked
the sh utility using execl() as follows:

execl(, "sh", "-c", command, (char *)0);

where is an unspecified pathname for the sh utility.

In other word, it doesn't refer SHELL environemnt. Now ruby does so too because it is easy understandable.
Moreover you can invoke zsh easily by you wrote or similar way.

=end

=begin
And if we accept this proposal, system() will lose user enviroment portability. e.g. csh has completely different syntax from /bin/sh. Thus, distributed ruby scripts will not be able to use system().

=end

=begin
On Fri, Nov 26, 2010 at 08:18, Motohiro KOSAKI [email protected]wrote:

And if we accept this proposal, system() will lose user enviroment
portability. e.g. csh has completely different syntax from /bin/sh. Thus,
distributed ruby scripts will not be able to use system().

Surely anyone using system() to execute a shell script will be using a
shebang (#!) line to specify the shell the script is supposed to be executed
by?

If you don't, you're likely to discover that ksh is the standard POSIX
shell, not sh; and then there's the whole issue of bash vs ash vs sh.

mathew

On Fri, Nov 26, 2010 at 08:18, Motohiro KOSAKI <[email protected]> wrote:

=end

=begin
2010/11/27 mathew [email protected]:

On Fri, Nov 26, 2010 at 08:18, Motohiro KOSAKI [email protected]
wrote:

And if we accept this proposal, system() will lose user enviroment
portability. e.g. csh has completely different syntax from /bin/sh. Thus,
distributed ruby scripts will not be able to use system().

Surely anyone using system() to execute a shell script will be using a
shebang (#!) line to specify the shell the script is supposed to be executed
by?
If you don't, you're likely to discover that ksh is the standard POSIX
shell, not sh; and then there's the whole issue of bash vs ash vs sh.

In practical world, peope who want distribute their own scripts are only using
ash subset. It works enough, I think.

=end