From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: perhaps rephrase "misplaced interactive spec"
Date: Thu, 31 Jul 2014 18:45:19 -0400 [thread overview]
Message-ID: <barmar-2E8AAF.18451931072014@news.eternal-september.org> (raw)
In-Reply-To: 87iomdusvs.fsf@debian.uxu
In article <87iomdusvs.fsf@debian.uxu>,
Emanuel Berg <embe8573@student.uu.se> wrote:
> Emanuel Berg <embe8573@student.uu.se> writes:
>
> > (define-minor-mode MODE DOC ...
> >
> > so I wonder why I just didn't get a
> > wrong-number-of-arguments? That would have instantly
> > made it clear.
>
> Aha, now I see, it is because of those others :property
> arguments. So it is more complicated.
>
> Is the reason for having those (:some thing) that some
> can be provided, and others left out? Is that
> implemented function-by-function (like a C binary or
> shell function that has to decode what options were
> passed)?
>
> (define-minor-mode MODE DOC &optional INIT-VALUE
> LIGHTER KEYMAP &rest BODY)
>
> Although it was more complicated than I thought, that
> doesn't make the warning message any more clear...
> Especially since it works just fine (the minor mode)
> without the docstring it gets even more confusing.
This type of thing tends to happen when functions and macros evolve over
time. Probably the original definition was just
(define-minor-mode MODE DOC &rest BODY)
Then someone decided to add options, and the most obvious place to add
them was before the BODY.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2014-07-31 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 21:06 perhaps rephrase "misplaced interactive spec" Emanuel Berg
2014-07-31 21:21 ` Emanuel Berg
2014-07-31 22:45 ` Barry Margolin [this message]
2014-08-21 19:55 ` lee
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=barmar-2E8AAF.18451931072014@news.eternal-september.org \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@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.