Re: [Gambas-user] Reply: No EXEC Output but Works in Terminal

2009-03-04 Thread Doriano Blengino
Jussi Lahtinen ha scritto: ... Well, I have to be more precise. Sorry mr. Person to have been too concise. I understand that docs are not the best, but I did understand them with just a little effort, thanks to other knowledges you perhaps miss. And I made a mistake when speaking of WAIT in comb

Re: [Gambas-user] Reply: No EXEC Output but Works in Terminal

2009-03-04 Thread Ron_1st
On Wednesday 04 March 2009, Jussi Lahtinen wrote: > I tried your code... (first I did move test.sh to execution folder). > With me, this; > EXEC ["sh", Application.Path &/ "test.sh"] TO sOutPut > works well. > > But this; > EXEC ["sh " & Application.Path &/ "test.sh"] TO sOutPut > does NOT work (n

Re: [Gambas-user] Reply: No EXEC Output but Works in Terminal

2009-03-04 Thread Ron_1st
On Wednesday 04 March 2009, A Person wrote: > Good Day . . . > > Thank You all except the one that told me to read the EXEC docs. Despite I understand it a little it is not fair. Still he was right. > I read that many times and tried many variations including trying getting > INPUT > and OUTP

Re: [Gambas-user] Reply: No EXEC Output but Works in Terminal

2009-03-04 Thread Jussi Lahtinen
I tried your code... (first I did move test.sh to execution folder). With me, this; EXEC ["sh", Application.Path &/ "test.sh"] TO sOutPut works well. But this; EXEC ["sh " & Application.Path &/ "test.sh"] TO sOutPut does NOT work (no output). So EXEC command is pretty picky. Benoit, comments? Als

[Gambas-user] Reply: No EXEC Output but Works in Terminal

2009-03-04 Thread A Person
Good Day . . . Thank You all except the one that told me to read the EXEC docs. I read that many times and tried many variations including trying getting INPUT and OUTPUT to work. But nothing worked. The one problem that I have with Gambas is that the docs are not adequate to a novice user. I t