260
votes
289
9
29
529
votes
538
10
9
Selected solution (#2):
Collapsed additional information
Written by
dcruz the 28 Apr 09 at 10:47.
The dialog should contain collapsed additional information from both files that the user could access, such as:
* size
* creation date
* modification date
* creator
* etc.
The dialog should contain collapsed additional information from both files that the user could access, such as:
* size
* creation date
* modification date
* creator
* etc.
202
votes
231
36
29
Selected solution (#3):
Diff view for text files
Written by
dcruz the 28 Apr 09 at 10:48.
Have an option the see the difference between both files it those files are textual.
Have an option the see the difference between both files it those files are textual.
338
votes
344
9
6
Selected solution (#4):
Have an option to suggest another name.
Written by
Lachu the 28 Apr 09 at 13:08.
GNOME should have option, like in KDE to write file in destination folder, but changes the name. When file should be named "SomeDocument", we should name it "SomeDocument-CurrentDate" or "SomeDocument-SourceFolderName".
GNOME should have option, like in KDE to write file in destination folder, but changes the name. When file should be named "SomeDocument", we should name it "SomeDocument-CurrentDate" or "SomeDocument-SourceFolderName".
229
votes
242
10
13
Selected solution (#5):
Have an option to rename old file
Written by
Akerbos the 29 Apr 09 at 19:52.
Similar to #3, but rename the existing file (kind of backup style)
I'd like this because most often you want the new file to be in effect at that moment while preserving the old one.
Similar to #3, but rename the existing file (kind of backup style)
I'd like this because most often you want the new file to be in effect at that moment while preserving the old one.
103
votes
123
17
20
Selected solution (#6):
Option to Merge files/folders
There should also be an option for merging files/folders together just as in some other operating systems. This will be especially beneficial in case of folders.
There should also be an option for merging files/folders together just as in some other operating systems. This will be especially beneficial in case of folders.
95
votes
110
21
15
Selected solution (#7):
Easy way to open both files for visual comparison
Written by
philip the 5 May 09 at 22:25.
The motivation is like #2 but for non-text files. If one or both files are images, office documents or media files, diff will not help. Clicking on the file name should open the file. This saves a visual search for the files in the directory.
The motivation is like #2 but for non-text files. If one or both files are images, office documents or media files, diff will not help. Clicking on the file name should open the file. This saves a visual search for the files in the directory.
42
votes
79
18
37
Selected solution (#8):
Previews of the files
Written by
philip the 5 May 09 at 22:52.
The dialog should contain pre-computed views of the files, so you don't have to wait for (say) the spreadsheet program to load and open the files. The views should be about 100x100 pixels large and should show a cropped, scrollable view of each file. When the user resizes the dialog,, the preview areas should show more or less of the files. Or, a larger preview can show as a tool tip when the mouse hovers over the small preview.
The dialog should contain pre-computed views of the files, so you don't have to wait for (say) the spreadsheet program to load and open the files. The views should be about 100x100 pixels large and should show a cropped, scrollable view of each file. When the user resizes the dialog,, the preview areas should show more or less of the files. Or, a larger preview can show as a tool tip when the mouse hovers over the small preview.
45
votes
63
8
18
Selected solution (#9):
nautulis: copy old file to trash before overwrite
Written by
bgfeldm the 12 May 09 at 13:01.
add an option to move old file to the trash before overwrite.
nautulis:
move file to trash before overwrite, if file is a text or document file below a preconfigured size such as 1 MB.
This way overwritten files can be retrieved at a dept of one.
Or you could make the trash bin a temporary source repository for overwritten/deleted files, only storing the diff of the text files, so you limit space taken up by the trash bin and have multiple restore points for files. The repository will be clear every time the user clears the repository or after a defined amount of days.
add an option to move old file to the trash before overwrite.
nautulis:
move file to trash before overwrite, if file is a text or document file below a preconfigured size such as 1 MB.
This way overwritten files can be retrieved at a dept of one.
Or you could make the trash bin a temporary source repository for overwritten/deleted files, only storing the diff of the text files, so you limit space taken up by the trash bin and have multiple restore points for files. The repository will be clear every time the user clears the repository or after a defined amount of days.
56
votes
79
6
23
Selected solution (#10):
Compare checksum of files.
Written by
Matir the 26 May 09 at 03:19.
Since md5sum is necessary for parts of apt and is installed in every base system, only files with the same name and different checksums need to be considered.
Since md5sum is necessary for parts of apt and is installed in every base system, only files with the same name and different checksums need to be considered.
139
votes
153
10
14
Selected solution (#11):
Relace If Newer button
Written by
Redge the 2 Jun 09 at 18:34.
See also solution #6. We now have a "Replace All" button, but I miss Windows Explorer's "Replace if Newer" option. Displaying extra info is all nice, but I want to be able to do file operations that don't require further user interaction. So let's add that "Replace All if Newer" button.
See also solution #6. We now have a "Replace All" button, but I miss Windows Explorer's "Replace if Newer" option. Displaying extra info is all nice, but I want to be able to do file operations that don't require further user interaction. So let's add that "Replace All if Newer" button.
25
votes
26
2
1
Selected solution (#12):
Push transfers requiring user feedback to the end of the queue
Written by
Redge the 8 Jun 09 at 00:07.
When doing file operations and Nautilus encounters conflicts or errors that require the user's feedback to resolve, Nautilus should first try to complete the rest of the queue and push the files needing feedback to the end. That way, if the user is AFK as much of the operation as possible will be done by the time he/she gets back.
When doing file operations and Nautilus encounters conflicts or errors that require the user's feedback to resolve, Nautilus should first try to complete the rest of the queue and push the files needing feedback to the end. That way, if the user is AFK as much of the operation as possible will be done by the time he/she gets back.
-3
votes
3
1
6
Selected solution (#13):
Use Desktop files.
Written by
Lachu the 19 Jun 09 at 08:47.
On situation in idea, Ubuntu should save file on different name and create Desktop file to it. Many user uses only GUI application with file managers supporting Desktop Files.
On situation in idea, Ubuntu should save file on different name and create Desktop file to it. Many user uses only GUI application with file managers supporting Desktop Files.
37
votes
42
4
5
Selected solution (#14):
Check files below a certain size
Written by
korin43 the 18 Jun 09 at 20:58.
Decide on a on file size where it's faster to just check if it's an identical file than ask the user if they want to replace/skip. If the files with the same name are identical, we just skip them instead of presenting the replace/skip dialogue (since both options would have the same result).
Note: This would be a complete byte-for-byte comparison, not just a comparison of timestamps and name.
Here's the order that the system would check:
- Is there a file with the same name?
- Is it below the maximum size set to check? (we don't want to auto-check if it would be faster to ask the user. ex: 10 Gb file)
- Compare size
- Compare the two files (byte-for-byte), fail as soon as you find anything different (if the first byte of the new file is different, fail immediately instead of checking the whole file)
Note 2: Timestamps will not be compared. If the new file is identical with a different timestamp, the new timestamp should be applied.
Decide on a on file size where it's faster to just check if it's an identical file than ask the user if they want to replace/skip. If the files with the same name are identical, we just skip them instead of presenting the replace/skip dialogue (since both options would have the same result).
Note: This would be a complete byte-for-byte comparison, not just a comparison of timestamps and name.
Here's the order that the system would check:
- Is there a file with the same name?
- Is it below the maximum size set to check? (we don't want to auto-check if it would be faster to ask the user. ex: 10 Gb file)
- Compare size
- Compare the two files (byte-for-byte), fail as soon as you find anything different (if the first byte of the new file is different, fail immediately instead of checking the whole file)
Note 2: Timestamps will not be compared. If the new file is identical with a different timestamp, the new timestamp should be applied.
21
votes
29
10
8
Selected solution (#15):
Add "auto" option to replce/skip pop-up
This gives the user the option to replace/skip if they already know whether the file is identical or not, or don't want to risk replacing an important file. But if they don't know if the files are identical, then they can press the auto button.
It would look something like this:
|Auto| |Auto all| |Replace| |Replace all| |Skip| |Skip all|
This gives the user the option to replace/skip if they already know whether the file is identical or not, or don't want to risk replacing an important file. But if they don't know if the files are identical, then they can press the auto button.
It would look something like this:
|Auto| |Auto all| |Replace| |Replace all| |Skip| |Skip all|
25
votes
25
0
0
Selected solution (#16):
Show context for the differences
The dialog should attempt to show the differences between the files if they are in a recognizable format. For example, if the files are images, show both images, along with file size and date. This will allow the user to easily make a decision about whether to replace the file. The destination filename could also be an editable field to allow the user to change the name and have the copy continue under the new name. If the file were an audio file then it could display bitrate, sample rate, length, etc.
Here's an example dialog box from Directory Opus on Windows which demonstrates this:
The dialog should attempt to show the differences between the files if they are in a recognizable format. For example, if the files are images, show both images, along with file size and date. This will allow the user to easily make a decision about whether to replace the file. The destination filename could also be an editable field to allow the user to change the name and have the copy continue under the new name. If the file were an audio file then it could display bitrate, sample rate, length, etc.
Here's an example dialog box from Directory Opus on Windows which demonstrates this:
<img src="http://img20.imageshack.us/img20/4432/sreplacey.png">
836
votes
846
4
10
Selected solution (#17):
Continue copying the files that doesn't need confirmation
Written by
pgdx the 31 Jul 09 at 08:09.
The copying of the rest of the files should continue and the files in question should be queued until the user decides what to do with this.
The copying of the rest of the files should continue and the files in question should be queued until the user decides what to do with this.
164
votes
209
42
45
Selected solution (#18):
Try to read ahead for dialogue-requireing issues
When you do a large transfer, it could try to calculate exactly what needs to be moved where first, so that the user does not have to sit there to make sure there are no conflicts.
When you do a large transfer, it could try to calculate exactly what needs to be moved where first, so that the user does not have to sit there to make sure there are no conflicts.
62
votes
114
39
52
Selected solution (#19):
Avoid overwriting the same file.
Written by
pubsbin the 8 Aug 09 at 01:12.
There are some easy tests for checking if two files (in two different folders) are the same file. From the easy ones (metainformation, size, name), checking some positions (sampling) and, finally, comparing them entirely.
If Nautilus uses those easy equality checks, it could avoid copying equal files. Even if you compare the whole file, a read is faster than a write.
There are some easy tests for checking if two files (in two different folders) are the same file. From the easy ones (metainformation, size, name), checking some positions (sampling) and, finally, comparing them entirely.
If Nautilus uses those easy equality checks, it could avoid copying equal files. Even if you compare the whole file, a read is faster than a write.
151
votes
157
11
6
Selected solution (#20):
"No to ALL"
Written by
don1500 the 12 Aug 09 at 20:20.
Most of the time I have this problem I run into it when moving music files. There is a "Yes to ALL" but no "No to All". All I want are the files that are on the source but not on the target. "Overwrite if Newer" is close and a good suggestion, but sometimes I don't want to overwrite the old file. Sometimes you want to overwrite the older version, and with "Yes to All" you still have that option. Maybe adding both "Overwrite if newer" AND "No to ALL" is the answer. I think this would be the easiest to implement. This is also the K.I.S.S. answer.
Most of the time I have this problem I run into it when moving music files. There is a "Yes to ALL" but no "No to All". All I want are the files that are on the source but not on the target. "Overwrite if Newer" is close and a good suggestion, but sometimes I don't want to overwrite the old file. Sometimes you want to overwrite the older version, and with "Yes to All" you still have that option. Maybe adding both "Overwrite if newer" AND "No to ALL" is the answer. I think this would be the easiest to implement. This is also the K.I.S.S. answer.
83
votes
109
16
26
Selected solution (#21):
Use a 'For All' Checkbox to Simplify Things
Simple enough, instead of having 'Replace All' and 'Skip All' have a check box 'For All'.
Obviously, the actual thing would look a bit more professional than the one I made in Gimp.
Simple enough, instead of having 'Replace All' and 'Skip All' have a check box 'For All'.
<img src="http://dl.getdropbox.com/u/1217030/Ubuntu%20Brainstorm/replace%3F.png">
Obviously, the actual thing would look a bit more professional than the one I made in Gimp.
14
votes
23
20
9
Selected solution (#22):
warn when deleting a folder with a copied file in it.
Written by
caleb the 21 Aug 09 at 08:54.
I have gotten into the bad habit of copying a file deleting the parent folder, and pasting it elsewhere. Ubuntu should warn when deleting a copied file's folder.
I have gotten into the bad habit of copying a file deleting the parent folder, and pasting it elsewhere. Ubuntu should warn when deleting a copied file's folder.
8
votes
8
1
0
Selected solution (#23):
Advanced File Operations (AFO :D)
Written by
Chronos the 29 Aug 09 at 14:46.
Create a more advanced "thread" based queuing system for file operations. Its possible to make it simple, no need to make it complex. Read below:
Seriously, in Total commander i used a lot the function to not just copy files at once and send the process in the background, but to push F2, and create a list of the operations where(!) the list is a queue. So the processes are not running at the same time to slow things down. We can even make this better. Imagine you have 4 drives. A B C and D. You want to copy 3x6 folders/files from A to B and vice versa. It takes long, so you start to copy/move/whatsoever to work on C and D (like before from C to D and vice versa). To make all these operations (4direction) run at the same time slows the computer slow down(no wonder why).
We could create two thread with two queues in this case.
In summary, A and B would process their queue, processing files the fast as possible, and separately C and D would do their things as well.
We could make it automatic maybe, that if we are making file operations to or from one partition/hardware, at default it would create a queue, what (with a push of a button) would appear from the already used window(dont know the name). This queue would make sure that only one operation is active at a time, making hardware sweat less, and operations faster.
Maybe i'll do a mockup if i have time.
This is just an idea, we can modify it.
Cheers,
David
Create a more advanced "thread" based queuing system for file operations. Its possible to make it simple, no need to make it complex. Read below:
Seriously, in Total commander i used a lot the function to not just copy files at once and send the process in the background, but to push F2, and create a list of the operations where(!) the list is a queue. So the processes are not running at the same time to slow things down. We can even make this better. Imagine you have 4 drives. A B C and D. You want to copy 3x6 folders/files from A to B and vice versa. It takes long, so you start to copy/move/whatsoever to work on C and D (like before from C to D and vice versa). To make all these operations (4direction) run at the same time slows the computer slow down(no wonder why).
We could create two thread with two queues in this case.
In summary, A and B would process their queue, processing files the fast as possible, and separately C and D would do their things as well.
We could make it automatic maybe, that if we are making file operations to or from one partition/hardware, at default it would create a queue, what (with a push of a button) would appear from the already used window(dont know the name). This queue would make sure that only one operation is active at a time, making hardware sweat less, and operations faster.
Maybe i'll do a mockup if i have time.
This is just an idea, we can modify it.
Cheers,
David
32
votes
43
12
11
Selected solution (#24):
Pile up a list of action needed files.(Use with Solution #1)
The list would list all the files that need conformation and let u handle them with check boxes. ( A Select All/None combo button and an Invert Selection button are a must for such a list. Then double clicking a listed directory should select all in the directory.)
Then by for example pressing Overwrite or a Do Nothing button the action would affect all selected files. After which you can continue such steps until the List is gone or the user exits.
I'd imagine this would be simple to do without over complicating things.
Also the number of dialogues could easily be reduced with this strategy.
This increases efficiency because a user could handle all the conformation files at once in their own way even as their still copying normal files.
The list would list all the files that need conformation and let u handle them with check boxes. ( A Select All/None combo button and an Invert Selection button are a must for such a list. Then double clicking a listed directory should select all in the directory.)
Then by for example pressing Overwrite or a Do Nothing button the action would affect all selected files. After which you can continue such steps until the List is gone or the user exits.
I'd imagine this would be simple to do without over complicating things.
Also the number of dialogues could easily be reduced with this strategy.
This increases efficiency because a user could handle all the conformation files at once in their own way even as their still copying normal files.
6
votes
6
0
0
Selected solution (#25):
property comparison table
Just like solution #16 above, but the properties should be listed in a side-by-side table, with cells highlighted in green if they match, red if they don't match, and if they ALL match then there is no reason to bug the user at all.
Just like solution #16 above, but the properties should be listed in a side-by-side table, with cells highlighted in green if they match, red if they don't match, and if they ALL match then there is no reason to bug the user at all.
5
votes
5
0
0
Selected solution (#26):
Add intelligent preview/comparison box to the Nautilus file replacement dialogue
Written by
cajhne the 14 Sep 10 at 21:05.
Disclaimer: I worked this up before finding that my problem was a dupe of this thread, so don't yell at me for "duplicating" some ideas here. I've +1 promoted the ones that I came to the same or similar conclusions about. There's different stuff in here, so please read the whole thing! :)
It would be handy to show other relevant information based on the file type in a small preview/comparison area on the side of the replace notification dialogue. It would also be nice to have an in-dialogue "rename" function, where you could change the name of the file being copied rather than just the standard replace/don't replace option. Leave the defaults the way they are, but offer a drop-down of other solutions, as well as a preview box for the file. Text files could show the first few lines of the file (if permissions allow), the photo can show thumbnails, music can have the same (nifty) mouse-over preview in the file browser, etc.
The "intelligent" bit changes the options for replacement/renaming/etc based on the kind of file, and the kind of preview shown. Some handy alternate options might be "append" for videos/music/text files, which combines/concatenates two files into one, or "version" which simply appends an ordering number to the end of the filename (my_cat.jpg -> mycat_b.jpg)
I have worked up a visual on what I think this might look like if there's enough interest. :)
http://whitecatgraphics.com/ubuntu/nautilus_replace_comparison_dialogue.jpg
This example shows the standard file replace dialogue with my additions. The files under scrutiny are an old and new version of the same image. The desaturated, darker one is meant to represent an unedited photo, and the saturated one an edited version, which highlights the advantage/importance of being able to see samples of each to make the judgement.
Things to note in this sample:
1.The "replace all" option now has a drop-down menu below it, in which you can specify in what manner you want to "replace all".
2.The arrow between the two thumbnails indicates which is source and which is the destination (since some people in the world read from right to left. :))
3.The thumbnails act like thumbnails in the regular browser. Right-clicking on them could bring up options like "preview", "open with", "info", or "show in folder".
4.Selecting "Keep" under either sample will automatically set the other to "Erase", for ease of use. The "Save As..." option could bring up a box for the new file name, or alternatively, a standard "save as" dialogue as seen in GIMP, Open Office, etc, when you choose "Save As".
5.The green check-mark and the red "X" icon indicate which is being kept, and which is not. These change when "Keep" or "Erase" is selected.
6.After selection is complete, the user would then click the "Replace" button to perform the action, and continue the file copy/move operations.
I'm not married to any of the above components. If anyone thinks of a different/better way to do it, please post it in the comments section, and I'll revise this solution based on the suggestions. :)
I'm not proposing changing any of the defaults, just adding a box for more information, and a few more options to streamline the current replacement procedure.
Disclaimer: I worked this up before finding that my problem was a dupe of this thread, so don't yell at me for "duplicating" some ideas here. I've +1 promoted the ones that I came to the same or similar conclusions about. There's different stuff in here, so please read the whole thing! :)
It would be handy to show other relevant information based on the file type in a small preview/comparison area on the side of the replace notification dialogue. It would also be nice to have an in-dialogue "rename" function, where you could change the name of the file being copied rather than just the standard replace/don't replace option. Leave the defaults the way they are, but offer a drop-down of other solutions, as well as a preview box for the file. Text files could show the first few lines of the file (if permissions allow), the photo can show thumbnails, music can have the same (nifty) mouse-over preview in the file browser, etc.
The "intelligent" bit changes the options for replacement/renaming/etc based on the kind of file, and the kind of preview shown. Some handy alternate options might be "append" for videos/music/text files, which combines/concatenates two files into one, or "version" which simply appends an ordering number to the end of the filename (my_cat.jpg -> mycat_b.jpg)
I have worked up a visual on what I think this might look like if there's enough interest. :)
http://whitecatgraphics.com/ubuntu/nautilus_replace_comparison_dialogue.jpg
This example shows the standard file replace dialogue with my additions. The files under scrutiny are an old and new version of the same image. The desaturated, darker one is meant to represent an unedited photo, and the saturated one an edited version, which highlights the advantage/importance of being able to see samples of each to make the judgement.
Things to note in this sample:
1.The "replace all" option now has a drop-down menu below it, in which you can specify in what manner you want to "replace all".
2.The arrow between the two thumbnails indicates which is source and which is the destination (since some people in the world read from right to left. :))
3.The thumbnails act like thumbnails in the regular browser. Right-clicking on them could bring up options like "preview", "open with", "info", or "show in folder".
4.Selecting "Keep" under either sample will automatically set the other to "Erase", for ease of use. The "Save As..." option could bring up a box for the new file name, or alternatively, a standard "save as" dialogue as seen in GIMP, Open Office, etc, when you choose "Save As".
5.The green check-mark and the red "X" icon indicate which is being kept, and which is not. These change when "Keep" or "Erase" is selected.
6.After selection is complete, the user would then click the "Replace" button to perform the action, and continue the file copy/move operations.
I'm not married to any of the above components. If anyone thinks of a different/better way to do it, please post it in the comments section, and I'll revise this solution based on the suggestions. :)
I'm not proposing changing any of the defaults, just adding a box for more information, and a few more options to streamline the current replacement procedure.
6
votes
6
0
0
Selected solution (#27):
Do dry-run before actually copying data
Check the destination and see if any files are present, and if there are problems before actually start copying data.
That way, any problems requiring user interaction can be flagged upfront, once data copying has started it is guaranteed to continue without user interaction.
Check the destination and see if any files are present, and if there are problems before actually start copying data.
That way, any problems requiring user interaction can be flagged upfront, once data copying has started it is guaranteed to continue without user interaction.
5
votes
5
0
0
Selected solution (#28):
Additions to File Operations
Written by
JohnLM the 15 Jan 09 at 21:46.
I thought it could scan for involved devices and queue by (configurable) default, if that device is in use (i.e. having copy or move operation already). And have a "Do now!" kind of button on file operation window for override.
Naturally it should never en-queue same partition's move operations, cause they are super fast by nature!
btw As far as I know the Nautilus' File Operations thingie is not really finished and is under development now!
I thought it could scan for involved devices and queue by (configurable) default, if that device is in use (i.e. having copy or move operation already). And have a "Do now!" kind of button on file operation window for override.
Naturally it should never en-queue same partition's move operations, cause they are super fast by nature!
btw As far as I know the Nautilus' File Operations thingie is not really finished and is under development now!
9
votes
11
1
2
Selected solution (#29):
Conflict dialog: say how many more conflicts there are
Written by
philip the 18 Mar 11 at 20:07.
When you try to copy or move a bunch of files, and files with those names already exist in the destination folder, you get a dialog asking you if you want to replace the existing file or skip copying this file. You can also check a check box for repeating this operation on all other conflicting files.
It would be helpful to know how many more conflicting files there are. This can alert the user that he has done something wrong if he did not expect that many conflicts. It can also guide his decision to check the conflicts manually or click on the "perform this for all files" check box.
Getting more sophisticated, the dialog could even list the conflicting files when the user clicks on a drop down list.
When you try to copy or move a bunch of files, and files with those names already exist in the destination folder, you get a dialog asking you if you want to replace the existing file or skip copying this file. You can also check a check box for repeating this operation on all other conflicting files.
It would be helpful to know how many more conflicting files there are. This can alert the user that he has done something wrong if he did not expect that many conflicts. It can also guide his decision to check the conflicts manually or click on the "perform this for all files" check box.
Getting more sophisticated, the dialog could even list the conflicting files when the user clicks on a drop down list.
12
votes
14
3
2
Selected solution (#30):
Perform file operation / action with gksudo initiation
Perform file operation / action with gksudo-like initiation requiring a pword
Perform file operation / action with gksudo-like initiation requiring a pword
-1
votes
4
1
5
Selected solution (#31):
Require the user to enter a sub menu.
Simply having gksu pop up every time a user tries to do something they aren't allowed to (edit a system file) is a quick way to a non-working system.
I propose we put gksu-enabled commands in a sub-menu (like how new-file lists a few file types). This will prevent users from simply converting to "enter your password until it works" people.
Simply having gksu pop up every time a user tries to do something they aren't allowed to (edit a system file) is a quick way to a non-working system.
I propose we put gksu-enabled commands in a sub-menu (like how new-file lists a few file types). This will prevent users from simply converting to "enter your password until it works" people.
66
votes
67
0
1
Selected solution (#32):
Add a pause button
Written by
dead_orc the 12 Mar 09 at 13:40.
Add a pause/continue button next to the stop button with which you can pause file operations and continue them later on.
Add a pause/continue button next to the stop button with which you can pause file operations and continue them later on.
20
votes
22
2
2
Selected solution (#33):
Control the number of simultaneous op-s on a drive
Written by
andrew.p the 19 Mar 09 at 21:28.
This is not a complete solution, but an addition to #2/#1.
I often miss an option to limit the number of simultaneous file operations on a drive (simultaneous file operations are not as quick as one-by-one sometimes).
Speaking about sol#1, it would be logical to have an option to queue file operation instead of performing immediately (name menu item "Queue Paste" & give it keyboard shortcut like Ctrl+Alt+V/Ctrl+Q/Super+V). Also it is a workaround for controlling the number of simultaneous file operations.
This is not a complete solution, but an addition to #2/#1.
I often miss an option to limit the number of simultaneous file operations on a drive (simultaneous file operations are not as quick as one-by-one sometimes).
Speaking about sol#1, it would be logical to have an option to queue file operation instead of performing immediately (name menu item "Queue Paste" & give it keyboard shortcut like Ctrl+Alt+V/Ctrl+Q/Super+V). Also it is a workaround for controlling the number of simultaneous file operations.
-4
votes
6
1
10
Selected solution (#34):
Use ionice
The 'ionice' command sets the io scheduling class and priority for a program. A user can easily downgrade the io priority of any process. ionice is included in the 'schedutils' package, already in the repositories.
It's powerful and solves a lot of disk-thrashing if used properly. Read the man page before using it!
The 'ionice' command sets the io scheduling class and priority for a program. A user can easily downgrade the io priority of any process. ionice is included in the 'schedutils' package, already in the repositories.
It's powerful and solves a lot of disk-thrashing if used properly. Read the man page before using it!
7
votes
8
3
1
Selected solution (#35):
Click & drag priority management
Being able to set the priority of ops would be really useful, but we also don't want to add too much to the interface.
I think the most user-friendly solution would be to:
1) Run only one op at a time automatically
2) Have a continue / pause button to force start, pause, and resume
3) Have the ops listed by priority (i.e. which was started first; which are running)
4) Be able to click and drag the progress bars up/down to switch the priorities
Being able to set the priority of ops would be really useful, but we also don't want to add too much to the interface.
I think the most user-friendly solution would be to:
1) Run only one op at a time automatically
2) Have a continue / pause button to force start, pause, and resume
3) Have the ops listed by priority (i.e. which was started first; which are running)
4) Be able to click and drag the progress bars up/down to switch the priorities
15
votes
15
1
0
Selected solution (#36):
implement "queue file transfer" function
Written by
nuzeb the 25 Jun 09 at 11:43.
It would be nice to be able to manually start a lot of file transfers with a queue function (e.g. right click menue of nautils "queue copy"). The transfers will then be done one after another in given order.
It would be nice to be able to manually start a lot of file transfers with a queue function (e.g. right click menue of nautils "queue copy"). The transfers will then be done one after another in given order.
Attachments
No attachments.
Duplicates
Comments
Also thunar, XFCE beats Gnome badly.
MaxVK
wrote on the 9 Nov 08 at 10:49
+1
Which window manager is best is not an issue and is personal preference.
Assuming that nautilus is being used this is a good idea - More information is better and allows a more informed decision.
DrHalan
wrote on the 9 Nov 08 at 11:46
+1
also cool would be for text files a comparision similar to svn where you can see the actual changes.
deadowl
wrote on the 13 Nov 08 at 20:53
It would be so much easier if a batch processing methodology were used for file conflicts in the sense that idling over a file transfer or being interrupted by the file conflict is inefficient. But then again, I'm unsure as to whether anyone will ever listen to me about this.
korin43
wrote on the 16 Aug 09 at 09:01
Idea #20326 is not a duplicate of this. Why is it merged in?
Holy ****! 24 solutions - this should not have been merged.
via 10 and 19: What if the file is corrupted? and the md5 is known to be cracked.
via 8: that would be huge and time-consuming. No file managers do this, that I know of, so it's probably not worth the time and effeort to support every format.
komputes
(Brainstorm moderator)
wrote on the 8 Oct 11 at 17:43
Solution #2 and #4 have been implemented. This is what I am seeing in Oneiric:
Replace file "photo.jpg"
Another file with the same name already exists in Pictures.
Replacing it will overwrite its content.
(THUMBNAIL OF IMAGE)
Original file
Size 603.0 kB
Last Modified Thu 22 Apr 2010, 6:10:03 PM EDT
(THUMBNAIL OF IMAGE)
Replace with
Size 603.0 kB
Last Modified Thu 22 Apr 2010, 6:10:03 PM EDT
Options:
> Select a new name for the destination
> Apply this action to all files
komputes
(Brainstorm moderator)
wrote on the 8 Oct 11 at 17:48
Solution #17, although logical and famous, can create a different issue if you are moving files and it gets interrupted, you would not know where the copy ended. Currently it would end alphabetically and you would be able to easily identify the incomplete file.
It should be disconnected from this brainstorm (rationalesolution) and be moved to its own idea: "Copy process pauses/interrupts on file conflict". Ideally we would want all file conflicts would be managed before the copy starts and not during the copy.
"REPLACE ALL IF NEWER" button is not yet implemented. But those options that HAVE been implemented really come in useful!
^ REPLACE ALL IF NEWER for nautilus is not present in ubuntu 12.04.
Post your comment