From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62780@debbugs.gnu.org
Subject: bug#62780: 30.0.50; Redisplay gets slow when using Org tables + show-trailing-whitespace
Date: Fri, 14 Apr 2023 12:28:25 +0000 [thread overview]
Message-ID: <87edommyvq.fsf@localhost> (raw)
In-Reply-To: <83pm86fz2e.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> But to test this idea, I need enough test cases that use the
> 'composition' property to make sure the property still works after I
> disable that call. Can you collect a few test cases which use the
> 'composition' property, with or without Org tables? I guess
> prettify-symbols-mode is one of them, but are there others? I will
> then try to find time to test this idea.
1. The most obvious is prettify-symbols-mode in Emacs sources
Say, (setq-local prettify-symbols-alist '(("!" . ?¬)) M-x
prettify-symbols-mode
2. https://github.com/integral-dw/org-superstar-mode
You can use tests/*.org example files
Also, https://github.com/jdtsmith/shakespeare.org has a giant example
Org file. And https://github.com/casouri/valign/blob/master/test.org
has a number of example tables (though the package itself does not
use composition).
3. Typing using TeX input method will produce composed glyphs. The same
if you set org-pretty-entities to t and then type \alpha, \beta, etc
in Org buffers.
4. Composing long spans of text might be a reasonable edge case to test.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-04-14 12:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 18:52 bug#62780: 30.0.50; Redisplay gets slow when using Org tables + show-trailing-whitespace Ihor Radchenko
2023-04-11 19:25 ` Eli Zaretskii
2023-04-11 19:41 ` Ihor Radchenko
2023-04-12 7:19 ` Eli Zaretskii
2023-04-12 7:39 ` Ihor Radchenko
2023-04-12 7:58 ` Eli Zaretskii
2023-04-13 9:46 ` Ihor Radchenko
2023-04-13 10:45 ` Eli Zaretskii
2023-04-13 11:15 ` Ihor Radchenko
2023-04-13 14:33 ` Eli Zaretskii
2023-04-14 9:20 ` Ihor Radchenko
2023-04-14 10:37 ` Eli Zaretskii
2023-04-14 11:36 ` Ihor Radchenko
2023-04-14 12:06 ` Eli Zaretskii
2023-04-14 12:23 ` Eli Zaretskii
2023-04-14 12:52 ` Ihor Radchenko
2023-04-14 13:51 ` Eli Zaretskii
2023-04-14 13:56 ` Ihor Radchenko
2023-04-14 14:47 ` Eli Zaretskii
2023-04-14 14:56 ` Ihor Radchenko
2023-04-14 15:06 ` Eli Zaretskii
2023-04-14 15:23 ` Ihor Radchenko
2023-04-14 12:28 ` Ihor Radchenko [this message]
2023-04-29 8:57 ` Eli Zaretskii
2023-04-29 18:03 ` Ihor Radchenko
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=87edommyvq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=62780@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).