system command

[Kenneth Brody]

Quoting Dennis Malen (Tue, 1 Nov 2005 16:00:08 -0500):

> Mark,
>
> Your riight! I owe you an apology. In my haste to get back to you I put
> / instead of \. That was only on my post.
>
> In any event, I did try what you posted and that did not work either.

What, exactly, did you try?  (There have been numerous suggestions.)

Can you define "did not work"?

If you simply added ">/tmp/out" to the system command, as was suggested
several times, then what exactly "didn't work" about it?  What, exactly,
ends up in the /tmp/out file?

> I Do have a suggestion on how to fix it..
>
> What I suggest is to create 2 files that reside in /tmp. File1 is the
> first part of the line up to the @rn. File2 is the rest of the line
> after @rn.

If it's not properly doing it as one step, breaking the exact same parts
it up into several steps won't do what you want, either.

> Then use:
>
> system "/tmp/file1"{@rn{"/tmp/file2"

I don't think "/tmp/file155555/tmp/file2" is an executable file.

> If it all resided in one file in /tmp it works perfectly by using the
> original text that worked on the unix command line.

Then what, exactly, does your SYSTEM command in filePro generate?  How
is it different from the "correct" text?

> My problem is breaking up the file. I could have the system command use
> ">" and ">>" to append info to a file and then execute that from filepro
> (system), but that only appends another line. I need it on the same
> line.

It appends exactly what you send it.  If you send it something with a
newline in it, then yes it will end up with a newline in it.

> What do you think??

Don't complicate things.  Fix the original problem, rather than jumping
through hoops to do it another way.

[...]
--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com