unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 50034@debbugs.gnu.org
Subject: bug#50034: 28.0.50; elisp capf error "Wrong type argument: listp, elisp--witness--lisp"
Date: Mon, 22 Aug 2022 15:15:41 +0200	[thread overview]
Message-ID: <87v8qk5shu.fsf@gnus.org> (raw)
In-Reply-To: <87v949ee54.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 13 Aug 2021 14:13:27 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> 1. Start "emacs -Q"
>> 2. Enter "(defmacro foo bar" in the scratch buffer
>> 3. Press M-<tab> to invoke 'completion-at-point'
>>
>> The capf will throw the error "Wrong type argument: listp,
>> elisp--witness--lisp". This error will be shown on Emacs 27 and Emacs 28.
>
> Slightly simpler repro:
>
> (defmacro foo bar
> M-: (elisp--local-variables) RET
>
> It fails here:
>
>                     (`(lambda ,args . ,body)
>                      (elisp--local-variables-1
>                       (append (remq '&optional (remq '&rest args)) vars)
>                       (car (last body))))
>
> where it expects args to be a list, but it's the symbol
> `elisp--witness--lisp'.  I'm not quite sure what the correct fix is
> here, so I've added Stefan to the CCs.  :-)

One year later, this problem is still present in Emacs 29.  Stefan, do
you have any idea what the fix here should be?





  reply	other threads:[~2022-08-22 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  1:25 bug#50034: 28.0.50; elisp capf error "Wrong type argument: listp, elisp--witness--lisp" Daniel Mendler
2021-08-13 12:13 ` Lars Ingebrigtsen
2022-08-22 13:15   ` Lars Ingebrigtsen [this message]
2022-08-23  2:05   ` Michael Heerdegen
2022-08-23 14:17   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87v8qk5shu.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50034@debbugs.gnu.org \
    --cc=mail@daniel-mendler.de \
    --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).