How do you deal with ALEFileRename and git?

[gcb]

after :ALEFileRename the files already get moved, but also get text in them modified. What's your way to deal with this?

manually move back and then git move?

Whatever I do always feels messy.

[rymdbar]

As long as the changes are small enough for git mv <old-file> <new-file> to work, git rm -f <old-file> + git add <new-file> should work too. So there should be no need to do that extra dance step.

To be honest, I had never previously heard of :ALEFileRename, which I see only works for tsserver.

A theoretical ALE improvement would be to make it possible to get the operation status and the new name back somehow, but it's not fully trivial and the command can't be made to return them since communication with the tsserver is asynchronous. If you see a way to do that, please suggest a patch. It would make sense to be able for users to have custom commands calling both ALEFileRename and say Gmove from fugitive.

[gcb]

I've thought about it for a while... there's only two options for a patch on this, neither i think won't cause polemic.

1. check if it is a git repo and files are in the repo, and issue the git mv instead of mv (equivalent). or,
2. don't rename files, ever, and output the renames to be done in a new buffer.