From: Arthur Miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47937@debbugs.gnu.org
Subject: bug#47937: 27.1; Invisible text property updated only for a portion of buffer
Date: Wed, 21 Apr 2021 22:10:45 +0200 [thread overview]
Message-ID: <DB9PR09MB498604DDFD00B987D14E484F96479@DB9PR09MB4986.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <83o8e7pgzj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Apr 2021 22:36:32 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 21 Apr 2021 22:02:02 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: 47937@debbugs.gnu.org
>>
>> > From: Arthur Miller <arthur.miller@live.com>
>> > Cc: 47937@debbugs.gnu.org
>> > Date: Wed, 21 Apr 2021 20:40:31 +0200
>> >
>> > > They are not processed because there's no invisible property there.
>> >
>> > Why does it work on visible portion of the buffer, but not on the rest?
>>
>> 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.
next prev parent reply other threads:[~2021-04-21 20:10 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 [this message]
2021-04-22 6:46 ` Eli Zaretskii
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=DB9PR09MB498604DDFD00B987D14E484F96479@DB9PR09MB4986.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=47937@debbugs.gnu.org \
--cc=eliz@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).