2 fixes for compile.el

[Daniel Pfeiffer]

Hi,

Sorry, this time it's definite.  My post yesterday had some glitches, and while 
debugging them I corrected and slimmed down quite a few of the regexps.  Now I 
match all of the messages provided as examples except for the "horrible fc" and 
BSD lint 2 (both of which didn't work before either) and BSD lint 3, which 
still matches way too much.

While doing this it struck me that compile is a horrible cludge from 
prehistorical times.  Now that font lock can trivially set arbitrary properties 
-- and does it much better than the stop & go approach of compile!!! --, it 
would be best to let it do the whole parsing.

next-error and the like would then only have to scan the buffer for fileinfo 
text properties left for it by font lock.  I guess this would make the library 
a third smaller and more efficient too.

best regards
Daniel

---------------

Two more things:

- the word warning now gets found case insensitively in my new diff

- font-lock in CVS has for quite a few versions contained the line

,(+ ,c-type-names-depth 2))

which understandably causes an error for me in c-mode.  But even taking away 
the comma leaves the var undefined :-( (in 1.199 which is the latest that might 
have worked with 21.2)

---------------

Hi,

this fixes 2 things:

- warnings and errors didn't get distinguished which finally got insupportable 
with strict gcc 3.2

- compile buffers are hypertext but didn't have mouse hightlight

Note that the latter uses font-lock's facename as property list, which was 
documented in 21.2 (as delivered by SuSE 8.1), but only works when getting a 
newer font-lock and syntax from CVS.

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

-- 
 -- http://dapfy.bei.t-online.de/sawfish/
  --

ChangeLog
Description: Binary data

compile.el.diff
Description: Binary data