unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: 32012@debbugs.gnu.org
Subject: bug#32012: 27.0.50; jit-lock--run-functions broken
Date: Sat, 30 Jun 2018 15:06:23 +0200	[thread overview]
Message-ID: <6ba1427b-a26c-609c-f356-e82a5161c581@easy-emacs.de> (raw)
In-Reply-To: <83bmbsmrfr.fsf@gnu.org>

On 30.06.2018 13:42, Eli Zaretskii wrote:
>> Cc: 32012@debbugs.gnu.org
>> From: Andreas Röhler <andreas.roehler@online.de>
>> 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





  parent reply	other threads:[~2018-06-30 13:06 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
2018-06-30 11:42         ` Eli Zaretskii
2018-06-30 12:33           ` Andreas Röhler
2018-06-30 13:06           ` Andreas Röhler [this message]
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

  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=6ba1427b-a26c-609c-f356-e82a5161c581@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=32012@debbugs.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 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).