Monday, November 6, 2017

Handling differences in different plugins for the same type of operation

I'm looking for refactoring support in Vim, specifically for C, Python, and Go. It would probably suffice with renaming functions/variables and extracting function/method. My problem is that of being forced to keep multiple mappings for the same things just depending on which file type i'm working on at the moment.

For Python i know there is a plug in that is built around rope, https://github.com/python-rope/ropevim.

In Go there are both the Go Doctor, http://gorefactor.org/, and vim-go, https://github.com/fatih/vim-go.

For C with relatives (C++, Java, ...) there seem to be vim-refactor, https://github.com/LucHermitte/vim-refactor.

Even if these work they are no where close to a uniform interface. How do you guys handle such issues, stick with the differences, remap until insane, or something else?

I think it would be great if i could have a uniform interface to use for refactoring regardless of which language i happen to use at the moment. Remembering three different mappings for refactoring and when each one applies steal my focus from what i would like to do.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: