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: Mon, 31 May 2021 21:00:29 +0800 [thread overview]
Message-ID: <87eedn12j6.fsf@localhost> (raw)
In-Reply-To: <83y2bw2oyr.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> No, it is also subdivided into two separate regions, each one of 3
> characters. And that's why it doesn't work: the display engine
> expects that the composed text should be covered by a single text
> property which specifies the length (7 - 0 = 7) that is equal to the
> length of the covered text (301 - 294 = 7).
>
> So the problem is caused by whatever code in org-agenda-redo-all that
> "breaks" the composition property into 2 separate adjacent properties.
Yet, the same "broken" property does work in step 6... And in both cases
the composition properties of the two regions are same. The two
intervals are there because other properties in the list are not same,
as I understand.
The only possibility I can think about is that compositions in the two
intervals are 'eq at step 6, but only 'equal at step 8. (How on Earth
can one debug this???)
Best,
Ihor
next prev parent reply other threads:[~2021-05-31 13:00 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 [this message]
2021-05-31 14:32 ` Eli Zaretskii
2021-06-01 14:28 ` Ihor Radchenko
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=87eedn12j6.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).