Thursday, January 31, 2013

Re: Syntax highlight not happening on :newtab

On 2013-01-31, naaj_ila wrote:
> Hi Gary ,
> Followed the steps which you had given,
> but its not working
> Even opening the single file is not having the syntax enabled .

I just tried the following experiments. I first created a ~/file1.v
from your example, then copied the default verilog.vim to my ~/.vim
hierarchy:

cp /usr/local/share/vim/vim73/syntax/verilog.vim ~/.vim/syntax

1.
vim -N -u NONE --cmd 'syntax on' file1.v

The file was syntax highlighted.

:scriptnames
1: /usr/local/share/vim/vim73/syntax/syntax.vim
2: /usr/local/share/vim/vim73/syntax/synload.vim
3: /usr/local/share/vim/vim73/syntax/syncolor.vim
4: /usr/local/share/vim/vim73/filetype.vim
5: ~/.vim/syntax/verilog.vim
6: /usr/local/share/vim/vim73/syntax/verilog.vim

2.
Created a file2.v identical to file1.v with Hello changed to
Goodbye.

Moved my ~/.vimrc asided and created a new one containing only

syntax on

Executed

vim file1.v
:split file2.v

Both buffers are highlighted.

Something in your configuration is keeping file1.v from being
properly syntax highlighted. It works for me with my normal
configuration and with a minimal configuration with just "syntax
on". We just need to find out what in your configuration is keeping
this from working for you.

One approach is for you to start with a minimal configuration, get
highlighting to work, then add pieces of your normal configuration
until highlighting stops.

Why are you using your own verilog.vim instead of the default
$VIMRUNTIME/syntax/verilog.vim?

Regards,
Gary

--
--
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/groups/opt_out.

No comments: