unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 25294@debbugs.gnu.org
Subject: bug#25294: 26.0.50; Allow more catch-all values for cl-defmethod's &context plus major-mode specializer
Date: Mon, 11 Dec 2017 19:08:40 -0500	[thread overview]
Message-ID: <87k1xserjr.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87374gstr8.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 11 Dec 2017 15:57:15 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Ahem, I only just noticed (a year later) that there was a response to
> this when I searched for bug reports I'd opened -- sorry about that.

It's had lots of time to rest then :)

>> If you want to ignore the major mode, why do you want to use the
>> major-mode specializer?
>
> It's the equivalent of the "t" branch in a `cond' statement. You write
> methods to handle specific major modes, and write another method to
> handle the catch-all case of "all other modes".

Still not really convinced by this, what's wrong with the last way you
put in your OP:

    (cl-defmethod example-method ())






  reply	other threads:[~2017-12-12  0:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 19:13 bug#25294: 26.0.50; Allow more catch-all values for cl-defmethod's &context plus major-mode specializer Eric Abrahamsen
2016-12-30  4:35 ` npostavs
2017-12-11 23:57   ` Eric Abrahamsen
2017-12-12  0:08     ` Noam Postavsky [this message]
2017-12-12  1:39 ` Noam Postavsky
2017-12-12  1:43   ` Noam Postavsky
2017-12-12  5:42   ` Eric Abrahamsen
2017-12-12 23:58     ` Noam Postavsky
2017-12-14  0:06       ` Eric Abrahamsen
2017-12-14 21:01       ` Eric Abrahamsen

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=87k1xserjr.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25294@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).