Monday, February 17, 2014

Re: syntax settings with php module files - 'after' problem

On Sunday, February 16, 2014 3:12:43 PM UTC-6, Tim Johnson wrote:
> I'm using ver 7.3 on Mac OSX 10.7
>
> I have the following as a group in .vimrc inside of a
>
> if has("autocmd")
>
> block in
>
> augroup module
>
> autocmd BufRead,BufNewFile *.module set filetype=php
>
> autocmd BufRead,BufNewFile *.install set filetype=php
>
> autocmd BufRead,BufNewFile *.test set filetype=php
>
> autocmd BufRead,BufNewFile *.inc set filetype=php
>
> autocmd BufRead,BufNewFile *.profile set filetype=php
>
> autocmd BufRead,BufNewFile *.view set filetype=php
>
> augroup END
>
>
>
> And I have the following in ~/.vim/after/syntax/php.vim
>
> setlocal iskeyword=@,48-57,_,192-255
>
> setlocal expandtab
>
> setlocal shiftwidth=2
>
> setlocal tabstop=2
>
> setlocal softtabstop=2
>
>
>
> I have noted
>
> 1)That the setlocal options above are correct in a buffer with a
>
> .php extension
>
> 2)That the filetype is shown to be 'php' in a buffer with a .module
>
> or .install extension.
>
> **But**
>
> the setlocal options from ~/.vim/after/syntax/php.vim are being
>
> ignored in buffers with .module and .install extensions
>

I just tried this exact setup, and it works fine for me in 7.4.

I edited a new "test.install" file and all the settings in the after/syntax file were applied properly, just as they were in a new Vim instance editing "test.php".

So, what does this tell you?

:verbose set iskeyword? expandtab? shiftwidth? tabstop? softtabstop?

For me each option points to the after/syntax file.

--
--
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:

Post a Comment