Moving a folder, ignoring some files inside, but busting them in the end ?!

[deepseekuser]

Hello everyone.

First I would like to thank ghisler to delivering such a gem to the world. Thank you very much, and anyone involved in this project.
It's been a life saver for me for those very precise situations.

Recently I've been using it with adb and again it just changed my life.

But something really strange just happened.

I think I may have purged a folder from my device but I would like to be sure and furthermore understood what happened.
I had very long files with very long names and copying them just made the software crash.
So I decided to filter them out for the moment and only backup the "acceptable length" files on my disk.
Everything went well, and as a matter of wanting to proceed carefully, I did copy them first, backup them in an archive and in a third process MOVE them to the PC in order to free some space on the mobile device. You see the thing coming, I never (or very fewly) used the MOVE command before.

So everything went well until I fell on another folder I did not notice at the first place on my android device. Contrary to the first operations, which were consisting of processing a batch of files inside a directory to another, I simply decided to MOVE DIRECTLY the additional folder to a place on my disk.
I had the message of the file name ecceeding the 239 chars again. I just clicked on skip; the operation went full on, but after the operation finished, THE ORIGINAL FOLDER ON MY ANDROID DEVICE JUST VAPORIZED. So I got a copy of it with the non-bypassed files on my disk but what about the ignored files ?

I brievly navigated through the forum reading "it's a safe feature" but I have low hopes recovering my files. Why did not not keep the folder on the android device with the unprocessed files ?

Cheers