[scilab-Users] "unix" or "unix_g" ... use + portability

Antoine Monmayrant antoine.monmayrant at laas.fr
Thu Jun 7 11:50:47 CEST 2012


On 07/06/2012 09:15, paul.carrico at free.fr wrote:
> Dear All,
>
> AS ever spoken herebellow, I'm working on the portability from Windows OS to Linux oS including bash instructions ....
>
>
> Original code under Windows (works fine):
> commandline_BACON = "( ECHO ;INPUT """ + INPUT_FILE_NAME + ".dat""&  ECHO ;.FIN&  ECHO;.STOP ) | " + samcef_path + "\Bacon NOM=" + INPUT_FILE_NAME +" SAM_PREFIX=SAM_TMPDIR=banque=" + INPUT_FILE_NAME + ".dat "
> [rep,stat,err]=unix_g( );
>
>
> Nota :
> - INPUT + .FIN + .STOP are specific keywords of the solver ... and they lead to error with sh
> - I'm not "bash" skilled so I've not found the problem
> - I've ever tested both unix_g and unix scilab keywords ...
>
> Any advice or any doc on how to avoid this trouble ?
>
> thanks in advance
>
> Paul
>
>
>
>
>
> ----- Mail original -----
> De: "paul carrico"<paul.carrico at free.fr>
> À: users at lists.scilab.org
> Envoyé: Mercredi 6 Juin 2012 22:47:12
> Objet: [scilab-Users] "unix" or "unix_g" ... use
>
> Hi all,
>
> I'm currently rewriting programs (initially developped under Windows OS) on Linux OS ... and I've some troubles ...
>
> under Linux, why the following code does not work : unix('firefox') ... 'firefox is just for the example'
>
>
> from the help, 'unix' is equivalent to 'sh' ... on a terminal 'sh firefox' or simply 'firefox' works ????
>
> It's probably a stupid question, but I've many "command lines" to lauch from scilab ...
>
> Thanks
>
> Paul
>
> --
> To unsubscribe from this mailing-list, please send an empty mail to
> users-unsubscribe at lists.scilab.org
> To check the archives of this mailing list, see
> http://mailinglists.scilab.org/
>
> --
> To unsubscribe from this mailing-list, please send an empty mail to
> users-unsubscribe at lists.scilab.org
> To check the archives of this mailing list, see
> http://mailinglists.scilab.org/
>
>
Hi Paul,

Can you give us an example of what commandline_BACON really looks like 
once all the variables are evaluated (ie replaced by the string they 
code for)?
Did you try to run directly this commandline_BACON in  a unix terminal 
to see what it gives?
You might have in commandline_BACON some characters that have special 
meaning for the shell (like "&", "*", ">").

Antoine



More information about the users mailing list