It turns out I forgot the command to go back in Yazi and accidentally pressed one that unleashed this beast.
# { on = "<C-p>", run = "shell --confirm 'if [ -n \"$fx\" ]; then for dir in $fx; do cd \"$dir\" && find . -mindepth 2 -type f -exec mv -n -t . {} + && find . -type d -empty -delete && cd - >/dev/null; done; else find . -mindepth 2 -type f -exec mv -n -t . {} + && find . -type d -empty -delete; fi'", desc = "Aplanar carpetas hijas" }
Yisus...
59403 Files to restore :D
it's a real chaos because i was in a folder with many code projects maybe around 30 or more and each one with his node_modules folder....
so... it's really a chaos.
this command was an complete error without warnings and modal prevents...
so it's super usefull only when you really know wtf are you doing
How do I plan to address this problem?
I plan to group all files by type into folders.
I'll try to clean up everything I detect that belongs to node_modules, and then reinstall it.
(I hope I haven't flattened the .git folders, but i think yes)
I'm going to rely almost entirely on my memory to know what should go where...
And I'm going to have to completely redefine many of my directories.
Because there were folders within folders within folders...., all with a semantically correct structure according to my workflow...
They weren't just code projects.
- Images
- Videos
- Writings
- Markdown notes.
- code structures (with his imports) long etc....
its a mess
I'm literally flattening everything D:
Imagine suddenly having no folders on your system and having ABSOLUTELY ALL your files in one folder.
xD It reminds me of your aunt's or grandma's downloads folder.
Like that, but worse... I mean, omg, I want to cry.

Top comments (0)