Naoya showed me workaround.
#+begin_src emacs-lisp
(when (equal emacs-major-version 27)
(with-eval-after-load "org-compat"
(defalias 'org-font-lock-ensure 'ignore)))
#+end_src
Now I switched from 26.3 to 27.1.
> Okay, your bisect scripts points to one of my commits.
>
> But I wish it was more automated. Because I tried quite
> hard and sometimes I _could_ reproduce the problem and
> sometimes I couldn't. So you could be seeing noise here.
> Maybe you can make your script do those copy-paste
> opera
Okay, your bisect scripts points to one of my commits.
But I wish it was more automated. Because I tried quite
hard and sometimes I _could_ reproduce the problem and
sometimes I couldn't. So you could be seeing noise here.
Maybe you can make your script do those copy-paste
operations automatica
Hi, I'm new on this thread, but I can reproduce tak's issue and I
tried to do bisect.
Finally, I got 5b45c269cda09fe46e110adb6f6767040f4ade59 is a
commit has a some problem.
I'm happy if this information could help you.
```
5b45c269cda09fe46e110adb6f6767040f4ade59
New jit-lock-antiblink-grace
>> > I'll keep looking a bit, but at this point it doesn't seem to have
>> > anything to do with the antiblink feature. I might be wrong, but I
>> > think that only shows up first in the messages buffer because it's
>> > unlucky enough to be one of the first users of syntax-ppss after a
>> > comma
On Sun, Dec 20, 2020 at 12:15 AM Tak Kunihiro wrote:
>
> > I'll keep looking a bit, but at this point it doesn't seem to have
> > anything to do with the antiblink feature. I might be wrong, but I
> > think that only shows up first in the messages buffer because it's
> > unlucky enough to be one
> I'll keep looking a bit, but at this point it doesn't seem to have
> anything to do with the antiblink feature. I might be wrong, but I
> think that only shows up first in the messages buffer because it's
> unlucky enough to be one of the first users of syntax-ppss after a
> command.
I confirme
> Tak Kunihiro, what is in your opinion the deciding character of these
> files? I.e. what did you change from the first file (where I couldn't
> reproduce) to the second?
The difference between the first and the second files is, the existence
of plain sentences after the second org-table.
I see
> I apologize that the file I posted is NG. Please try the following file
> as shown below.
Thanks, now I did reproduce... something. I get the "Marker does not
point anywhere" error you describe, but also mentions to other broken
functionality, not only the "antiblink":
Error in post-command-h
João Távora writes:
> I'll keep investigating: I still don't know which marker the message
> is referring to. It could be antiblink's marker, but it could be
> anything else.
>
> João
I've now reproduced after setting
(setq jit-lock-antiblink-grace nil)
Which turns off the antiblink feature
> From: João Távora
> Cc: Eli Zaretskii , 45...@debbugs.gnu.org,
> t...@misasa.okayama-u.ac.jp
> Date: Tue, 08 Dec 2020 17:02:13 +
>
> I'm quite lost as to why this happens, of course, but it seems it's
> always coming from syntax-ppss. When I evaluate that definition (rather
> than compi
11 matches
Mail list logo
