From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57693@debbugs.gnu.org
Subject: bug#57693: 29.0.50; Is there a more reliable version of `char-displayable-p'?
Date: Sat, 10 Sep 2022 14:37:41 +0800 [thread overview]
Message-ID: <87y1urybt6.fsf@localhost> (raw)
In-Reply-To: <83czc3bvbg.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> However, it is not very clear for me how to determine programmatically if
>> given character is displayable in buffer.
>
> Make the char-displayable-p test at run time, I guess, i.e. when you
> are actually about to insert it.
This should indeed be slightly more accurate. However, it will still not
cover scenarios when, for example, an overlay at point has 'face
property that sets a font that is unable to display given char. Or do I
miss something?
--
Ihor Radchenko,
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:[~2022-09-10 6:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 13:25 bug#57693: 29.0.50; Is there a more reliable version of `char-displayable-p'? Ihor Radchenko
2022-09-09 13:38 ` Eli Zaretskii
2022-09-09 22:25 ` Stefan Kangas
2022-09-10 6:01 ` Eli Zaretskii
2022-09-10 6:06 ` Ihor Radchenko
2022-09-10 6:35 ` Eli Zaretskii
2022-09-10 6:44 ` Ihor Radchenko
2022-09-10 4:48 ` Ihor Radchenko
2022-09-10 6:24 ` Eli Zaretskii
2022-09-10 6:37 ` Ihor Radchenko [this message]
2022-09-10 7:56 ` Eli Zaretskii
2022-09-10 8:17 ` Ihor Radchenko
2022-09-10 8:42 ` Eli Zaretskii
2022-09-11 9:31 ` Ihor Radchenko
2022-09-11 9:43 ` Eli Zaretskii
2022-09-11 10:07 ` Eli Zaretskii
2022-09-12 5:46 ` Ihor Radchenko
2022-09-12 11:15 ` Eli Zaretskii
2022-09-13 1:44 ` Ihor Radchenko
2022-09-13 11:19 ` Eli Zaretskii
2022-09-14 1:52 ` Ihor Radchenko
2022-09-14 2:43 ` Eli Zaretskii
2023-02-17 19:18 ` Stefan Kangas
2023-02-17 19:29 ` Eli Zaretskii
2023-02-17 22:31 ` Stefan Kangas
2023-02-18 6:56 ` Eli Zaretskii
2023-02-18 9:00 ` Stefan Kangas
2023-02-18 9:18 ` Eli Zaretskii
2023-02-18 11:32 ` Ihor Radchenko
2023-02-18 11:56 ` Eli Zaretskii
2023-02-19 11:31 ` Ihor Radchenko
2023-02-19 11:55 ` Eli Zaretskii
2023-02-19 12:08 ` Ihor Radchenko
2023-02-19 12:23 ` Eli Zaretskii
2023-02-19 14:19 ` Ihor Radchenko
2023-02-19 15:02 ` Eli Zaretskii
2023-02-18 11:35 ` Ihor Radchenko
2023-02-18 12:00 ` Eli Zaretskii
2022-09-12 5:24 ` Ihor Radchenko
2022-09-09 13:46 ` Robert Pluim
2022-09-09 22:25 ` Stefan Kangas
2022-09-10 4:56 ` Ihor Radchenko
2022-09-10 6:02 ` Eli Zaretskii
2022-09-10 4:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1urybt6.fsf@localhost \
--to=yantar92@gmail.com \
--cc=57693@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.