On Sat, Apr 17, 2004 at 11:06:52AM -0700, Kees Cook wrote:
On Sat, Apr 17, 2004 at 01:35:07PM -0400, MenTaLguY wrote:
Perhaps you need to install the C++ vim mode? It works fine with my vim installation.
Hm... digging into vim, it looks like mine is named "cpp". And none of the vim docs even hint at calling this "c++". How is yours installed?
For me (default Debian install of vim 6.2, including patches 1-149), c++ and cpp each work. I've no big objection to a global change to filetype=cpp (except that it isn't as clear as c++, e.g. could mean C preprocessor or something else I haven't thought of). Kees, do you have a reasonably recent vim installation?
I would object to removing the filetype=blah specification for .h files (vim would wrongly guess C, which behaves differently for e.g. private/public/protected), and I would object to having different settings for .h and .cpp files. However, I don't usually use vim for C/C++ development.
I've just discovered today that the c-file-offsets line should also have `(case-label . +)' in the alist to conform to the examples in the CodingStyle page (case statements indented by one quantum from the switch statement). This change and the filetype change (if any) can be done as one commit.
pjrm.