[cfe-dev] Slightly improved clang-format vim integration

Daniel Jasper djasper at google.com
Mon Sep 16 11:12:06 PDT 2013


I think this generally seems like a good idea. However, I'd like to also
keep the old version at least for a while for compatibility and because I
think it is slightly easier to install until it can be used by Vundle etc.

That should however not keep us from also committing this. Either to some
Github repository so it can be used by Vundle or to a separate directory
inside cfe, e.g. tools/clang-format/vim. The current state where several
editor integrations are just files in tools/clang-format is a mess anyway ..


On Mon, Sep 16, 2013 at 7:14 PM, Steffen Prohaska <prohaska at zib.de> wrote:

>
> On Sep 16, 2013, at 6:04 PM, Tobias Grosser <tobias at grosser.es> wrote:
>
> > Steffen, I believe the idea of your patch is great. Unfortunately it has
> from my point two issues:
> >
> > 1) You rely on features of very recent vim versions
>
> I've addressed this in in the revised script that I've just sent in a
> separate mail.
>
>
> > As this is not a complicated plugin, there seems no reason to drop
> support for older vim versions.
> >
> > 2) You require python in the .vimrc file
> >
> > I would prefer to not require python in the .vimrc, but have the plugin
> report an error when it is called without python support.
>
> Python has also been required by the previous version of the script.  So
> my proposed changes don't make the situation worse.
>
> I agree that a full plugin would be ideal.  I think that it would ideally
> be hosted in a separate git repo on Github, so that Pathogen or Vundle can
> be used to install it.  However, I don't plan to create such a plugin
> anytime soon.
>
>         Steffen
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130916/ea87a3a1/attachment.html>


More information about the cfe-dev mailing list