Well, this isn't required on platforms other than Windows, which, as I
understand it, is a minority within Rails developers.
Perhaps adding a note to the top that says "If on Windows, you'll need
to add `ruby` to the beginning of these commands" would be helpful,
but adding it to the beginning of all of them is unnecessary.
I think Jeremy’s suggestion is the way to go. However, in Rails 3
script/* is gone, and published guides are frozen.
So, all those examples now read “rails command …” in docrails, which
is the new thing (preferred over script/rails).
– fxn
PS: rails command is not portable at this moment, there’s a pending
patch for that.
Well now that’s ironic! I though the only reason for adding all the new behavior to the rails command was so that the usage syntax could now be platform-independent.
Is there some other reason why the rails command is now a wrapper for script/*? Maybe I’m missing something obvious.
Problem is it is implemented using exec at this moment. That is not
portable because it needs script/rails to be executable.
I submitted a patch precisely because of this thread. The message is
that the rails command is the way to go, but if it is not portable
documentation will need ugly warnings as the ones Rajinder needed for
Windows: