From: "Andreas Röhler" <andreas.roehler@online.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32012@debbugs.gnu.org
Subject: bug#32012: 27.0.50; jit-lock--run-functions broken
Date: Sat, 30 Jun 2018 13:19:40 +0200 [thread overview]
Message-ID: <8be5975a-6b51-4a74-745c-7b601bd3ce43@online.de> (raw)
In-Reply-To: <83in60mths.fsf@gnu.org>
On 30.06.2018 12:57, Eli Zaretskii wrote:
>> Cc: 32012@debbugs.gnu.org
>> From: Andreas Röhler <andreas.roehler@online.de>
>> Date: Sat, 30 Jun 2018 08:54:49 +0200
>>
>> On 30.06.2018 08:34, Eli Zaretskii wrote:
>>>> From: Andreas Röhler <andreas.roehler@online.de>
>>>> Date: Fri, 29 Jun 2018 22:16:55 +0200
>>>>
>>>> Running into it from ert-tests which call ‘jit-lock-fontify-now’
>>>>
>>>> When reproduced from emacs -Q in scratch-buffer:
>>>>
>>>> Debugger entered--Lisp error: (wrong-number-of-arguments (2 . 2) 0)
>>>> jit-lock--run-functions()
>>>> eval((jit-lock--run-functions) nil)
>>>> elisp--eval-last-sexp(nil)
>>>> eval-last-sexp(nil)
>>>> funcall-interactively(eval-last-sexp nil)
>>>> call-interactively(eval-last-sexp nil nil)
>>>> command-execute(eval-last-sexp)
>>>
>>> Why did you think you can call that function tis way?
>>>
>>
>> Hmm, by looking at its signature
>>
>> (defun jit-lock-fontify-now (&optional start end)
>>
>> Why that shouldn't work?
>
> That's not what the backtrace suggests. It suggests that you invoked
> jit-lock--run-functions via eval-last-sexp.
Right. But the arguments are optional.
Wherefrom to expect it failing?
next prev parent reply other threads:[~2018-06-30 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 20:16 bug#32012: 27.0.50; jit-lock--run-functions broken Andreas Röhler
2018-06-30 6:34 ` Eli Zaretskii
2018-06-30 6:54 ` Andreas Röhler
2018-06-30 10:57 ` Eli Zaretskii
2018-06-30 11:19 ` Andreas Röhler [this message]
2018-06-30 11:42 ` Eli Zaretskii
2018-06-30 12:33 ` Andreas Röhler
2018-06-30 13:06 ` Andreas Röhler
2018-06-30 13:52 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8be5975a-6b51-4a74-745c-7b601bd3ce43@online.de \
--to=andreas.roehler@online.de \
--cc=32012@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.