Re: Find this error in... Changes in complete.el?

[Stefan Monnier]

> I think it's due to this change

> 2006-07-18  Stefan Monnier  <address@hidden>

>       * progmodes/compile.el (compilation-find-file): Handle the
>       cases where the user selects a non-existent file.

Indeed.

> Does the patch below restore the old behaviour for you?

I think reverting is basically correct, except that we want to remember that
we reverted it and why.

The problem that my patch was trying to fix was to try and enforce during
completion that the user cannot tell compile to use directory "foo" when
"foo" doesn't contain the file we're looking for.

Now this predicate is right when used in minibuffer-complete-and-exit, but
not in minibuffer-complete because the user may as here want to select the
file "foo/bar" or the dir "foo/toto" (which does contain the file compile is
looking for).  Sadly, the completion system we have only has one predicate
and the predicate doesn't know for which of the two cases it's being called.

> It's not a fix because it undoes whatever Stefan's patch intended, which I
> don't quite understand because I have a different problem when a generate this
> message (with a linker error):

> Find this error in (default In function `myprint':/home/nickrob/myprint.c): ~/

> because my compilation message (gcc version 4.1.0) is:

> myprint.o: In function `myprint':/home/nickrob/myprint.c:27: undefined
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>  reference to `mysquare6'

Please complain to the linker guys that they should use error messages that
follow the GNU standard.


        Stefan