Gabriele Thanks. I guess from you suggestion, it isn't easy (or perhaps not even possible) for the called rebol session to have its own terminal session.
On 27 Dec 2008, at 19:23, Gabriele Santilli wrote: > > On Sat, Dec 27, 2008 at 6:36 AM, Peter W A Wood <[email protected]> > wrote: > >> call "/Applications/Rebol/rebol -cs called.r" > > I assume you are on OSX, or some other Unix. You'll want to try > something like: > > call "/Applications/Rebol/rebol -qws called.r >/dev/null </dev/ > null" I'm testing on OS X, the live system is on Windows. > If the script output is of any importance, you'll want to redirect it > to a log file instead, eg. > > call "/Applications/Rebol/rebol -qws called.r >>> /path/to/logfile.txt </dev/null" It is useful to see the output during testing. It looks as though re- directing the output will be the best option. For compatibility, it would seem best to use the /output refinement. I tried the /output refinement with an "out" argument of #[none] which I though would be the equivalent of ">/dev/null" but it had no effect. Is this the expected behaviour? Regards Peter When I tried the -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
