xavierd
Improvements
Following extra functionalities are implemented in separate commits:
- Option to disable preview window.
- When jumping to declaration print whether we go jump to a virtual method to warn user that actually other derived function could be called.
- Possibility and keybinding to print type of identifiers and if identifier is an enum, then it's value as well.
- Remove extra =? in optional argument in newer clang libraries, which supports printing default value.
- Making it possible to disable/change the mappings.
@DroZ-hun, are you actively using the plugin? You have made changes in pretty much every part of the plugin properly documenting them along the way, I'm thinking maybe it makes sense to ask Rip-Rip to give you write access in case you can and are willing to maintain the plugin in some way?
Well, I am actively using the plugin, these are changes, which I have made over the time, but had no time until now to shape them in a way to be able to merge them back (follow conventions, etc.).
So I would gladly accept the push permission, but I do not think I will have the time to regularly maintain the repo, so maybe it is not worth it.
Adding two fixes:
- one is fixing an old bug, which bothered me some times back, but decided, that I will just not use that preview setting,
- the other is again something I have not used but other could have, this later only comes out when default mapping is changed for snippet jumping in clang snippet and completion menu is closed by
or .
I think that few pull requests I do (up till now I have this and had an other 2 and a half years back) does not worth to have write permission, but if you think otherwise, then I can request it form Rip-Rip via email.
Well, if you don't have much time, then it's probably not worth it. The problem with the project is that there seem to be no more people who both have write permissions and still use the plugin. That's why I don't even merge things much as I'm not able to test them adequately, and it's probably better to keep what's already there working than break things by merging untested changes.
Thanks for the changes either way, somebody might find them helpful.
That's too bad, this is a nice plugin. Well I am pretty sure lot's of people chose this plugin when working with c/c++ using vim, so I am hoping someone will have time to maintain it, and will chose to do so.