From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48740@debbugs.gnu.org
Subject: bug#48740: 28.0.50; Composition text property is not always honoured
Date: Tue, 01 Jun 2021 22:28:50 +0800 [thread overview]
Message-ID: <878s3tbqvx.fsf@localhost> (raw)
In-Reply-To: <835yyz2ctp.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Yet, the same "broken" property does work in step 6...
>
> No, AFAIU in step 6 a single property list covers the whole of the
> word ONGOING.
I feel that I am missing something then.
Stripping all unrelated properties from the plists, I get
At step 6 (after changing todo state from TODO to ONGOING):
For "ONG"
14 17 (... prettify-symbols-end 301 prettify-symbols-start 294 composition (0 7 [128119]) ...)
For "OING"
17 21 (... prettify-symbols-end 301 prettify-symbols-start 294 composition (0 7 [128119]) ...)
At step 8 (after org-agenda-redo-all):
For "ONG"
14 17 (... prettify-symbols-end 301 prettify-symbols-start 294 composition (0 7 [128119]) ...)
For "OING"
17 21 (... prettify-symbols-end 301 prettify-symbols-start 294 composition (0 7 [128119]) ...)
step 6 and step 8 look identical for me, yet step 6 does have
composition being rendered, unlike step 8.
>> The two intervals are there because other properties in the list are
>> not same, as I understand.
>
> Exactly. And that cannot work with the composition property.
Again, I feel that I miss something. Consider the following test case:
(switch-to-buffer "test")
(insert "asdasd")
(compose-region (point-min) (point-max) '(?a (bl . tl) ?| (bl . tl) ?b))
(put-text-property 1 3 'test 1)
(put-text-property 3 6 'test 2)
(buffer-string)
The output is
#("asdasd" 0 2 (composition (43 6 [97 72 124 72 98]) test 1) 2 5 (composition (43 6 [97 72 124 72 98]) test 2) 5 6 (composition (43 6 [97 72 124 72 98])))
Composition works fine here despite spanning over multiple intervals.
Again, I feel that I miss something in your explanation.
Best,
Ihor
next prev parent reply other threads:[~2021-06-01 14:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 7:35 bug#48740: 28.0.50; Composition text property is not always honoured Ihor Radchenko
2021-05-30 11:10 ` Eli Zaretskii
2021-05-30 13:08 ` Ihor Radchenko
2021-05-30 13:52 ` Eli Zaretskii
2021-05-30 15:13 ` Ihor Radchenko
2021-05-30 15:58 ` Eli Zaretskii
2021-05-31 13:00 ` Ihor Radchenko
2021-05-31 14:32 ` Eli Zaretskii
2021-06-01 14:28 ` Ihor Radchenko [this message]
2021-06-01 15:25 ` Eli Zaretskii
2021-06-01 16:25 ` Eli Zaretskii
2021-06-20 11:24 ` Ihor Radchenko
2021-06-20 11:53 ` Eli Zaretskii
2021-06-20 13:16 ` Ihor Radchenko
2021-06-21 12:18 ` Eli Zaretskii
2021-06-24 14:35 ` Ihor Radchenko
2021-06-24 16:06 ` Eli Zaretskii
2021-10-24 7:42 ` Stefan Kangas
2021-10-24 12:04 ` Eli Zaretskii
2021-10-24 12:27 ` Stefan Kangas
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=878s3tbqvx.fsf@localhost \
--to=yantar92@gmail.com \
--cc=48740@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).