![]() But so far, even trying to enable all libclang flags to get these brief comments, I was unable to make them show up here in my machine. Since I'll keep using it I'll make fixes if I find dirty corners.Īlso the preview windows instead of just showing overloads, since now they "all" show up in the popup, it's also supposed to show brief comments with the accompanying prototype. Right now it's just a patch over the original YCM's ClangCompleter, if I turn it into something more modular I'll try a pull-request but for now it serves as a preview. It's just the same simple but fast parameter completion approach. The behavior can be viewed in this video: ![]() This is the clang_complete/supertab config for that:įor anyone interested in a behavior just like clang_complete's parameter completion using g:clang_snippets_engine='clang_complete' I started a preliminary work under oblitum/YouCompleteMe/tree/clang_complete-params. I'm willing to switch to YCM, but still, without this, I feel it doesn't obsoletes clang_complete. I guess this behavior turns the extra preview window popup completely unnecessary, and hence, discarding it provides yet one more feature: less interface cluttering. ![]() This video (at time 2m30s) illustrates how this parameter completion works.Īnd this is a GIF from a fork that patches YCM to provide this: there's an option to hide the characters used to surround the parameters using VIM's conceal feature, so may not even clutter the view. this way, you never lose completion context for nested completions. Then, you can just start typing to automatically enter insert mode, overwriting the selected one. bar + selection *inserts* bar's call into code with traversable parameters: // bar(, ) // foo + selection *inserts* foo's call into code with traversable parameters: // bar(foo(,, ), ) // to cycle between parameters you just go to normal mode and press tab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |