On Mon, April 25, 2005 2:17 pm, Sam J said:
> Ken Hayber wrote:
>> Kristoffer wrote:
>>> I did something i should'nt have done today: i copied over the wrong
>>> files. It would have been so nice to just 'undo' that operation like
>>> one can with a certain other filemanager for a certain other os, but
>>> I can't.
> Explorer's "Undo" function has got me out of a tight spot or two, mainl=
> due to it's IMHO rather poor drag and drop model where it will move a f=
> or folder if it's on the same disk - without asking! Thank goodness I c=
> set both Konqueror and ROX to pop up a menu. Now if only Konq would
> auto-resize the window and icons like ROX does, that would be bliss...
>>> Now. Maybe I can do this _somehow_ with the CLI, with _some_ app out
>>> there; but that's besides the point. The point is: Why can't I do thi=
>>> in ROX? And: Will it be implemented? And lastly: Why not? -- if that
>>> is the case.
>>> Kristoffer Fossg=E5rd
>> What you probably want (I know I do) is some kind of
>> version-control-filesystem, that remembers previous versions of files.
>> Like CVS, DAV, or VMS' filesystem. Maybe something like this could be
>> done using FUSE. I think it would be nice for /home and maybe /etc to
>> have this. It is probably overkill and slow for the whole filesystem
> "Check out" (sorry, couldn't resist) Joey Hess's (Debian Installer
40 lashes for you.
> developer I do believe, among other things) article "Keeping Your Life =
> Subversion"  for some interesting reading. I'd love to be able to do
> something like that, but my college insists on Windows and since that's
> only other place I really use computers so far, I have no use for the
> replication aspect of it.
> I rather like the idea of never saving anything, to instead mark a
> and to be able to go back to any previous revision, as described in Set=
> Nickell's feature list  for GNOME Storage. It's like taking the
> advantages of writing on paper (you can't "lose" anything unless you
> physically lose the storage medium) and the advantages of using a
> It sounds like what the original poster was suggesting was something
> simple like Explorer's Undo function, i.e. a history of what you've don=
> which would undoubtedly be useful in itself.
AFAIK that Undo feature only undoes deletes and moves/renames. If you
'copy over' files then you're screwed unless you have revision history or
something like it.
Otherwise I agree with you.
However, I think this is one of those things that shouldn't be done at th=
application level, but rather at the filesystem level, so all
applications/tools have an equal footing.
This appears to be what I'm talking about: http://wayback.sourceforge.net=