[PATCH] Handle output from Emacs byte-compilation properly

[Jostein Kjønigsen]

It's common for module-developers to run Emacs byte-compilation in
separate build-scripts.

When invoking byte-compile on Emacs-lisp files you often get the
following headers:

- In toplevel form:
- In end of data:

When these errors show up in the output of a build-script initiated
through M-x compile and show up in a compilation-mode buffer, these
lines gets treated as guile-errors for files which doesn't exist.

This is due to the following regexp, which is quite frankly extremely
wide:

    (guile-file "^In \\(.+\\):\n" 1)

This breaks prev-error and next-error based navigation because the
files "toplevel form" and "end of data" doesn't exist.

This patch ensures those lines are treated as information only before
getting to the guile-file regexp.

--
Jostein Kjønigsen
address@hidden / address@hidden

compilation-mode-emacs-lisp.patch
Description: Text Data