Wednesday, June 19, 2013

Re: Where to put "set iskeyword+=_" or remove "iskeyword-=_

Tim, JR, coot,

Here is the output from ":verbose set isk?"

iskeyword=@,48-57,192-255
Last set from C:/Program Files (x86)/Vim/vim73/syntax/tex.vim

Note that the above path to tex.vim is the same as that returned by suggested command

:echo globpath(&rtp, 'syntax/tex.vim')

Thanks for cluing me in to the fact that searching for iskeyword won't find the short form "isk". It looks like tex.vim gets called when I enable syntax highlighting. The chunk of code that sets isk-=_ is:

" (La)TeX keywords: only use the letters a-zA-Z {{{1
" but _ is the only one that causes problems.
if version < 600
set isk-=_
if b:tex_stylish
set isk+=@
endif
else
setlocal isk-=_
if b:tex_stylish
setlocal isk+=@
endif
endif

If I did not want to change the files in the install tree, is there somewhere else I can put "setl isk+=_" so that my tex file edit sessions/files/buffers always treat underscore as a keyword character? I tried putting it into "/c/Program Files (x86)/Vim/vimfiles/syntax/tex.vim", but that doesn't seem to do it.
--------------------------------------------------
P.s. I also looked for "isk" and "keyword" in $VIM/ftplugin/tex.vim, no hits.

Furthermore, the commands

help g:tex_isk
help tex_isk

yield the error message:

E149: Sorry, no help for g:tex_isk
E149: Sorry, no help for tex_isk

Finally, the commands

echo &g:tex_isk"
echo &tex_isk"

yield

E113: Unknown option: tex
E15: Invalid expression: &g:tex_isk

E113: Unknown option: tex
E15: Invalid expression: &tex_isk

Perhaps tex_isk is part of an installation-specific customization?

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