Re: makefile-mode font-lock bugs and annoyances

[Daniel Pfeiffer]

la 11.06.2005 00:37 Richard Stallman skribis:

>    As GNU-make is upward compatibile with traditional make, this makes the
>    implementation easy:  just highlight GNU-make extensions by default, no
>    mode-setting or whatever is necessary.
>
> Daniel, that's how I want it to work.
For one thing you said yesterday that you wanted someone else to 
(partially) undo my changes. After that statement, this one is rather 
unclear. Are you trying to tell me you reconsidered? I'm not doing 
anything until I get a clear go ahead to repair the open issues that 
were brought up these last days, to save my work.

For another, when you load a .h file it comes up in C mode, even though 
enough .h files contain C++. Nobody would write class or template or 
even import or interface in C file, so why not have a superset of C, C++ 
or Java in one mode? That would be the same as having all makefiles in 
gmake mode, or, for that matter, in makepp mode because that is the 
superset. Nobody would (hopefully...) write "ifdef FOO" in a plain 
Makefile or "and ifsys aix" or "$((perl if( ... ) { ... }))" in a 
GNUMakefile. Too bad for BSD make which is incompatible!

Instead I had suggested doing some rudimentary scanning of the file to 
decide which submode is applicable. But I'd be just as happy (with less 
work for me) to just put [Mm]akefile in makefile-gmake-mode (except on 
BSD systems, where makefile-bsdmake-mode is the default). Then the 
modeline would clearly indicate this. And those who care could do C-c 
C-m C-m to go to plain make mode or set up their alist accordingly.

I see this separation as cleaner, and I don't think there's an overhead 
for derived modes to even bother about this, as long as the "politically 
right" mode gets chosen by default.

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

--
lerne / learn / apprends / lär dig / ucz się    Esperanto:
                             http://lernu.net/