unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Prefix Argument and optional argument
Date: Thu, 07 Jul 2022 10:58:00 -0400	[thread overview]
Message-ID: <jwva69ldl92.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: trinity-1b15b602-f888-4afb-b90e-29952bc6213c-1657199701051@3c-app-mailcom-bs15

Christopher Dimech [2022-07-07 15:15:01] 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.
I suspect that you compiled a slightly different code.


        Stefan




  parent reply	other threads:[~2022-07-07 14:58 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                   ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-07-07 15:12                     ` Prefix Argument and optional argument Emanuel Berg
2022-07-07 19:19                       ` Christopher Dimech
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=jwva69ldl92.fsf-monnier+emacs@gnu.org \
    --to=help-gnu-emacs@gnu.org \
    --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.
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).