From: David MacMahon <davidm@...>
Date: 2013-06-04T02:29:00+09:00
Subject: [ruby-core:55278] Re: [ruby-changes:28951] zzak:r41003 (trunk): * process.c: Improve Process::exec documentation


On Jun 3, 2013, at 8:26 AM, Tanaka Akira wrote:

> 2013/5/31 zzak <ko1@atdot.net>:
>> zzak    2013-05-31 17:58:06 +0900 (Fri, 31 May 2013)
>> + *  The standard shell always means <code>"/bin/sh"</code> on Unix-like systems,
>> + *  same as <code>ENV["RUBYSHELL"]</code>
>> + *  (or <code>ENV["COMSPEC"]</code> on Windows NT series), and similar.
> 
> I'm afraid that someone thinks RUBYSHELL affects on Unix.
> Is it impossible interpretation?

I agree that this new wording could be interpreted to imply that ENV["RUBYSHELL"] is the same as "/bin/sh" on Unix-like systems, even though this is not the intended meaning.  I think the new wording of this particular sentence is actually less clear than the original.  Maybe something even more explicit would be better:

The "standard shell" is OS dependent.  On Unix-like systems it is always <code>/bin/sh</code>.  On Windows systems it is specified by <code>ENV["RUBYSHELL"]</code> (or <code>ENV["COMSPEC"]</code> on Windows NT).

I'm not sure about the technical details of the behavior on Windows systems in my suggested wording, but at least it makes a sharper distinction between Unix and Windows systems (IMHO).

Dave