all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sun, 20 Jun 2021 19:24:55 +0800	[thread overview]
Message-ID: <87v968ok1k.fsf@localhost> (raw)
In-Reply-To: <83wnrdzjxe.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> Composition works fine here despite spanning over multiple intervals.
>> Again, I feel that I miss something in your explanation.
>
> We are mis-communicating.  You already stated correctly the reason for
> the problem:

Thanks for the clarification.

> I don't know why the values of the 'composition' property become not
> 'eq'; perhaps some code does a copy-sequence or something?  Presumably
> if you take a good look at what happens in org-agenda-redo-all and its
> subroutines, you will find that code.  In general, when you are
> dealing with static compositions, I'd suggest not to break the
> composed region into several separate intervals with different
> property lists: it's dangerous, as you see.

I debugged the agenda code and found the place where the breakage
happened:

(concat
		   (substring x 0 (match-end 1))
                   (unless (string-empty-p org-agenda-todo-keyword-format)
		     (format org-agenda-todo-keyword-format
			     (match-string 2 x)))
                   ;; Remove `display' property as the icon could leak
		   ;; on the white space.
		   (org-add-props " " (org-plist-delete (text-properties-at 0 x)
			 				'display))
                   (substring x (match-end 3)))

Magically, replacing concat with format appears to fix the issue.

However, I still have no clue what is going on there. I tried to
investigate further and examined the text properties of the composed
ONGOING keyword in inbox.org buffer. It turned out that the composition
is broken in the inbox.org itself:

#("* ONGOING" 0 1 (...) 2 5 (... composition (0 7 [128119]) prettify-symbols-start 3 prettify-symbols-end 10 face org-todo) 5 9 (... composition (0 7 [128119]) prettify-symbols-start 3 prettify-symbols-end 10 face org-todo))

Yet, the ONGOING string is correctly replaced by 👷 symbol in inbox.org.
The replacement does not work only in agenda, *and only when concat is
used to construct the keyword*. I am completely confused about what is
going on.

Do you have any ideas about this?

Best,
Ihor







  parent reply	other threads:[~2021-06-20 11:24 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
2021-06-01 15:25                 ` Eli Zaretskii
2021-06-01 16:25                   ` Eli Zaretskii
2021-06-20 11:24                   ` Ihor Radchenko [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v968ok1k.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.