Subject: Re: bug#32012: 27.0.50; jit-lock--run-functions broken

From: Andreas Röhler <[email-masked]>
Date: Sat, 30 Jun 2018 15:06:23 +0200

On 30.06.2018 13:42, Eli Zaretskii wrote:
>> Cc: [email-masked]
>> From: Andreas Röhler <[email-masked]>
>> Date: Sat, 30 Jun 2018 13:19:40 +0200
>>
>>>> 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?
> 
> A function that has optional argument doesn't necessarily support
> invocation without arguments in any arbitrary context.

When looking for a example-case, mistakenly did run 
jit-lock--run-functions, which requires args, Should run 
jit-lock-fontify-now - which might be evaluated in scratch - but doesn't 
help for the original issue.

While file a new report maybe.
Please close this, sorry for the noise and thanks for your care,

Andreas