5 ms·
I rarely refactor across entire projects, but I'm fairly certain vim has plugins that can do that. As for finding what calling methods there are, as other have
by qdog 14y ago
I rarely refactor across entire projects, but I'm fairly certain vim has plugins that can do that.
As for finding what calling methods there are, as other have stated, you can use ctags, or go full throttle with Cscope - http://cscope.sourceforge.net/ http://cscope.sourceforge.net/ it will do textual searches along with displaying all callers for a method across all the files you tell it to search (in setup).
With the vim gui and a cscope backend, I'm pretty sure vim is just as much an IDE as any of the other editors. It just happens to work fine in a terminal, too.
- roel_v 14y ago"With the vim gui and a cscope backend, I'm pretty sure vim is just as much an IDE as any of the other editors." <guy never having run more than a mile> 'Yeah I'm pretty sure that these 7.95$ Walmart sneakers are just fine for running the NY marathon, why would I need those Nike's or Asics?'
- qdog 14y agoYou're assuming I don't ever use one of the other IDE's. I've used Eclipse on occasion (currently using it somewhat on Android development as a debugger) and I have to open up Visual Studio at work on occasion. Neither is better for me than vim and unix tools, even if I have to run under cygwin. It's cool that jetbrains is making something new, I just wanted to point out there are few (if any)features vim and/or emacs do not have.
- duaneb 14y agoI'm pretty sure c++ refactoring is impossible (or near to it) because of the ## concat preprocessor directive.
- mserdarsanli 14y agoNot handling ## directive would not be a big loss
- duaneb 14y agoYes it does, because it would refactor partially or brokenly, which is worse in my mind than not refactoring at all.