After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 629581 - file-operations fire-n-forget
file-operations fire-n-forget
Status: RESOLVED DUPLICATE of bug 339420
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.28.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-13 21:52 UTC by Victor Vargas
Modified: 2011-10-09 19:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Victor Vargas 2010-09-13 21:52:36 UTC
This requirement was originally filled at:
https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/528403


Hi,

got an idea for nautilus (and any other file explorer basically)

first, i'll say that i really like the single window for multiple file operations.

but, it still displays popups during copying for errors/warnings/user-descisions-needed.
copy is stalled then.

instead, could you please:
- keep copying files that dont require userinteraction.
- list all errs / warnings / etc in a (user-visible) interactive log. have a setting in config for auto-show-or-not of log.
- during, or at the end of copying, check the log, and resolve the errs/warnings/etc. pref not by a gauntlet of dialogs, but by showing the log, some colors, and a right-side panel to select the action (which starts immediately, counter/progressbar in colored log entry plz)

I believe this would be a great improvement for nautilus; end-users, if you agree, comment "+1" plz.

On a side-note; it would also be cool if nautilus took into acount the various filesystems being copied from and to.
One set of write-operations per file-system please, that would result in faster copying i think.
Comment 1 Cosimo Cecchi 2011-10-09 19:49:20 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 339420 ***