Re: Rename files with $EDITOR

[hossman]

in reply to Rename files with $EDITOR

The idea behind this script both terrifies, and excites me.

The script itself however frightens me, because there are some edge cases that can have some relaly nasty behavior...

• There's a risk of some silent catastrophic user error if a person inadvertently attempts to rename two different files to the same file (ie: "a->x and b->x" ... or if they mean to do "a->b and b->a" but they forget to change one and wind up with a->b and b->b). It would be pretty easy to prevent this type of error by doing an "exists" around line #60
• There's a really bad assumption in your "handle overwriting name changes" ... it will work for a->b and b->a but not any other generalized overlaps like "a->b and b->c". This is because the loop over the keys only checks for the existence of the "target" file as a key in the hash and if it exists it creates a temp file -- but it never looks at the value that "target" had in the hash when moving the tmpfile, it just assumes you wanted a straight swap.
• Even if you fix the previous bug by using mv($tmpfile, $files{$files{$fname}}); instead of mv($tmpfile, $fname); I still think it's possible you're going to wind up edge cases where things fail depending on what files get processed in -- in particular consider the case of "a->b and b->c and c->a"

I think the only safe way to deal with all of this is that if you detect your $target is already a key in the hash, you need to mv($target,$tmpfile) and then update the hash, ala: $files{$tmpfile} = $files{$target}; delete $files{$target};. It complicates things because you can't do a simple loop over a one time copy of the keys, but that's not a big deal. Just do a "while (keys %files) { $fname = (keys %files)[0]; ...; delete $files{$fname}; }" type flow instead.

[tye]

Yeah, I was going to point out some of those same problems.

I wrote the same basic tool about 20 years ago. Since then it has been one of my most heavily-used tools.

It was usually the first tool I missed when I moved to a new environment. And I've been surprised over the years to not run into this functionality by other authors.

I remember missing my precious mvi and thinking, "Oh, vim lets you edit directories, I'll just use that". Gah, what an awkward interface. I can't even do :%s/HTM/html/. I can't use all of the vi features to get all of the file names just right.

So it was nice to finally see this simple idea cross my path. (Surely others have written such a tool, just not that I've run into.)

Over the years my mvi has grown. It is now over 500 lines, actually. It handles all of the cases you outlined. It also lets you copy, link, or delete files. Deleting files leads to the case of "delete b; mv a b" which would be ugly if you did those steps in the wrong order. It deals with very badly named files. It lets you pick whether you want to overwrite files and/or be asked first (it was always important that it be a safe way to rename files -- in fact, I'd often reach for it to do a very simple rename because I knew it wouldn't overwrite even when I didn't have a local equivalent for "mv -n" or wasn't sure what the local equivalent of "mv -i" was).

I'll post the code for it in a bit.

bumby++

Update: Posted at mvi -- mv+vi (+ln+rm+cp+mkdir).

[bumby]

Thanks for the feedback and mvi, very useful tool!