system command

Dennis Malen dmalen at malen.com
Tue Nov 1 16:17:01 PST 2005


Ken,

I'm forwarding to you my first post which shows you the line that works, 
which was:

echo "\033&oFvar searchnum=55555;CompileFile(\"260268.cs\");\015"

This works fine from the command line and also if I create an executable 
file and execute it from system command.

Dennis
----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at bestweb.net>
To: "Dennis Malen" <dmalen at malen.com>
Cc: <filepro-list at lists.celestial.com>; "pmahler" <pmahler at malen.com>
Sent: Tuesday, November 01, 2005 6:54 PM
Subject: Re: system command


> Quoting Dennis Malen (Tue, 1 Nov 2005 18:22:24 -0500):
>
>> Ken,
>>
>> The only sequence that seems to work is the creation of an executable
>> file and then having system command execute it. That works!
>
> That's because you're creating the file properly, whereas you're not
> building the system command properly.
>
>> system /tmp/file
>
> You have shown what your filePro code generates.  (Though we haven't
> seen the code that generates it.)
>
> What does "/tmp/file >/tmp/out" generate?  How does that compare to
> the direct-from-filePro output you posted earlier?  What is the actual
> filePro code that generated the direct-from-filePro output, so that we
> can see what needs to be changed so that your filePro code generates
> the "correct" output.
>
>> It works because I am not dealing with the interaction of "\" and the
>> open quotes on misinterpreting those characters with the system command.
>
> It "works" because you generate the correct output, rather than the
> incorrect output.
>
>> The executable already resides in a UNIX directory and does not go
>> through the interpretation that the system command may put it through..
>
> So, what is the "correct" output?
>
>> My only problem is attempting to use a variable for @rn. Attempting to
>> do that I need to have two files in the UNIX directory by breaking up
>> the line I originally posted day One. There would then be three parts.
>> File1, @rn and file2. I have to merge all three parts to get one line
>> that can be executed.
>> I could do it with an append command with the use of the system command
>> but that would put each piece on a separate line.
>
> Only if you include a newline in the output.  Appending to a file does
> not cause a newline to appear from nowhere.
>
>> I need to know if there is a command I can use to create the info on one
>> line and then execute it. Again, this approach takes out of the equation
>> the problem with the unique characters we are dealing with.
>
> I'm sure there is, but without knowing the exact sequence you're trying
> to generate, nor the filePro code you're using, people can only guess
> as to the answer.
>
> Again, why go through the complexity of creating three separate files,
> merging them into one, and executing the resulting file, when you could
> simply execute a SYSTEM command from within filePro to accomplish the
> same thing?
>
> [...]
>> As you can see if I can figure out how to put directory files and @rn on
>> one line I avoid the problem.
>
> How do you create them so that they're not on one line?  Without knowing
> that, we can't tell you how to not create multiple lines.
>
> [...]
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
>
>
> 




More information about the Filepro-list mailing list