From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Advice Required
Date: Mon, 27 Oct 2014 09:54:22 -0400 [thread overview]
Message-ID: <jwvfve9fwkk.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 21582.18359.682112.937687@mail.eng.it
> Wonderful. This does not require an external device and the error
> message in the minibuffer that you get when you run the command from
> within emacs is negligible.
I don't know what error message you're referring to.
> (defun ediff-after (foobar)
> (interactive)
> (error "pingpipe"))
> (advice-add 'ediff-quit :after #'ediff-after)
> but when I tried this a second time it did not work, complaining about
> wrong number of arguments. What did I wrong?
I don't know. Can you show us the backtrace?
Stefan
next prev parent reply other threads:[~2014-10-27 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 9:56 Advice Required Gian Uberto Lauri
2014-10-27 12:45 ` Stefan Monnier
2014-10-27 13:25 ` Gian Uberto Lauri
2014-10-27 13:54 ` Stefan Monnier [this message]
2014-10-27 14:11 ` Gian Uberto Lauri
2014-10-27 15:03 ` Stefan Monnier
2014-10-27 15:11 ` Gian Uberto Lauri
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfve9fwkk.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).