Hi, I encountered problem with syntax highlighting when I set vim as my editor using command 'sudoedit'. I can reproduce it like in Fedora:
1) $ sudo dnf install vim bind 2) $ export EDITOR=vim 3) $ sudoedit /etc/named.conf As result, there is syntax highlighting for bind zone file, not for named.conf. I saw it is common issue (sudoedit creates copy of file in /var with name namedXXXX.conf , so hard-coded regular expression in filetype.vim doesn't recognize it), but always fixed as workaround on local machine. Is there any reason why these fixes aren't in VIM by default (I think it can be like in attached patch - just edit regular expression)? Can we fix it at least for named.conf, because when VIM recognizes named.conf filetype badly as bind zone file (because of scripts.vim:323), it shows all text in red color. -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
diff --git a/filetype.vim.orig b/filetype.vim index 173b5eb..30bce3d 100644 --- a/filetype.vim.orig +++ b/filetype.vim @@ -288,7 +288,7 @@ au BufNewFile,BufRead *.bib setf bib au BufNewFile,BufRead *.bst setf bst " BIND configuration -au BufNewFile,BufRead named.conf,rndc.conf setf named +au BufNewFile,BufRead named*.conf,rndc*.conf setf named " BIND zone au BufNewFile,BufRead named.root setf bindzone
