From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Florian Beck <fb@miszellen.de>
Cc: 16959@debbugs.gnu.org
Subject: bug#16959: bug#16981: 24.3.50; electric-pair-delete-adjacent-pairs broken in c-mode, python-mode, maybe-others
Date: Tue, 25 Mar 2014 20:34:36 -0400 [thread overview]
Message-ID: <jwv1txp4xdh.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87siq62n6x.fsf@sophokles.streitblatt.de> (Florian Beck's message of "Tue, 25 Mar 2014 18:38:30 +0100")
> The result is that the advice SEEMS to work (the user put it in her
> .emacs and presses C-x C-e), but on restarting emacs it depends on the
> order advice defintions.
That's why the doc says:
[..]
should stay as the outermost advice. When two advices specify the
same depth, the most recently added advice will be outermost.
[..]
> Of course, from a user's point of view, macros usually are already expanded.
> How would a user go about advising, say, byte-compile-log in her .emacs?
She can't do it and hope for it to affect already compiled code, indeed.
But we use advice-add in cl.el on the `declare', `dolist', and `dotimes'
macros and it works very well. Obviously code that uses those needs to
have a (require 'cl) somewhere to make sure the advice is installed
before macro-expansion.
Stefan
next prev parent reply other threads:[~2014-03-26 0:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16921.1394480964.10748.bug-gnu-emacs@gnu.org>
2014-03-10 19:47 ` bug#16981: 24.3.50; electric-pair-delete-adjacent-pairs broken in c-mode, python-mode, maybe-others João Távora
2014-03-13 22:04 ` Alan Mackenzie
2014-03-18 1:56 ` bug#16959: " Stefan
2014-03-20 0:33 ` Florian Beck
2014-03-21 21:47 ` Stefan
2014-03-25 17:38 ` Florian Beck
2014-03-26 0:34 ` Stefan Monnier [this message]
2014-04-05 11:58 ` João Távora
2014-04-05 15:45 ` Stefan Monnier
2014-04-06 1:51 ` João Távora
2014-04-06 12:48 ` Stefan Monnier
2014-04-06 15:08 ` João Távora
2014-04-07 0:04 ` João Távora
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=jwv1txp4xdh.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=16959@debbugs.gnu.org \
--cc=fb@miszellen.de \
/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.