Hi, Rene Engelhard: > > > > $ libreoffice & > > $ libreoffice /tmp/something.odt; rm /tmp/something.odt > > And why are you doing that then? Sorry, I'd understand it in the second > case, but... > Doesn't matter. Maybe the user is editing the next Great American Novel at the time; the point is that LO is running in the background while this takes place.
> > This is because the second command signals LO to open the document and then > > returns immediately, instead of waiting for the file to be actually opened. > > Of course it tells the already running process to open the file. What else? It should wait until the 'receiving' LO process indicates that it has in fact opened the file! The problem is that as soon as mutt notices that the LO process it forked has died, it feels free to delete the temporary file it created. > I *think* it's ooplash.bins fault. This is not a splash screen problem. -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
