[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Hi Volker and Gabriele,
for your help.
I'll try to experiment with that too in my own context !
Regards,
Gerard
> VN> How about [ call/output "rebol --cgi script.r" ] ? should write to output?
>
> Hmm, -c does not work in a MS-DOS window, but does with
> CALL/OUTPUT. That's good to know. :-)
>
> >> call/output {rebol.exe -c --do "print 'hello quit"} s: ""
> == 0
> >> print s
> hello
>
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Hi Gabriele, Gabriele wrote: == > GC> 2. The Call/output doesn't seem to create and fill the > GC> expected file with the results outputted when used - an empty > GC> file is created > GC> and nothing else. > > CALL/OUTPUT actually works correctly on Windows. You can also > redirect the output to a string, like: > > >> call/output "ping localhost" s: "" > == 0 > >> print s > Thanks for demonstrating this way of doing things. I will be VERY useful to many of us I think. > > GC> call/output "E:\Installation de logiciel\REBOL\View 1.3 - > GC> Betas testing\rebview1224031.exe -s xcode.r" %results.txt > GC> print read > GC> %results.txt > > REBOL does not send output to STDOUT on Windows, so CALL/OUTPUT on > REBOL itself isn't useful. > AH! AH! This is the real reason I presume. Seems I misconceived the way it would work as I skipped the fact that the CALL would redirect all the outputted output even the results coming from the newly called copy of REBOL. I could have done better but sometimes evidence is in front of our face without our eyes seeing it. An old "déjà vu" pattern that still survives... many many years! Thanks for this one. Now at least I know that I was looking for is not feasible in the way hoped to do so.I > GC> As it currently stands I don't see the real usefulness of > GC> having a script like easy-vid.r or any other script that would > GC> lauch > GC> another REBOL script during some CLICK and PLAY demo app > GC> - as I planned it initially... > > To launch another REBOL script there's LAUNCH. > Thanks. I'll throw an eye on it too. May be it could have been shorter than learning to use the CALL mechanism. But as I don't know the details I will not speculate here. I'll first go and learn more. Regards, Gerard -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Hi Volker,
- Original Message -
Volker Wrote:
> > call/output "E:\Installation de logiciel\REBOL\View 1.3 - Betas
> > testing\rebview1224031.exe -s xcode.r" %results.txt print read %results.txt
>
> first look: can you check for whitespace-handling? i would expect you need ""
> around the exe-path, like
> call {"wsp path\rebol.exe" args}
> in your example i expect "E:\Installation" is called with the rest as
> argument.
>
I will look at but seems the exec worked fine and the results correctly displayed
on the console. Seems the output has something to do with the mystery - and a
few seconds ago I received the reason from Gabriele. See its answer by yourself.
Clearly it is erroneous for me to think that CALLING a copy of REBOL ensures
the output of the running script is also redirected since REBOL normally doesn't
send its output to STDOUT. This is a misconception I had about the way I
planned my solution as it is often the case.
I simply skipped the fact that this is the second copy of REBOL that must be
redirected and not only the first one...
Thank you,
Gerard
P.S. I will nevertheless try your suggestions just to see the effects I can get from
them
even if I don't hope to receive the results in a file as planned working in this
direction.
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Hi Petr, IIRC I already tested it and saw no difference. But I'll try the many suggestions Volker offered me and I'll come back soon. Thanks, Gerard - Original Message - From: "Petr Krenzelok" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 12, 2004 4:11 AM Subject: [REBOL] Re: SHELL cmd exec using CALL in View 1.3 > > Gerard Cote wrote: > > >Oups! I forgot to join the entire file as a reference to those interested. > >Here it is. > > > >Regards, > >Gerard > > > >P.S. I also looked back to the REBOL Command SHELL interface (Official Docs) and it > >seems that one way to let REBOL do leave an > >executed console window opened would necessitate a new switch to use when launching > >REBOL as in REBOL -k(for keep open) > >and this would be bypassing the normal internals REBOL is using. In normal case > >REBOL automatically adds intrnally the /c switch > >with the CALL under Windows OS as if the coders had used CALL/c to automatically > >close the console window when finished... > > > > > > > What about call/wait? > > -pekr- > > >-- Binary/unsupported file stripped by Ecartis -- > >-- Type: text/x-rebol > >-- File: my-easy-vid-coder.r > > > > > > > > > > > -- > To unsubscribe from this list, just send an email to > [EMAIL PROTECTED] with unsubscribe as the subject. > > -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Hi Volker,
On Monday, January 12, 2004, 4:27:37 PM, you wrote:
VN> How about [ call/output "rebol --cgi script.r" ] ? should write to output?
Hmm, -c does not work in a MS-DOS window, but does with
CALL/OUTPUT. That's good to know. :-)
>> call/output {rebol.exe -c --do "print 'hello quit"} s: ""
== 0
>> print s
hello
Regards,
Gabriele.
--
Gabriele Santilli <[EMAIL PROTECTED]> -- REBOL Programmer
Amiga Group Italia sez. L'Aquila --- SOON: http://www.rebol.it/
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Am Montag 12 Januar 2004 11:52 schrieb Gabriele Santilli: > Hi Gerard, > > REBOL does not send output to STDOUT on Windows, so CALL/OUTPUT on > REBOL itself isn't useful. > How about [ call/output "rebol --cgi script.r" ] ? should write to output? > > Regards, >Gabriele. -Volker -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Hi Gerard, On Sunday, January 11, 2004, 10:48:35 PM, you wrote: GC> 2. The Call/output doesn't seem to create and fill the GC> expected file with the results outputted when used - an empty GC> file is created GC> and nothing else. CALL/OUTPUT actually works correctly on Windows. You can also redirect the output to a string, like: >> call/output "ping localhost" s: "" == 0 >> print s Esecuzione di Ping GABRIELE [::1] con 32 byte di dati: Risposta da ::1: durata<1ms Risposta da ::1: durata<1ms Risposta da ::1: durata<1ms Risposta da ::1: durata<1ms Statistiche Ping per ::1: Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi), Tempo approssimativo percorsi andata/ritorno in millisecondi: Minimo = 0ms, Massimo = 0ms, Medio = 0ms >> GC> call/output "E:\Installation de logiciel\REBOL\View 1.3 - GC> Betas testing\rebview1224031.exe -s xcode.r" %results.txt GC> print read GC> %results.txt REBOL does not send output to STDOUT on Windows, so CALL/OUTPUT on REBOL itself isn't useful. GC> As it currently stands I don't see the real usefulness of GC> having a script like easy-vid.r or any other script that would GC> lauch GC> another REBOL script during some CLICK and PLAY demo app GC> - as I planned it initially... To launch another REBOL script there's LAUNCH. Regards, Gabriele. -- Gabriele Santilli <[EMAIL PROTECTED]> -- REBOL Programmer Amiga Group Italia sez. L'Aquila --- SOON: http://www.rebol.it/ -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Am Sonntag 11 Januar 2004 22:48 schrieb Gerard Cote:
> Hi list,
> call/output "E:\Installation de logiciel\REBOL\View 1.3 - Betas
> testing\rebview1224031.exe -s xcode.r" %results.txt print read %results.txt
first look: can you check for whitespace-handling? i would expect you need ""
around the exe-path, like
call {"wsp path\rebol.exe" args}
in your example i expect "E:\Installation" is called with the rest as
argument.
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Gerard Cote wrote: >Oups! I forgot to join the entire file as a reference to those interested. >Here it is. > >Regards, >Gerard > >P.S. I also looked back to the REBOL Command SHELL interface (Official Docs) and it >seems that one way to let REBOL do leave an >executed console window opened would necessitate a new switch to use when launching >REBOL as in REBOL -k(for keep open) >and this would be bypassing the normal internals REBOL is using. In normal case REBOL >automatically adds intrnally the /c switch >with the CALL under Windows OS as if the coders had used CALL/c to automatically >close the console window when finished... > > > What about call/wait? -pekr- >-- Binary/unsupported file stripped by Ecartis -- >-- Type: text/x-rebol >-- File: my-easy-vid-coder.r > > > > -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
[REBOL] Re: SHELL cmd exec using CALL in View 1.3
Oups! I forgot to join the entire file as a reference to those interested. Here it is. Regards, Gerard P.S. I also looked back to the REBOL Command SHELL interface (Official Docs) and it seems that one way to let REBOL do leave an executed console window opened would necessitate a new switch to use when launching REBOL as in REBOL -k(for keep open) and this would be bypassing the normal internals REBOL is using. In normal case REBOL automatically adds intrnally the /c switch with the CALL under Windows OS as if the coders had used CALL/c to automatically close the console window when finished... -- Binary/unsupported file stripped by Ecartis -- -- Type: text/x-rebol -- File: my-easy-vid-coder.r -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
