system command

[Fairlight]

Confusious (Kenneth Brody) say:
> Quoting Fairlight (Tue, 1 Nov 2005 18:32:53 -0500):
> 
> > ONLY to help -Ken- not have to waste more time.
> [...]
> > <QUOTE POSTER="DM" FORMAT="BROKEN_MAILER_LINEBREAKS">
> > Hello Everyone!
> >
> > I am on IBM AIX. I have 4.8 filepro soon to upgraded to 5.0.
> >
> > I would like to place the following string in a system command:
> >
> > echo "\033&oFvar searchnum=55555;CompileFile(\"260268.cs\");\015"
> >
> > When this line is executed on the command line it works perfectly.
> 
> Okay.  That generates this sequence:
> 
>     ^[&oFvar searchnum=55555;CompileFile("260268.cs");^M
> 
> (Where "^[" is ESCape and "^M" is Ctrl-M.)
> 
> According to Dennis, the filePro code generates this:
> 
>     ^[&oFvar searchnum=55555;CompileFile(\"260268.cs\");
> 
> The only difference is the filePro code generates extraneous backslashes,
> and the missing Ctrl-M.  I am going to assume that the Ctrl-M is there
> but not shown in his sample.

Right.  Look at what he said he wanted, which was (\"260268.cs\"). That's
what he -said- he wanted.  His code actually generated (originally, when I
tested it) (\260268.cs\).  My mods gave him what he -said- he wanted.  If
it wasn't elucidated clearly, Not My Problem.  It even had the backing of
his own code, in which he had fP code of (\\\""260268.cs\\\") which implies
that he -wanted- those extraneous backslashes.  

What can I say?  I gave a line that generated exactly what was requested.

mark->