avoid confusion with thameera/vimv

[jrpie]

After very bad experiences with thameera/vimv (the idea is great, the implementation is not) I am reluctant to run a program called vimv on my computer, especially since one only notices the difference between the two programs after the renaming (and destruction in the case of thameera/vimv) is done. Also note that it is very easy to confuse the AUR packages vimv and vimv-git.

I'd suggest renaming this project to vimvim for vimv improved ^^

Another (perhaps more practical) idea would be to add a first line to the file shown in vim indicating what program is being used and just ignoring the line for renaming.

[NicoWeio]

Actually, we could take inspiration from the comment lines that git commit inserts into the editor by default. Something like

# Please edit the filenames to your liking.
# Swapping files is supported.
# Saving an empty file or removing a line will abort the operation.
# blah blah

myfile.txt
myotherfile.txt

The only immediate drawbacks I see are verbosity (→ keep it short / at the end?) and reserving a special character (probably #) for comments.

[NicoWeio]

As a side note, checking for the “kind” of vimv should be as easy as

head $(which vimv)

and seeing whether it starts with ELF or #!/usr/bin/env bash

[jrpie]

Actually, we could take inspiration from the comment lines that git commit inserts into the editor by default. Something like ...

Yes, that is what I had in mind. # already seems to be used for deleting files though.

[jrpie]

As a side note, checking for the “kind” of vimv should be as easy as

head $(which vimv)
and seeing whether it starts with ELF or #!/usr/bin/env bash

The point is that one can easily forget to check this when working on another machine

Also dmulholl/vimv has a -v flag and thameera/vimv has not

[danjl1100]

# already seems to be used for deleting files

It seems like using # for a header should be OK in most cases?

As long as users don't add or remove comments, the lines below the header will still be one-to-one.

Maybe it could refuse to execute the renames if you changed the header? Something to train users that "this isn't like GIT, the lines below are still one-to-one matched to file names, and # deletes them"