I don't understand, why require "rubygems" is necessary in _no_wait processes. It shouldn't be, since we set up $LOAD_PATH with everything needed inside of it. Or don't we?
Jarmo On Jul 2, 5:22 pm, Hugh McGowan <[email protected]> wrote: > We talked offline and in his environment he's adding require > 'rubygems' to every script to get them working (independent of the > no_wait issue). Since this doesn't get pushed through in the LOAD_PATH > I had him set RUBYOPT=-rubygems and he's working now. > > This does expose an issue because the _no_wait methods fail silently. > I'll take a look to see if we can post an error when the command > fails. > > Hugh -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
