Re: Moving open files

Mumia W. wrote:

Dotan Cohen wrote:
2008/7/7 Derek Broughton <news@xxxxxxxxxxxxxx>:
[...] No, sorry, I don't agree with that. You may not like the
[behaviour, but it
is logical. Would you still think it's a bug if the user had just
_copied_
the original, and then there were two different versions? I can't do
exactly the same thing with Word, because it _does_ lock the file, but
that's a design choice.

In my opinion, and the opinion of he who 'lost' his data, there should
be a lock file.
[...]

Even if there were a lock file, the result of moving the files using
'mv' would be the same--data loss. 'Mv' is a very simple application
that doesn't know about file locks, and it might move *both* the
original and lock files to a new location--effectively destroying the
lock.

Well, not really. First, there was no loss of data. I'm sorry the user
couldn't find it, but really it isn't rocket science to figure that if OO
opened a file in location A and somebody proceded to move it to location B,
OO may not know anything about that move. That said, if OO kept the file
open, then mv could move it elsewhere, but OO would still write to the
_file_ not create a new file with the original name. Plus, it really is
badly behaved if it writes a "new" file - when it should know it's
modifying an old file - and doesn't bother to inform the user that the file
moved. _That_ should be fairly simple to both fix and get attention for.
--
derek


--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: Moving open files
    ... Would you still think it's a bug if the user had just _copied_ ... In my opinion, and the opinion of he who 'lost' his data, there should ... Even if there were a lock file, the result of moving the files using ... The only safe way to move files when OOo is open is to do that within ...
    (Ubuntu)
  • Re: "Lock file has grown too large"
    ... The link above is to an eight year old, but still current Borland article on ... > the only problem was that the lock file, as described below, grew ... > Last week we changed the application to create the PRIV directory inside ... > Is it in fact an absolutely hard-coded forever there bug in Paradox on ...
    (comp.databases.paradox)