Re: Waiting until Acrobat closes file

2006-05-28 Thread Christian Huldt
28 maj 2006 kl. 02.47 skrev Chris Devers: On Sun, 28 May 2006, David Cantrell wrote: if instead you're doing something like ... system('open', '/Applications/Acrobat.app'); then you'll need to: wait around until Acrobat appears in the process table; wait around until that PID

Re: Waiting until Acrobat closes file

2006-05-28 Thread David Cantrell
Joel Rees wrote: Except, of course, this is Unix, and we have i-nodes, and the system knows how to hold onto a file until all links are gone, as I recall. Ergo, just delete it once you know the viewer has it open, IIRC. Which is fine, but if you use 'open' to fork off and run Acrobat in

Re: Waiting until Acrobat closes file

2006-05-28 Thread wren ng thornton
--- Chris Devers wrote: Really?? In my experience, the `open` command immediately returns control to the controlling process (the shell, or whatever else invoked it (pine etc)) without waiting for the `open`ed application to finish, or for that matter even to finish launching. Others

Re: Waiting until Acrobat closes file

2006-05-28 Thread Joseph Alotta
This may not be what you are looking for, but if you were to name the files in a way that uses the date, then you can just delete the old ones the next day. Joe. On May 28, 2006, at 5:34 PM, wren ng thornton wrote: --- Chris Devers wrote: Really?? In my experience, the `open` command