From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: 47937-done@debbugs.gnu.org
Subject: bug#47937: 27.1; Invisible text property updated only for a portion of buffer
Date: Thu, 22 Apr 2021 09:46:34 +0300 [thread overview]
Message-ID: <83mttqq0j9.fsf@gnu.org> (raw)
In-Reply-To: <DB9PR09MB498604DDFD00B987D14E484F96479@DB9PR09MB4986.eurprd09.prod.outlook.com> (message from Arthur Miller on Wed, 21 Apr 2021 22:10:45 +0200)
> From: Arthur Miller <arthur.miller@live.com>
> Cc: 47937@debbugs.gnu.org
> Date: Wed, 21 Apr 2021 22:10:45 +0200
>
> >> Because you have font-lock-mode turned on. And JIT font-lock begins
> >> by wiping out all the text properties.
> >
> > I should clarify this, I guess: this is specific to Org buffers, see
> > org-unfontify-region. And "all text properties" is an exaggeration:
> > it removes many properties, but not all of them.
>
> Allright, thank you for the excellent clarification. I guess I should go
> for custom visibility spec instead of plain invisible property, so that
> my text property survive font lock.
>
> Please close the bug and thanks.
I'm closing the bug, but I suggest to take this up with Org
developers, because I think org-unfontify-region removes too many
properties in a way that is too indiscriminate. They should ideally
only remove the properties they themselves add.
next prev parent reply other threads:[~2021-04-22 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 18:14 bug#47937: 27.1; Invisible text property updated only for a portion of buffer Arthur Miller
2021-04-21 18:29 ` Eli Zaretskii
2021-04-21 18:40 ` Arthur Miller
2021-04-21 19:02 ` Eli Zaretskii
2021-04-21 19:36 ` Eli Zaretskii
2021-04-21 20:10 ` Arthur Miller
2021-04-22 6:46 ` Eli Zaretskii [this message]
2021-04-21 22:43 ` bug#47937: [External] : " Drew Adams
2021-04-21 22:40 ` Drew Adams
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=83mttqq0j9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47937-done@debbugs.gnu.org \
--cc=arthur.miller@live.com \
/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).