<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#0050d0">
Sent: Tue Nov 15 2011 02:47:59 GMT-0700 (MST)<br>
From: Raoul Bhatia [IPAX] <a class="moz-txt-link-rfc2396E" href="mailto:r.bhatia@ipax.at"><r.bhatia@ipax.at></a><br>
To: The Pacemaker cluster resource manager
<a class="moz-txt-link-rfc2396E" href="mailto:pacemaker@oss.clusterlabs.org"><pacemaker@oss.clusterlabs.org></a> <br>
Subject: Re: [Pacemaker] Syntax highlighting in vim for crm
configure edit
<blockquote cite="mid:4EC2354F.9040406@ipax.at" type="cite">hi!
<br>
<br>
On 2011-08-19 16:28, Dan Frincu wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
On Thu, Aug 18, 2011 at 5:53 PM,
Digimer<a class="moz-txt-link-rfc2396E" href="mailto:linux@alteeve.com"><linux@alteeve.com></a> wrote:
<br>
<blockquote type="cite">On 08/18/2011 10:39 AM, Trevor Hemsley
wrote:
<br>
<blockquote type="cite">Hi all
<br>
<br>
I have attached a first stab at a vim syntax highlighting
file for 'crm
<br>
configure edit'
<br>
<br>
To activate this, I have added 'filetype plugin on' to my
/root/.vimrc
<br>
then created /root/.vim/{ftdetect,ftplugin}/pcmk.vim
<br>
<br>
In /root/.vim/ftdetect/pcmk.vim I have the following content
<br>
<br>
au BufNewFile,BufRead /tmp/tmp* set filetype=pcmk
<br>
<br>
but there may be a better way to make this happen.
/root/.vim/pcmk.vim
<br>
is the attached file.
<br>
<br>
Comments (not too nasty please!) welcome.
<br>
</blockquote>
</blockquote>
<br>
I've added a couple of extra keywords to the file, to cover a
couple
<br>
more use cases. Other than that, great job.
<br>
</blockquote>
<br>
will this addition make it into some package(s)?
<br>
would it be right to ship this vim syntax file with crm?
<br>
<br>
thanks,
<br>
raoul
<br>
</blockquote>
<br>
Gave this syntax file a shot and I dont think it should be included
in the standard package. Its very colorful, but it breaks too many
standard highlighting conventions.<br>
<ul>
<li>The 'node' keyword doesnt gets highligted with a different
color than 'primitive', 'property', etc</li>
<li>The names of primitives, clones, etc should be highlighed with
"Identifier" not "Type"</li>
<li>The primitive type (ocf:hearbeat:whatever) should be "Normal"</li>
<li>Chars like '=' '\' ':' should not be assigned a color
("Normal" or left alone)</li>
<li>Colors of weights are assigned different colors when used in
location rules and colocation/order rules. These should get the
same color policy, and should also be something other than
"String".</li>
</ul>
The color output you get from 'configure show' should be what vim
looks like, or very close to it.<br>
</body>
</html>