[feature request] Confirmation of succesful copy/move operation

[pariahdog]

I would like to see an option to leave the last operation or last few operations visible in the task manager window after they have been completed so that you can see the copy went to 100% without problems and without having to confirm a popup box. Although a popup which confirms that the copy was successful could be another way of accomplishing the same thing. I think the task manager window allowing persistence is a more elegant solution though. In addition it would be nice if the option to automatically confirm the copy using CRC or MD5 was available. For an existing example of this functionality see http://codesector.com/teracopy (a windows app).

[IgnorantGuru]

I don't see the value of allowing finished commands to persist in the list. If a command is removed without popup it completed successfully; otherwise a popup always appears with the error. Closing this request because there are no plans to change this behavior, but feel free to add further comments on this below.

No plans to implement the hash confirmation - this was already considered and rejected when the task manager queue was added. You could make a plugin which adds this functionality. Note that as of 0.8.7 (current next branch) custom commands can start internal copy tasks.

[IgnorantGuru]

Also note View|Tasks|Popups|Popup All Tasks if you always want a popup.

[pariahdog]

You say that hash confirmation was considered and rejected. Does this mean just by you or was there some kind of public discussion about it that you could point me to. I'd be interested in knowing what the reasoning was behind that decision. Not because I want to try to change your mind. Just because I am curious. I want to ask you some questions about implementing a hash check plugin, but I guess it would be better to do that in the forum since it seems off topic here. It's neither a feature request nor a bug.

[IgnorantGuru]

You say that hash confirmation was considered and rejected. Does this mean just by you or was there some kind of public discussion about it that you could point me to. I'd be interested in knowing what the reasoning was behind that decision.

I don't recall any public discussion of it. Some of Teracopy's and other FM features were discussed privately and reviewed for how they would work for SpaceFM, particularly when the queue features were added.

The hash feature was rejected as a candidate feature for a number of reasons. SpaceFM is intended to have a simple interface. While small features like hashing may seem like good ideas, if you put them all together they create a dizzyingly complex interface, so the line has to be drawn somewhere. SpaceFM is not a Teracopy clone and aims for a simpler interface. Also, dev time for such a feature must be justified as it compares to other pending work to be done in SpaceFM - how valuable is the functionality, how often used, how many users will use it, etc.

Most specialized features like this in SpaceFM are left as plugin material, as writing such functions in bash is far less time intensive than developing and supporting it in C code, the default interface is kept simpler, and it avoids bloat. Plugins can now do much of what built-in commands can do.

For this, you might consider a 'Copy & Compare' plugin which first copies selected files, then verifies them. My Burn Tools plugin includes a feature to compare disc contents to directory contents, so you could use some of that code as reference. Also note scripts such as animecheck which create hashes.

I see you added a question on the forum, which is a better place to discuss it.