Dènis Riedijk wrote:
> On Thu, 2001-12-06 at 13:47, Kevin Brosius wrote:
> > Christian Kreibich wrote:
> > >
> > >
> > >
> > > Hi.
> > >
> > > Kevin recently committed code that hooks in Efsd's file move and copy
> > > functionality (yay! Cheers Kevin.), so you can move and copy files
> > > around. Please BE CAREFUL. This part of Efsd has seen some ad hoc
> > > testing, but you should be prepared for things going wrong etc. Don't
> > > move or copy important files that are not backed up etc. Maybe Efsd will
> > > do it right (so far it seems it does). Maybe it'll lose a file. Maybe
> > > it'll replace it with an image of my neighbour's dog.
> > >
> > > Kevin already included this warning in his commit message, I just
> > > thought I'd bring it to the list as well.
> > >
> > I second Christian's caution message. I've done some testing, but it's
> > not exhaustive. I'm also interested in feedback about dragging to other
> > applications. I've tested with xine CVS, which doesn't like to open
> > files with full URLs, so that's one failure.
> > What should work: dragging single and multiple files between views,
> > moving them by default, copying them when shift-click is used. Files
> Ehh, could copying please be Ctrl-drag and move Shift-drag like in
> windows ?? I think that is the default that most people expect. It could
> (should) offcourse become an option, but I think the defaults should be
> what most people expect.
This isn't windows... What does everyone think? I'm open to a vote for
the default behavior. While windows copies by default, I don't think
that's the most intuitive. For example, in a mail reader, I expect
dragging a message to a folder will move it, not copy it.
> > will not overwrite if they also exist in the destination, and the
> > operation will abort on the first conflict for multiple files. This
> > means that a multiple file move/copy may partially complete, but then
> > not finish all the files in the list. I haven't decided if this is a
> > feature or a bug... What do you all think?
> Ehhm, it is most usual that after the first comflict an error message
> pops up, and the rest of the operation is aborted.
Error message???? ;-) This is early CVS. There isn't any error
message. (Yet. Sorry!)
> What I would like the most is that a window would pup up and give 3
> options :
> 1. abort the rest of the operation.
> 2. abort the whole operation (undoing what has already been done)
> 3. continue operation and do all that doesn't fail (and don't pop up a
> window anymore on errors)
> But that's just my preference :-)
> I'll try to test it tonight, first I'll have to get my Linux to boot
> again after installing M$ XP...
> Does anybody have any tips on getting in Linux again after Win has
> erased LILO from my bootdisk ?? My root is on Software-RAID-0 :-(
Maybe efsd ops could have another option, something like 'complete all
possible' operations, just skipping the files that fail?