GNU bug report logs - #50482
Unhelpful error message whilst byte-compiling a function.

Previous Next

Full log

Message #8 received at 50482 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: 50482 <at> debbugs.gnu.org
Subject: Re: bug#50482: Unhelpful error message whilst byte-compiling a
 function.
Date: Thu, 09 Sep 2021 16:42:29 +0200

Alan Mackenzie <acm <at> muc.de> writes:

> I'm working on a function which begins thus:
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> (defun jit-lock--run-functions-new (beg end &optional last-fun)
>   (let ((tight-beg nil) (tight-end nil) ; The region we have fully fontified.
>         (loose-beg beg) (loose-end end)) ; The maximum region we have fontified
>                                         ; with at least some of
>                                         ; `jit-lock-functions'.
>     (run-hook-wrapped
>      'jit-lock-functions
> ......
> ......
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
> On doing M-x compile-defun on this function, I get as sum total of the
> output in *Compile-Log* this:
>
> Buffer jit-lock.el:416:1: Error: Wrong number of arguments: #<subr
> macroexp--warn-wrap>, 3

If I just put that in a buffer (and add some closing parentheses), I
don't get that warning.  Is there something else needed?

> ..  I don't know what this means.  Line 416 is the line where the defun
> starts.  I don't have `macroexp--warn-wrap' anywhere in my source code,
> it's not clear to what form 3 arguments are being wrongly passed, or
> where.

The warn-wrap stuff comes from `with-suppressed-warnings', I think.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.