From: Eli Zaretskii <eliz@gnu.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: 33170-done@debbugs.gnu.org, monnier@IRO.UMontreal.CA
Subject: bug#33170: 27.0.50; interactive spec with cl-defgeneric/method
Date: Tue, 30 Oct 2018 12:15:37 +0200 [thread overview]
Message-ID: <838t2floza.fsf@gnu.org> (raw)
In-Reply-To: <877ei0n8du.fsf@gmail.com> (message from Alex Branham on Mon, 29 Oct 2018 09:18:53 -0500)
> From: Alex Branham <alex.branham@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 33170@debbugs.gnu.org
> Date: Mon, 29 Oct 2018 09:18:53 -0500
>
> 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.
Done.
next prev parent reply other threads:[~2018-10-30 10:15 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
2018-10-30 10:15 ` Eli Zaretskii [this message]
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=838t2floza.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33170-done@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--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 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).