From: Yuan Fu <casouri@gmail.com>
To: 42590-done@debbugs.gnu.org
Subject: bug#42590: Fwd: bug#42590: 27.0.91; Advice error for interactive commands
Date: Wed, 29 Jul 2020 15:22:36 -0400 [thread overview]
Message-ID: <D3D82DE6-580A-4CF7-A8D5-C646B179F524@gmail.com> (raw)
In-Reply-To: <B7E67629-1E59-4B92-8833-D7204F2DE8A5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
> Begin forwarded message:
>
> From: Yuan Fu <casouri@gmail.com>
> Subject: Re: bug#42590: 27.0.91; Advice error for interactive commands
> Date: July 29, 2020 at 3:21:52 PM GMT-4
> To: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 42590@debbugs.gnu.org
>
>
>
>> On Jul 29, 2020, at 1:41 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
>>
>> Yuan Fu <casouri@gmail.com> writes:
>>
>>> To reproduce the issue, evaluate
>>>
>>> (advice-add 'backward-delete-char-untabify :after 'ignore)
>>>
>>> and hit backspace (which should call backward-delete-char-untabify), and
>>> an error occurs: apply: Wrong number of arguments: (1 . 2), 0
>>
>> Had to think about it. But it's expected I think: `ignore' is
>> interactive, and as documented, its interactive spec overwrites the
>> interactive spec of the original function. And it doesn't fit.
>>
>> So everything behaves as documented, it's your specified after advice
>> that causes the problem. Right?
>>
>> Michael.
>
> Thanks. I first advised with another interactive function and found this problem. Ignore is just an example. Once I remove the advice the problem went away. I’ll close this report now.
>
> Yuan
[-- Attachment #2: Type: text/html, Size: 4011 bytes --]
prev parent reply other threads:[~2020-07-29 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 1:58 bug#42590: 27.0.91; Advice error for interactive commands Yuan Fu
2020-07-29 17:41 ` Michael Heerdegen
2020-07-29 19:21 ` Yuan Fu
2020-07-29 19:22 ` Yuan Fu [this message]
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=D3D82DE6-580A-4CF7-A8D5-C646B179F524@gmail.com \
--to=casouri@gmail.com \
--cc=42590-done@debbugs.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.
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.