Limiting a match in vim to certain filetypes?
Asked Answered
P

2

8

I have the following in my .vimrc to highlight lines longer than 80 chars:

highlight OverLength ctermbg=red ctermfg=white guibg=#592929
match OverLength /\%81v.*/

This works quite well. However, the problem is that I would prefer it if it only worked on certain file types. Basically, any programming language should be highlighted and things like html, xml, and txt files should not be. I'm pretty sure I could do this easily with an autocmd, but I'm not sure if that is the best way to accomplish that goal. Anybody have any opinions?

Postulate answered 9/11, 2009 at 17:46 Comment(0)
T
7

Sounds like you might want something like:

autocmd FileType html,xml highlight OverLength ctermbg=red ctermfg=white guibg=#592929
autocmd FileType html,xml match OverLength /\%81v.*/

Seems to work for me anyway :-)

Trager answered 9/11, 2009 at 17:53 Comment(4)
Argh, actually that's not quite what you asked for is it. Hmm, wonder if it's possible to negate the FileType...Trager
Yeah, like I said, I think doing it this way with the autocmds could work well enough, you just need to swap which files are here. Instead of html and xml, it should be c, c++,etc... So, if the FileType could be negated, then that would be even better.Postulate
Hmm, I don't think it is. Look like you'll have to actually list the filetypes you want this highlighting for.Trager
You can use autocmd FileType * to match any type. Presumably it's overwritten by a more specific setting.Dehumidify
M
6

The issue with using match for a task like this is that it is local to the active window, not to the buffer being edited. I'd try something along the following lines:

highlight OverLength ctermbg=red ctermfg=white guibg=#592929
fun! UpdateMatch()
    if &ft !~ '^\%(html\|xml\)$'
        match OverLength /\%81v.*/
    else
        match NONE
    endif
endfun
autocmd BufEnter,BufWinEnter * call UpdateMatch()

Basically, you want to trigger whenever the buffer in the current window changes. At that point, you evaluate what filetype the buffer has and adjust whether the match should be active or not.

If you also want to support editing an unnamed buffer and then setting its filetype (either via saving or manually setting &ft), the FileType even should be added to the list.

Middendorf answered 9/11, 2009 at 18:19 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.