vim: named syntax highlighting

Fri, 01/20/2012 - 11:17 - augustin
Project:Linux software
Component:Documentation
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active
Related pages:#251: Vim
Description

vim: named syntax highlighting.

I have identified 2 problems:
- when editing named.conf.options, a common bind9 configuration file name on Debian systems, the syntax highlighting is not selected by default.
Other file names to include: named.conf.*.

- the keyword listen-on-v6 is not recognized. Add in in named.vim:

syn keyword namedOption contained allow-query allow-transfer allow-recursion listen-on-v6
\   nextgroup=namedAML skipwhite

Comments

#1

augustin - 01/20/2012 - 11:28

Also, comments within sections do not work.

E.g.:

named.conf:

logging {
    #
    # Define channels for the two log files
    #
    channel query_log {
        severity info;
        print-time yes;
  file "query.log" versions 3 size 100M;
    };
};

#2

augustin - 01/20/2012 - 11:29

"info" in "severity info" (see above) should be green.

#3

augustin - 01/20/2012 - 12:08

add filenames in:
/usr/share/vim/vim73 $ vi filetype.vim

#4

augustin - 01/22/2012 - 02:45

The syntax does not seem to take into account the different commenting styles: #, //, /* */
http://ftp.isc.org/isc/bind9/cur/9.7/doc/arm/Bv9ARM.ch06.html#id2574128

#5

augustin - 01/23/2012 - 06:33

Also, in the zone file. The SOA coloring changes according to the use of parenthesis. E.g. the email address is printed blue if placed before the opening parenthesis, and white if within the parenthesis. The colors should not change either way.