From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: ahyatt@gmail.com, 3418@debbugs.gnu.org, garyo@genarts.com
Subject: bug#3418: Issue with compile.el and compilation-parse-errors-filename-function
Date: Fri, 11 Aug 2017 09:34:59 +0300 [thread overview]
Message-ID: <83378ysjcc.fsf@gnu.org> (raw)
In-Reply-To: <878tir2ai2.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Cc: Eli Zaretskii <eliz@gnu.org>, 3418@debbugs.gnu.org, Andrew Hyatt <ahyatt@gmail.com>
> Date: Thu, 10 Aug 2017 20:50:29 -0400
>
> Gary Oberbrunner <garyo@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)))
Or use func-arity?
next prev parent reply other threads:[~2017-08-11 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 14:46 bug#3418: Issue with compile.el and compilation-parse-errors-filename-function Gary Oberbrunner
2016-01-26 5:21 ` Andrew Hyatt
2016-01-26 14:42 ` Eli Zaretskii
2016-01-26 15:15 ` Gary Oberbrunner
2016-01-26 16:08 ` Eli Zaretskii
2016-01-26 16:19 ` Gary Oberbrunner
2017-08-11 0:50 ` npostavs
2017-08-11 1:04 ` Gary Oberbrunner
2017-08-11 6:34 ` Eli Zaretskii [this message]
2017-08-12 15:42 ` npostavs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83378ysjcc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3418@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=garyo@genarts.com \
--cc=npostavs@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.