unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 68849@debbugs.gnu.org, papadakis.k@yandex.com
Subject: bug#68849: 30.0.50; font-lock does not flush fontification after calling open-line
Date: Sat, 03 Feb 2024 11:55:27 +0200	[thread overview]
Message-ID: <864jep50ts.fsf@gnu.org> (raw)
In-Reply-To: <875xz9oep2.fsf@localhost> (message from Ihor Radchenko on Wed, 31 Jan 2024 12:44:09 +0000)

> Cc: Kostas Papadakis <papadakis.k@yandex.com>
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Wed, 31 Jan 2024 12:44:09 +0000
> 
> This bug was originally reported in
> https://orgmode.org/list/c5fb9f63-185c-4e36-b13f-e887a4a29aae@yandex.com
> 
> I am not 100% sure if is Emacs bug, but my preliminary testing showed
> anomalies in `jit-lock-after-change' -
> (put-text-property jit-lock-start jit-lock-end 'fontified nil) somehow
> did not apply the text properties. I suspect that I missed something
> though.
> 
> May someone please help debugging this and figuring out if the problem
> is on Emacs side?
> 
> Steps to reproduce:
> 
> 1. Create bug.el:
> (require 'org-faces)
> (set-face-underline 'org-block-end-line t)
> (setq org-fontify-whole-block-delimiter-line t)
> 
> 2. Create bug.org:
> #+begin_src
> #+end_src
> 
> asd
> 
> 3. Move point to the end of #+end_src line:
> #+end_src<point>
> 
> 4. M-x open-lien
> 
> 5. Observe underline face being applied to the empty line _after_
> #+end_src.

Stefan, any suggestions?





  reply	other threads:[~2024-02-03  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 12:44 bug#68849: 30.0.50; font-lock does not flush fontification after calling open-line Ihor Radchenko
2024-02-03  9:55 ` Eli Zaretskii [this message]
2024-02-03 18:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-04 13:33   ` Ihor Radchenko
2024-02-04 14:24     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=864jep50ts.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68849@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=papadakis.k@yandex.com \
    --cc=yantar92@posteo.net \
    /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).