GNU bug report logs - #3418
Issue with compile.el and compilation-parse-errors-filename-function

Previous Next

Full log

View this message in rfc822 format

From: Gary Oberbrunner <garyo <at> genarts.com>
To: npostavs <at> users.sourceforge.net
Cc: Eli Zaretskii <eliz <at> gnu.org>, 3418 <at> debbugs.gnu.org, Andrew Hyatt <ahyatt <at> gmail.com>
Subject: bug#3418: Issue with compile.el and compilation-parse-errors-filename-function
Date: Thu, 10 Aug 2017 21:04:47 -0400

[Message part 1 (text/plain, inline)]

This sounds perfect to me.

On Thu, Aug 10, 2017 at 8:50 PM, <npostavs <at> users.sourceforge.net> wrote:

> Gary Oberbrunner <garyo <at> genarts.com> writes:
>
> > If a user (such as myself) has an implementation of this function in his
> .emacs today, like so:
> >
> > (defun process-error-filename (filename)
> >   ;;; do stuff with filename
> >   filename)
> > (setq compilation-parse-errors-filename-function
> 'process-error-filename)
> >
> > and we add a new argument that gets passed to that function, it'll throw
> an error. *Users* will have to add
> >   &optional spec-dir
> > to their implementations of it to avoid the error.
>
> We could do something like
>
>     (condition-case err
>         (funcall compilation-parse-errors-filename-function filename
> spec-dir)
>       (wrong-number-of-arguments
>        ;; Try again with single arg for backwards compatibility.
>        (funcall compilation-parse-errors-filename-function filename)))
>



-- 
Gary Oberbrunner *--* CTO *--* Boris FX

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.