From: Juri Linkov <juri@linkov.net>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
17871@debbugs.gnu.org
Subject: bug#17871: 24.4.50; (elisp) `Core Advising Primitives': interactive spec as function?
Date: Wed, 21 Aug 2019 00:49:05 +0300 [thread overview]
Message-ID: <87d0gzwnm6.fsf@mail.linkov.net> (raw)
In-Reply-To: <877e7a2fut.fsf@gmail.com> ("Štěpán Němec"'s message of "Mon, 19 Aug 2019 01:50:18 +0200")
> And although I have managed to clarify a few points myself thanks to
> this conversation, my personal conundrum[2] remains unanswered: why does
> a simple advice have no effect on the interactive spec of the function
> being advised, and is that really a feature? But perhaps that's for
> another thread.
Recently I tried to use an advice to override the default call of
`forward-word' in `org-metaright', but this is impossible to do
because it called by `call-interactively'. Maybe your case has the
same problem?
next prev parent reply other threads:[~2019-08-20 21:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 14:13 bug#17871: 24.4.50; (elisp) `Core Advising Primitives': interactive spec as function? Drew Adams
2014-06-29 15:01 ` Michael Heerdegen
2014-06-29 15:52 ` Drew Adams
2014-06-29 22:03 ` Stefan Monnier
2014-06-29 23:49 ` Drew Adams
2014-06-30 20:48 ` Michael Heerdegen
2019-08-04 12:06 ` Lars Ingebrigtsen
2019-08-04 12:45 ` Michael Heerdegen
2019-08-04 12:56 ` Lars Ingebrigtsen
2019-08-04 15:15 ` Štěpán Němec
2019-08-05 6:26 ` Michael Heerdegen
2019-08-05 8:44 ` Štěpán Němec
2019-08-05 9:21 ` Lars Ingebrigtsen
2019-08-18 12:26 ` Michael Heerdegen
2019-08-18 13:32 ` Štěpán Němec
2019-08-18 23:06 ` Lars Ingebrigtsen
2019-08-18 23:50 ` Štěpán Němec
2019-08-19 0:35 ` Drew Adams
2019-08-20 21:49 ` Juri Linkov [this message]
2019-08-20 22:44 ` Štěpán Němec
2019-08-21 7:01 ` Stefan Monnier
2019-08-21 8:17 ` Štěpán Němec
2019-08-25 15:51 ` Stefan Monnier
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=87d0gzwnm6.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=17871@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=stepnem@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).