Re: 27.0.50, (void-function with-buffer-prepared-for-jit-lock)

["Andreas Röhler" <andreas.roehler@online.de>]

On 30.06.2018 01:14, Stefan Monnier wrote:
>> when running an uncompiled Emacs --which is preferred for jumping into maybe
>> changed sources-- got
> 
> There's no such thing as "an uncompiled Emacs". 

Okay. Should mean didn't compile elisp .el files into .elc



  All it means is that
> you did something to use some uncompiled code somewhere, but without
> clarifying what it is you did.
> 
>> Error during redisplay: (jit-lock-function 1245) signaled (void-function
>> with-buffer-prepared-for-jit-lock)
> 
> So, apparently what you did was not right: 


Well, the question is if a general used function should depend from

(eval-when-compile

Maybe there are reasons, don't know.
Being able to run elisp code without compiling its .el sources is a gain 
to consider.

Might be also a design issue of eval-when-compile, saying:

"In interpreted code, this is entirely equivalent to
‘progn’, except that the value of the expression may be (but is
not necessarily) computed at load time if eager macro expansion
is enabled."

Such "may be (but is not necessarily)" doesn't sound that well.

Best,
Andreas