Date: Sat, 28 Jul 2007 19:06:01 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: cptsalek@gmail.com, mail@michaelworobcuk.de, 000.fbsd@quip.cz, freebsd-stable@freebsd.org Subject: Re: syntax highlighting of rc.conf with vim Message-ID: <20070729020601.GA45042@eos.sc1.parodius.com> In-Reply-To: <239431185628362@webmail18.yandex.ru> References: <9C496190-E2DE-4015-A340-CA0062B6EF9E@michaelworobcuk.de> <14989d6e0707280355j1c808a95o52ab8d4b012660c2@mail.gmail.com> <CFB247C4-B151-405C-BF1F-0065A6A5C31A@michaelworobcuk.de> <46AB35F9.7060302@quip.cz> <239431185628362@webmail18.yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 28, 2007 at 05:12:42PM +0400, Andrey V. Elsukov wrote: > > Am 28.07.2007 um 14:26 schrieb Miroslav Lachman: > > > If your rc.conf file will start with comment character (#) then > > > syntax highlight will be OK. > > WUOUf, that is a pretty trick. Thanks very much. It works. > > Also you can put in the comment highlight type: > # vim: filetype=sh FreeBSD has somewhat of an exception to this. The feature you're talking about is called vim modeline, and there's quite a big warning in the vim port (shown during installation) about modelines causing historic security problems. Regardless of that fact, I do use them myself, but I'm selective about them. I prefer to use .vimrc and set up appropriate AutoCmd entries depending upon fully-qualified paths for config files. Take your pick. I just wanted to point out that FreeBSD does explicitly mention the historic issues with modeline in the port. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070729020601.GA45042>