From: Christopher Dimech <dimech@gmx.com>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Prefix Argument and optional argument
Date: Thu, 7 Jul 2022 21:19:43 +0200 [thread overview]
Message-ID: <trinity-88bb4e8c-9ecf-4d98-b57a-ed758c5f5677-1657221583254@3c-app-mailcom-bs15> (raw)
In-Reply-To: <874jztez2d.fsf@dataswamp.org>
> Sent: Friday, July 08, 2022 at 3:12 AM
> From: "Emanuel Berg" <incal@dataswamp.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Prefix Argument and optional argument
>
> Stefan Monnier via Users list for the GNU Emacs text editor wrote:
>
> >> (defun poke (prefix)
> >> "TODO."
> >> (interactive "P")
> >> ...)
> >>
> >> gives
> >>
> >> Warning: misplaced interactive spec: ‘(interactive P)’
> >
> > I don't get this warning here. Instead I get two arnings,
> > one about the fact that `prefix` is not used, and the other
> > about the fact that `...` is not a known variable.
>
> Do
>
> C-u M-x checkdoc-current-buffer RET
>
> and learn that it also has a docstring problem:
>
> Argument ‘prefix’ should appear (as PREFIX) in the doc
> string
>
> At the stage when it does nothing, it seems 'poke' has so many
> problems already!
Don't poke! ;)
> I also don't get any warnings but the ones you mention,
>
> Warning: Unused lexical argument `prefix'
> Warning: reference to free variable ‘...’
>
> and that's on
>
> GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+
> Version 3.24.24, cairo version 1.16.0) of 2022-05-28
> [commit 707124d2b92780b4f21d72c7c62899e074fa8ced]
>
> (Love the 'ever' command BTW,
> https://dataswamp.org/~incal/emacs-init/meta.el )
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2022-07-07 19:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 2:51 Prefix Argument and optional argument carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-05 6:52 ` Bruno Barbier
2022-07-05 11:32 ` Michael Heerdegen
[not found] ` <N6C6ucy----2@missing-mail-id>
2022-07-05 20:26 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-06 11:25 ` Michael Heerdegen
2022-07-06 21:35 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-07 19:04 ` Stefan Monnier via Users list for the GNU Emacs text editor
[not found] ` <N6Cxz_J--3-2@tutanota.com-N6F1to4----2>
2022-07-06 21:18 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-07 10:56 ` Michael Heerdegen
2022-07-07 11:51 ` Emanuel Berg
2022-07-07 12:02 ` Emanuel Berg
2022-07-07 12:15 ` Michael Heerdegen
2022-07-07 12:38 ` Christopher Dimech
2022-07-07 12:53 ` Michael Heerdegen
2022-07-07 13:15 ` Christopher Dimech
2022-07-07 13:45 ` Michael Heerdegen
2022-07-07 14:03 ` Christopher Dimech
2022-07-07 14:35 ` Michael Heerdegen
2022-07-07 15:20 ` Emanuel Berg
2022-07-07 15:31 ` Michael Heerdegen
2022-07-07 15:50 ` Emanuel Berg
2022-07-07 17:03 ` docstrings (was: Re: Prefix Argument and optional argument) Emanuel Berg
2022-07-07 17:06 ` docstrings (was: " Christopher Dimech
2022-07-07 17:48 ` Christopher Dimech
2022-07-07 19:20 ` Emanuel Berg
2022-07-07 19:42 ` enforce/automate docstring correctnes (was: Re: docstrings) Emanuel Berg
2022-07-07 14:58 ` Prefix Argument and optional argument Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-07 15:12 ` Emanuel Berg
2022-07-07 19:19 ` Christopher Dimech [this message]
2022-07-07 19:38 ` Christopher Dimech
2022-07-07 14:08 ` Jean Louis
2022-07-07 15:41 ` Christopher Dimech
2022-07-07 13:04 ` Yuri Khan
2022-07-07 13:38 ` Michael Heerdegen
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=trinity-88bb4e8c-9ecf-4d98-b57a-ed758c5f5677-1657221583254@3c-app-mailcom-bs15 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.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.
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).