GNU bug report logs - #32012
27.0.50; jit-lock--run-functions broken

Previous Next

Package: emacs;

Reported by: Andreas Röhler <andreas.roehler <at> online.de>

Date: Fri, 29 Jun 2018 20:15:02 UTC

Severity: normal

Tags: notabug

Found in version 27.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Andreas Röhler <andreas.roehler <at> online.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 32012 <at> debbugs.gnu.org
Subject: bug#32012: 27.0.50; jit-lock--run-functions broken
Date: Sat, 30 Jun 2018 08:54:49 +0200

On 30.06.2018 08:34, Eli Zaretskii wrote:
>> From: Andreas Röhler <andreas.roehler <at> 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?

Coming here because when using font-lock-fontify-buffer in ert-tests, 
get a warning for interactive use only. Should use font-lock-ensure.
But font-lock-ensure isn't known from ert.

Maybe another bug?

Need with-buffer-prepared-for-jit-lock which seems not being provided by 
uncompiled font-lock.el

Thanks,
Andreas





This bug report was last modified 7 years and 46 days ago.

Previous Next


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