Hi,
I am facing this syntax highlighting problem here for the following code
segment. The problem is if we put this code in a file having .c
extension. The same macro color is shown for the main() function also.
Does anyone else faced this problem with vim7 ?
regards,
s
===somefile.c
On 8/3/06, Srinivas Rao. M [EMAIL PROTECTED] wrote:
I am facing this syntax highlighting problem here for the following code
segment. The problem is if we put this code in a file having .c
extension. The same macro color is shown for the main() function also.
Does anyone else faced this problem
On Thu, 2006-08-03 at 14:09, Yakov Lerner wrote:
On 8/3/06, Srinivas Rao. M [EMAIL PROTECTED] wrote:
I am facing this syntax highlighting problem here for the following code
segment. The problem is if we put this code in a file having .c
extension. The same macro color is shown for the main
Srinivas Rao. M wrote:
I am facing this syntax highlighting problem here for the following code
segment. The problem is if we put this code in a file having .c
extension. The same macro color is shown for the main() function also.
Does anyone else faced this problem with vim7 ?
regards,
s
Jerin Joy wrote:
I use gvim as my default editor. My source files are in a non standard
language whose syntax is similar to Verilog. When I open files from
command line in independent gvim windows the syntax highlighting uses
the verilog syntax which is what I want. The only thing is when I
On Wed, May 10, 2006 at 04:06:38PM +0530, Jerin Joy wrote:
Hi,
I use gvim as my default editor. My source files are in a non standard
language whose syntax is similar to Verilog. When I open files from
command line in independent gvim windows the syntax highlighting uses
the verilog syntax
Hi,
I use gvim as my default editor. My source files are in a non standard
language whose syntax is similar to Verilog. When I open files from
command line in independent gvim windows the syntax highlighting uses
the verilog syntax which is what I want. The only thing is when I use
the split
