Re: new style Emacs compile

[Daniel Pfeiffer]

Saluton, Moin,

Stefan Monnier <address@hidden> skribis:

> > My structure mostly adds variants, i.e. file, line and maybe column can
> > also be lists rather than indexes.  The tail has changed.  Where the
> > formats were before there are new elements, while the formats will go into
> > the file-list (because they pertain to the file name).  This means that
> > for all matchers not using the secret function-feature or formats the
> > compatibility is given.
> 
> Good.

Of course when I remove the limitation that matchers are implicitly anchored at 
beginning-of-line, everybody will have to add a ^ in front, or they may be 
matching more than what they thought.  (But then the standard regexps are 
already quite hairy :-)

On the plus side, because I give names (like compilation-gnu-messages) to these 
complex constructs, customizing this alist will become far easier.

> > This doesn't help.  If nobody can say what to look for, Emacs can't look
> > for it.  I've asked on the TeX newsgroup and got one disheartening reply
> > so far:
> 
> It's sadly a problem.  Don't try to solve it.
> 
> > clicking -3,11 would go to those lines in dir1/a while +4,10 would do the
> > same for dir2/a -- and so forth however many difference groups there are.
> 
> My diff-mode.el does something similar.

Emacs: Eight Million features And Constantly Surpassing itself.  How is a mere 
mortal to realize all there is :-)

> > And a new command could be configured like the -p option to patch.
> > I.e. it would know in which directory to find the file a corresponding to
> > dir1/a.  Or more generally (also useful for remote-compile) there would be
> > a translation function "when diff says dir1/a go to foo/bar".
> 
> Take a look at how my diff-mode.el does it: I always planned to adapt it
> for use in compile.el but never got around to it.  It basically tries to
> learn by example: if it can't find dir1/a, and the user says "it's in
> foo/a.bar", when dir1/b is requested it will try foo/b.bar.

I like the "Patch already applied" message.  This is definitely a plus to just 
jumping there as I had intended.  But to offer this, compile would need some 
general "Bug already fixed" artificial intelligence, where diff could hook in...

Diff-mode already goes into the internal data-structures of the old compile 
message parser.  So it'll have to be looked at anyways.  Any ideas on how to 
integrate diff-mode's intelligence with compile's plain jump-to logic?

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

-- 
lerne / learn / apprends / läramå    Esperanto:
                              http://lernu.net/