Vim not automatically recognizing groff (manpage) files

Question

I have:

$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Dec  1 2011 03:25:24)

using Debian testing.

I was playing around with an old manpage I wrote and noticed that vim (I used gedit to write it initially but have switched to vim) is not recognizing it as a nroff/groff filetype upon loading or with a:

:filetype detect

It does syntax highlighting fine, of course, with:

:set filetype=groff

Anyone else have this behaviour and if so find a fix?

BTW, it recognizes html, bash, and python scripts correctly and sets the correct syntax highlighting. Just seems to balk at groff files that are saved without the [FILENAME].1-type suffix.

Cheerio, Narnie

Does your `~/.vimrc` include any `filetype` commands? (Look in the `autocmd` commands too -- it might not be the first word on the line.) — sarnold, Feb 09 '12 at 04:01
Yes, filetype plugin on is set. Other filetypes are recognized fine. — narnie, Feb 09 '12 at 04:26
My `~/.vimrc` also has `filetype on`, `filetype indent on`, `filetype plugin on` and gets the filetype correct when testing with e.g. `/usr/share/man/man1/ls.1.gz`. (Vim 7.3, but Ubuntu packaged.) — sarnold, Feb 09 '12 at 04:42
Ur right, mine recognizes /usr/share/man/man1/ls.1.gz as well, but I'll bet it is based on the filename. I normally don't follow the convention of .sh, .py, or .1 when initially writing my scripts, python code, and manpages, respectively. Perhaps the filetype detection only relies of file suffix rather than content. It does so with bash and python scripts by content, not relying on file suffix. — narnie, Feb 09 '12 at 04:50

score 2 · Answer 1 · edited May 06 '13 at 14:02

2

Add in your ~/.vimrc file:

au BufNewFile,BufRead *.groff set filetype=groff

Or whatever extension you're using to define your groff files.

edited May 06 '13 at 14:02

fsbmain

5,267
2
16
23

answered May 06 '13 at 13:36

stephane

21
2

score 2 · Accepted Answer · answered Feb 09 '12 at 07:22

2

Vim can detect the filetype based on both the name of the file and the context. It appears that in this case vim only looks at the file name. You can write your own filetype detection script to figure out files of this type based on the context. The vim's help has some basic instructions on how to do this. Basically you can just write a vim script that detects the file type and put it in $VIMRUNTIME/scripts.vim.

answered Feb 09 '12 at 07:22

David Brown

13,336
4
38
55

This was starting to be my thinking exactly. – narnie Feb 09 '12 at 18:11

Vim not automatically recognizing groff (manpage) files

2 Answers2