From: Alex Branham <alex.branham@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 33170@debbugs.gnu.org
Subject: bug#33170: 27.0.50; interactive spec with cl-defgeneric/method
Date: Mon, 29 Oct 2018 09:18:53 -0500 [thread overview]
Message-ID: <877ei0n8du.fsf@gmail.com> (raw)
In-Reply-To: <jwv4ld7kqry.fsf-monnier+emacsbugs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Sat 27 Oct 2018 at 16:49, Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
> AFAIC it's a limitation. We could support interactive specs, but I'm
> really not convinced it's worth the trouble. If using 2 functions (one
> generic and one interactive, which calls the generic one) is really
> annoying for some reason, I guess you could use
>
> (put '<GENERIC> 'interactive-form <FORM>)
>
> but I think this property should be deprecated, so don't tell anyone
> (especially don't tell me) that I even mentioned it to you,
Thanks for the response. Seems like the two-function solution is the way
to go I guess. I do think this should be documented as a limitation
somewhere though. Perhaps a note at the end of that section in the
manual along the lines:
Note that a current limitation of generic functions is that they may not
be interactive. The recommended way of working around this is to define
an interactive function that simply calls the generic function.
That's not strictly true of course since (cl-defgeneric foo ()
(interactive) (message "foo")) works just fine. It's adding methods that
seems to mess it up.
Alex
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-10-29 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 22:19 bug#33170: 27.0.50; interactive spec with cl-defgeneric/method Alex Branham
2018-10-27 6:54 ` Eli Zaretskii
2018-10-27 12:40 ` Alex Branham
2018-10-27 14:47 ` Eli Zaretskii
2018-10-27 14:50 ` Alex Branham
2018-10-27 16:11 ` Eli Zaretskii
2018-10-27 16:14 ` Alex Branham
2018-10-27 21:49 ` Stefan Monnier
2018-10-29 14:18 ` Alex Branham [this message]
2018-10-30 10:15 ` Eli Zaretskii
2018-10-30 12:48 ` Stefan Monnier
2018-10-30 13:09 ` Eli Zaretskii
2018-10-31 14:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ei0n8du.fsf@gmail.com \
--to=alex.branham@gmail.com \
--cc=33170@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.