On 2012-12-20, analogsix wrote:
> My .gvimrc resource file only contains a few custom modifications like:
> set ...
> set guifont=...
> highlight Normal guibg=black
> colorscheme slate
> noremap ...
>
>
> I believe I have the default automatic filetype and syntax
> coloring VIM configuration settings, since there are no
> syntax-relevant commands in my .gvimrc resource file.
>
> Scenario1 When Observing the Problem:
> say I run gvim file1.sv on the command-line
> Then, within gVIM, I run :edit file2.sv
> In both cases, syntax coloring is fine.
> -
> Now, I switch back to file1 by running :edit # (i.e. load alternate buffer)
> Now, I loose all my syntax coloring for file1.sv.
> Just for kicks, I switch back to file2.sv by running :edit #file2.sv
> Now I loose syntax coloring for file2.sv
>
> Interestingly, let's say I load my .gvimrc file in gVim via the
> command-line and then load file1.sv (i.e. :edit file1.sv) and then
> switch back to my .gvimrc (i.e. :edit #). In this scenario, I do
> not loose the syntax coloring for the active .gvimrc file.
> However, when I switch back to file1.sv, voila... syntax coloring
> is gone!
I don't see any filetype detection rules for *.sv in
$VIMRUNTIME/filetype.vim in my Vim 7.3.646 installation. Perhaps
you're using some custom filetype detection rules that are
incomplete.
When you first load file1.sv and syntax highlighting is working as
you expect it to, what is the result of this command?
:verbose set ft?
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
