[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vim-dev
Subject:    RE: syntax highlighting problem with 6.2
From:       "Keith Roberts" <kroberts () wpas-inc ! com>
Date:       2003-09-22 18:41:33
[Download RAW message or body]

>-----Original Message-----
>From: Bram@moolenaar.net [mailto:Bram@moolenaar.net]
>Sent: Monday, September 22, 2003 10:32 AM
>To: Keith Roberts
>Cc: 'Norbert Tretkowski'; vim-dev@vim.org
>Subject: RE: syntax highlighting problem with 6.2
>
>Keith Roberts wrote:
>
>> I'm talking through my hat here, but wouldn't it be possible to
>> distinguish
>> between the two by setting 'makeprg' differently for gmake, or by setting
>> some global variable which identifies which is being used, and use the
>> appropriate behavior?
>
>Setting a variable such as "make_is_gmake" could be a solution to
>highlight two Makefile variants with one syntax file.  It doesn't solve
>the problem of automatically switching though.  I edit all kinds of
>Makefiles myself (also BSD make, which is incompatible with gmake in
>several ways).
>
>Since the file being edited does not necessarily correspond with the
>setting of 'makeprg' or even what the "make" program does, I can't think
>of a reliable method to find out the kind of make to use for
>highlighting.  For example, my "make" program is BSD make, but I often
>edit gmake-style Makefiles.
>
>Best solution, of course, is to get rid of all Makefiles and use Aap
>recipes :-).

Well, if gmake and BSD make could be trained to recognize filetype of .gmake
and .bmake, the solution would be obvious ... :))

I was making the assumption that the user always used the same makeprg
rather than having to deal with several; perhaps not reality-based.  Enter
the dreaded modeline.  :))




[prev in list] [next in list] [prev in thread] [next in thread]