Vim syntax plugin loading issue

[Sam Burk]

I am trying to use a plugin called vim-coldfusion 
(https://github.com/ernstvanderlinden/vim-coldfusion 
), which provides an 
alternative syntax file to the vim default.

I am using Vim 8’s builtin packages to load it.

Whenever I load it via Vim’s package system, it is read after the default cf 
syntax file (I got this information by looking at :scriptnames), but if I copy 
the syntax file to ~/.vim/syntax, it is read before the default syntax file. 
The plugin aborts if b:current_syntax is set, and it is set by the default cf 
syntax file. Thus, the plugin syntax file is never applied.

How can I resolve this? Are syntax files under pack/ always read after the 
default syntax files?

Ideally, I’d like to keep this plugin in pack/*/opt/ and load it only for cf 
files.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim syntax plugin loading issue

[Bram Moolenaar]

Sam Burk wrote:

> I am trying to use a plugin called vim-coldfusion 
> (https://github.com/ernstvanderlinden/vim-coldfusion 
> ), which provides an 
> alternative syntax file to the vim default.
> 
> I am using Vim 8’s builtin packages to load it.
> 
> Whenever I load it via Vim’s package system, it is read after the default cf 
> syntax file (I got this information by looking at :scriptnames), but if I 
> copy the syntax file to ~/.vim/syntax, it is read before the default syntax 
> file. The plugin aborts if b:current_syntax is set, and it is set by the 
> default cf syntax file. Thus, the plugin syntax file is never applied.
> 
> How can I resolve this? Are syntax files under pack/ always read after the 
> default syntax files?
> 
> Ideally, I’d like to keep this plugin in pack/*/opt/ and load it only for cf 
> files.

The 'runtimepath' is updated with the directory of the package.  It is
added after the directory that matches, otherwise at the end.

Is your package also under ~/.vim/syntax ?  If not, then put it there.

-- 
Ten bugs in the hand is better than one as yet undetected.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim syntax plugin loading issue

[Ben Fritz]

On Wednesday, April 25, 2018 at 1:51:09 PM UTC-5, Bram Moolenaar wrote:
> Sam Burk wrote:
> 
> > I am trying to use a plugin called vim-coldfusion 
> > (https://github.com/ernstvanderlinden/vim-coldfusion 
> > ), which provides an 
> > alternative syntax file to the vim default.
> > 
> > I am using Vim 8’s builtin packages to load it.
> > 
> > Whenever I load it via Vim’s package system, it is read after the default 
> > cf syntax file (I got this information by looking at :scriptnames), but if 
> > I copy the syntax file to ~/.vim/syntax, it is read before the default 
> > syntax file. The plugin aborts if b:current_syntax is set, and it is set by 
> > the default cf syntax file. Thus, the plugin syntax file is never applied.
> > 
> > How can I resolve this? Are syntax files under pack/ always read after the 
> > default syntax files?
> > 
> > Ideally, I’d like to keep this plugin in pack/*/opt/ and load it only for 
> > cf files.
> 
> The 'runtimepath' is updated with the directory of the package.  It is
> added after the directory that matches, otherwise at the end.
> 
> Is your package also under ~/.vim/syntax ?  If not, then put it there.
> 

Huh? Why would we put packages in ~/.vim/syntax? The whole point of packages is 
to avoid scattering and intermingling plugin files all over the ~/.vim tree.

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim syntax plugin loading issue

[Bram Moolenaar]

Ben Fritz wrote:

> On Wednesday, April 25, 2018 at 1:51:09 PM UTC-5, Bram Moolenaar wrote:
> > Sam Burk wrote:
> > 
> > > I am trying to use a plugin called vim-coldfusion 
> > > (https://github.com/ernstvanderlinden/vim-coldfusion 
> > > ), which provides an 
> > > alternative syntax file to the vim default.
> > > 
> > > I am using Vim 8’s builtin packages to load it.
> > > 
> > > Whenever I load it via Vim’s package system, it is read after the default 
> > > cf syntax file (I got this information by looking at :scriptnames), but 
> > > if I copy the syntax file to ~/.vim/syntax, it is read before the default 
> > > syntax file. The plugin aborts if b:current_syntax is set, and it is set 
> > > by the default cf syntax file. Thus, the plugin syntax file is never 
> > > applied.
> > > 
> > > How can I resolve this? Are syntax files under pack/ always read after 
> > > the default syntax files?
> > > 
> > > Ideally, I’d like to keep this plugin in pack/*/opt/ and load it only for 
> > > cf files.
> > 
> > The 'runtimepath' is updated with the directory of the package.  It is
> > added after the directory that matches, otherwise at the end.
> > 
> > Is your package also under ~/.vim/syntax ?  If not, then put it there.
> > 
> 
> Huh? Why would we put packages in ~/.vim/syntax? The whole point of
> packages is to avoid scattering and intermingling plugin files all
> over the ~/.vim tree.

Sorry, I meant ~/vim/pack.  Definitely not $VIMRUNTIME/pack
 

-- 
Facepalm statement #1: "I'm going to New York tomorrow, hopefully I have time
to visit the White House"

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.