From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 50482@debbugs.gnu.org
Subject: bug#50482: Unhelpful error message whilst byte-compiling a function.
Date: Thu, 09 Sep 2021 16:42:29 +0200 [thread overview]
Message-ID: <87k0jpu7xm.fsf@gnus.org> (raw)
In-Reply-To: <YTkfGUmOcOx+qley@ACM> (Alan Mackenzie's message of "Wed, 8 Sep 2021 20:37:45 +0000")
Alan Mackenzie <acm@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
next prev parent reply other threads:[~2021-09-09 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 20:37 bug#50482: Unhelpful error message whilst byte-compiling a function Alan Mackenzie
2021-09-09 14:42 ` Lars Ingebrigtsen [this message]
2021-09-09 17:13 ` Alan Mackenzie
2021-09-09 18:12 ` Alan Mackenzie
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=87k0jpu7xm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50482@debbugs.gnu.org \
--cc=acm@muc.de \
/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).