for me its often the case that i unpack e.g. a ZIP archiv with a context menu option. In the context menu i have "Unpack here" and "Unpack to <name_of_the_Archiv_subfolder>.
And following Murphys law i ever choose the wrong one.
But then i often end up with the zip content in a double subfolder because the zip archiv already contains a subfolder in its structure. E.g. i unpack test.zip with the "Extract to test subfolder" shell context menu option and the zip archiv already contains a test folder where the real files sit in, i end up with the files in .\test\test\<here are the files>.
Then my regular task is to mark all the files and move them to parent folder. OK, new WinRAR version now solves this problem in most cases with an option to remove double folders at the end of the path, but this is not the only case when such a "Move/Copy to parent" would come handy. Sometimes i just want to move some files out of the way to perform some batch renaming, whatever. Then i move them to parent, do the actions i need, and move them back again (Moving down is easy when you go up to parent and you see the childfolder in the list).
I now have to drag/drop the files into the tree. But that needs me to first spot out the right folder in the tree where to drop. If you have many similar named folders, then its sometimes difficult to tell which one is the correct one.
So i wonder if you and some others maybe agree, that expanding the already existing context menu items "Move/Copy ..." "here as copy", "here to new subfolder", etc. could be extended by another item "Copy/Move to parent"?
Any comments? Good? Bad? Will i got burned by the community now as a heretic for this idea?
Greetings to all
JoTo
XYplorer Beta Club