The Ubuntu community has contributed 12357 ideas, 58479 comments, 1187050 votes
Idea
#9965: During copy, Nautilus should check files name before complaining about space
|
| |
410
|
|
|
Written by Hiéroglyphe the 17 Jun 08 at 10:35.
Category: System.
Related to:
Nothing/Others.
Status: New
|
|
|
Description
I've got a 1 Gb USB storage with an 800 Mb file on it.
When I want to copy an updated version of this file (same name), Nautilus warn me that the operation can't be done cause there is not enought space on the disk.
So I have to manualy erase the old file, empty the trashcan, and finaly copy the new file.
Therefore I suggest that Nautilus check files name when coping or moving operations BEFORE complaining about having not enought space left. (and then simply ask if we want to replace/rename/cancel)
Tags:
(none)
Attachments
 Bug #264585 : nautilus does not count files to replace before showing "not enough space"
|
|
Duplicates
Comments
|
Nxx wrote on the 17 Jun 08 at 11:40
| |
I think this deserves a bug report.
|
|
nevermind85 wrote on the 17 Jun 08 at 13:52
| |
Don't know... The way Nautilus replaces a file is by making a copy of it first and then removing the original... Still don't know how it would work, should it remove the file by itself first? what if the files have just the same name but are entirely different from each other? Seems dangerous to me, even when a warning could pop up...
|
|
elitepenguin wrote on the 17 Jun 08 at 18:35
| |
Nautilus sucks, that's a well known fact. I don't think that this is the problem of the Ubuntu folks, I rather think that the gnome people should fix this.
|
|
ethana2 wrote on the 17 Jun 08 at 22:51
|
Very yes
I like to think canonical does enough upstream work that they won't blow this off as 'not their problem'.
|
 droetker (Moderator) wrote on the 18 Jun 08 at 05:05
| |
So coiuld you file a bug at lauchpad for this please?
|
|
Wouter.de.Groot wrote on the 18 Jun 08 at 11:34
|
Basically, it should check it at the same time: suppose you replace the 800MB file with a 1.2GB one, instead. You'd have Nautilus asking you to replace it and then complain about space.
If it checks both it should come to the conclusion that even if you consent to replacing the file it won't work.
If the file would otherwise fit it will already know and then ask you about replacing the original. It could even indicate that renaming either file won't cut it because of space issues.
Supporting this, but just swapping the order might not be the best approach.
|
|
Craig73 wrote on the 25 Jun 08 at 23:07
|
I don't know - if I was replacing a file, how hard would it be for me to hit delete first?
A bug perhaps, but not even a very high priority one.
|
|
Mårten Woxberg wrote on the 26 Jun 08 at 20:25
|
Craig73, Imagine you're replacing a whole directory structure where some files are new but some are not.
Then you'll probably answer no to some files and yes to some, thus saving time on the copy.
You only want to "Replace newer files" but I don't think that options exists in Nautilus.
|
|
syberjj wrote on the 12 Jul 08 at 15:27
|
My idea was marked as a duplicate of this one but it also contains other things... would be cool if you could add the other stuff I wrote about to your idea, if not im gonna try te separate them again since your idea is after a bug fix and mine is ater general improvements in the copy system
thanks
|
|
saivann (Moderator) wrote on the 4 Sep 08 at 04:50
|
I reported a bug for this.
If you get issues of this kind in the future, please use launchpad to report bugs. Voting on bugs unfortunately don't help them to get fixed, providing informations to developer is much better ;)
|
Post your comment
|
|
|
