unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33170@debbugs.gnu.org, Alex Branham <alex.branham@gmail.com>
Subject: bug#33170: 27.0.50; interactive spec with cl-defgeneric/method
Date: Sat, 27 Oct 2018 17:49:13 -0400	[thread overview]
Message-ID: <jwv4ld7kqry.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83r2gbmksh.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Oct 2018 19:11:42 +0300")

>> > I don't think generic functions can be interactive.  At least it is
>> > not documented anywhere that they can be.
>> Ah, that's unfortunate. Perhaps this limitation should be documented
>> somewhere?
> If Stefan (CC'ed) says it's a limitation and not a bug, I will
> document it.

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,


        Stefan





  parent reply	other threads:[~2018-10-27 21:49 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 [this message]
2018-10-29 14:18             ` Alex Branham
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

  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=jwv4ld7kqry.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=33170@debbugs.gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=eliz@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 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).