You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
This feature would allow the ability to queue certain operations on a stack, and then execute them consecutively. This would be implement undo for file operations. This would also add security for larger operations. My idea for this is similar to SQL transactions.
I see this mainly useful for moving/interacting with a large amount of files. Sometimes I accidentally move to the wrong folder, or I copy the wrong file from different harddrives.
Will you be willing to contribute this feature?
Yes, I'll give it a shot
Describe the solution you'd like
Allow the user to start a transaction with a keybinding, and then all operations from then on will be queued. At any time the user can bail out, or undo an operation. Once they are done, they can commit their changes and then all the actions will be taken.
On commit, the integrity and validity of the operations can be checked, to make sure nothing unexpected happens.
Describe alternatives you've considered
This would probably be the easiest way to implement undoing. I don't know how feasible this is to implement with the current task system, and would require some way to interact with plugins. I'd definitely being willing to write a PR if I could get some direction on how this should be implemented and if this would be a welcome feature.
Is your feature request related to a problem? Please describe
This feature would allow the ability to queue certain operations on a stack, and then execute them consecutively. This would be implement undo for file operations. This would also add security for larger operations. My idea for this is similar to SQL transactions.
I see this mainly useful for moving/interacting with a large amount of files. Sometimes I accidentally move to the wrong folder, or I copy the wrong file from different harddrives.
Will you be willing to contribute this feature?
Describe the solution you'd like
Allow the user to start a transaction with a keybinding, and then all operations from then on will be queued. At any time the user can bail out, or undo an operation. Once they are done, they can commit their changes and then all the actions will be taken.
On commit, the integrity and validity of the operations can be checked, to make sure nothing unexpected happens.
Describe alternatives you've considered
This would probably be the easiest way to implement undoing. I don't know how feasible this is to implement with the current task system, and would require some way to interact with plugins. I'd definitely being willing to write a PR if I could get some direction on how this should be implemented and if this would be a welcome feature.
Additional context
#404
The text was updated successfully, but these errors were encountered: