Hello,
Is there a more in-depth list of planned features available somewhere?
I still haven't found a C-plugin that really fits me. The current ones
always seem too heavy and sluggish or just don't work in every case so I
ended up using basic ctags, ctrl-p and cscope (outside of vim). Not to
mention it's not always possible for me to install clang, depending on
the working place.
When working on a large code base the existing code completion schemes
end up being usually pretty slow... even vim's basic ctrl+p/o can get a
bit overburdened.
It'd be nice if you could define your own set of static rule checks so
that the editor would highlight where those are amiss instead of having
to run a third party checker... maybe not a full fledged analyzer as
that seems quite taxing, but some basic parsing might be nice.
I'd like to follow your progress if possible!
-- Sycc
On 07/18/2016 02:23 AM, Munawar Hafiz wrote:
> Our startup is developing power tools for C developers that will be available as a Vim plugin.
>
> We plan to provide support for common refactorings (Rename, Extract Function, Extract Local, Change Message Signature, etc.,), automatic and smart code completion that is context-sensitive, quick fixes, etc.
>
> We have created an infrastructure to support many syntax-aware and semantics-aware features.
> We want to know from the C developers (and hopefully future consumers of our plugin) about features that you would love to have. This will help us make a better tool for the Vim+C developer community.
>
> Thanks in advance for your help.
>
> Munawar Hafiz
>
--
--
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.
Monday, July 18, 2016
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment