Re: makefile-mode font-lock bugs and annoyances

[Glenn Morris]

Daniel Pfeiffer wrote:

> Like I said, I'll solve this more intelligently.

I really don't think this is the time to be doing this. Emacs is
supposed to be a feature freeze state so it can be released sometime.
Admittedly, it's not clear how anyone is supposed to recognize this...

I'm sure your new make code has lots of improvements under the hood,
but:

i) the surface appearance puts me off it completely. Yes, I'm shallow.
ii) the timing is bad.
iii) the lack of consultation is bad.

I have nothing more to say, so I'm shutting up about it after this.

> That's the nice thing about freedom. :-) And you'll still have
> correct recognition of targets.

The "you can customize it to look how you want" argument is not a
valid way to justify default behaviour that no-one apart from you
seems to like.

As a counter proposal, why not put the gaudier make font-locking
(together with that font-lock-negation stuff that no-one else liked
either), in your .emacs? Discuss bringing it back after 22.1 comes
out.

>>>I don't know why, but when I took over makefile mode, single
>>>character variables were already highlighted differently from
>>>parenthesized multiletter ones.

I don't see this in Emacs-21.3 (I don't have an old CVS version to
test). There, $(FOO), $^, and $@ look exactly the same. In the current
CVS, they all look different.

> Hey cut it out! If it bothers you, why didn't you complain or do
> something about this 10 years ago? On the one hand I get flamed for
> having changed make-mode, and then right afterwards I also get
> flamed for not having changed it.

I don't think I'm flaming you. I'm just saying I don't agree with you,
and I haven't seen anyone who does.


Shutting up... now.