You are not logged in.

Overwrite timeout or postponing t/o question

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

p.alfa

Beginner

  • "p.alfa" started this thread

Posts: 27

  • Send private message

1

Monday, April 18th 2005, 1:57pm

Overwrite timeout or postponing t/o question

Hi all,
yesterday, while I was moving a lot of files from a computer to another, I got annoyed with konqueror's overwrite question.
Imagine you have a batch that will last for 30 minutes and you go out for lunch. When you return, you expect that job to be finished, but... a silly overwrite question blocked it all!!!

I would like to suggest this feature, that is a timeout for overwrite. If you do not answer, for example, for 30 seconds, a default action is taken. It could be overwrite, change name automagically and so on...

I would like to suggest another feature: what about postponing the overwrite question after the copy/move action is completed?
You have 10000 files to be copied/moved, 20 of them, stochastically placed, are already present on the destination. Instead of having 20 overwrite questions placed casually among the batch, what about having all of them concentrated in the end?

Let's discuss!!!

Bye bye,
Pietro

jacek

Trainee

Posts: 105

Location: Warsaw, Poland

Occupation: Student

  • Send private message

2

Monday, April 18th 2005, 2:20pm

RE: Overwrite timeout or postponing t/o question

Quoted

Originally posted by p.alfa
yesterday, while I was moving a lot of files from a computer to another, I got annoyed with konqueror's overwrite question.
Imagine you have a batch that will last for 30 minutes and you go out for lunch. When you return, you expect that job to be finished, but... a silly overwrite question blocked it all!!!

Source code

 
1

$ /bin/cp src/* dst/ -R
And no questions asked ;)

Quoted

I would like to suggest this feature,

http://bugs.kde.org/wizard.cgi

Quoted

I would like to suggest another feature: what about postponing the overwrite question after the copy/move action is completed?

You have 10000 files to be copied/moved, 20 of them, stochastically placed, are already present on the destination. Instead of having 20 overwrite questions placed casually among the batch, what about having all of them concentrated in the end?

I like this idea, but taking default action after a timeout might be annoying too --- what if you forget about it?

p.alfa

Beginner

  • "p.alfa" started this thread

Posts: 27

  • Send private message

3

Monday, April 18th 2005, 5:20pm

I would like to be as cool as you with html:), but I am not... so I'll use old usenet style...

> $ /bin/cp src/* dst/ -R

Check it out:)!!! -R or --reply=yes ? :)

[Placing every question in the end of a batch... or performing them by default after a timeout]

> I like this idea, but taking default action after a timeout might be
> annoying too --- what if you forget about it?

Very good question. I do not wheter KDE had to become distract-proof, but following this way can lead to a strage mechanism of overwriting in moving and copying... Let's read.

If file_A_new overwrites by default file_A_old, KDE places file_A_old, before deletion, to a directory, like trash dir. After a reasonable time - or wasted space - amount, the system deletes it without asking anything.

You can still undo that action, isn't it?

Bye,
Pietro

jacek

Trainee

Posts: 105

Location: Warsaw, Poland

Occupation: Student

  • Send private message

4

Monday, April 18th 2005, 6:28pm

Quoted

Originally posted by p.alfa
I would like to be as cool as you with html:), but I am not... so I'll use old usenet style...

It's good until you change the page width. The 80 character limit doesn't apply here ;)

Quoted

If file_A_new overwrites by default file_A_old, KDE places file_A_old, before deletion, to a directory, like trash dir. [...] You can still undo that action, isn't it?

Yes, that might be a solution, but still some reminder dialog should be shown, as Normal Users tend to forget about everything.