<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Date: Thu, 10 Sep 2009 21:34:45 -0400<br>
From: Fairlight <<a href="mailto:fairlite@fairlite.com">fairlite@fairlite.com</a>><br>
Subject: Re: USER command questions<br>
<br>
> Can anyone tell me how to use cp or mv with the USER command? Or is it just<br>
> garbage and I should go back to SYSTEM?
<br>
</blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You're assigning the 'move' "alias" (ie., USER handle or whatever the<br>
proper fP parlance for it is) first, there. And then you're essentially<br>
piping in arguments to it, rather than having them all as one command.<br>
<br>
In shell terms, what you're doing is essentially the same as:<br>
<br>
$ mv <<END<br>
> -f<br>
> /some/path<br>
END<br>
<br>
That's why 'mv' is bailing on you. It's not meant to be used that way.<br>
<br>
Forget using USER for 'mv'. It's nothing you get interactive feedback<br>
from, so USER is overkill. Assemble the entire command with arguments and<br>
feed it to SYSTEM for each file.<br>
<br>
Also, be VERY careful with dirlist. It has a filename length limitation<br>
that will bite you if the filenames are longer than the memory allocated to<br>
the function's memory storage.<br>
<br>
Back to the original: Only use USER when you require interactive feedback<br>
from and/or interactive data supply to a process. Neither 'mv' nor 'cp'<br>
fall into that category.<br>
<br></blockquote><div> </div><div>Thanks Mark! That was exactly the answer I was looking for! I will stick with SYSTEM for mv then, and OPENDIR/NEXTDIR for getting the filenames :) (thanks to John Esak for the demo on how OPENDIR's usage)<br>
<br>Tyler<br></div></div><br>