From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yantar92@gmail.com, 57693@debbugs.gnu.org
Subject: bug#57693: 29.0.50; Is there a more reliable version of `char-displayable-p'?
Date: Sat, 18 Feb 2023 01:00:38 -0800 [thread overview]
Message-ID: <CADwFkm=veDinWeM8CGPOGjVAnekUPRs+pXyjCMEV5za2s5eYiQ@mail.gmail.com> (raw)
In-Reply-To: <83wn4fzcl5.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> That's for GUI displays only. And it's for strings, not characters.
> To test a single character, you don't need a separate function, IMO,
> you just need to use the test that is the core of that code.
[...]
> If you need to care for TTY frames, that problem has no known solution
> that works for all terminal emulators. So using fancy characters in
> general-purpose Emacs features is a problem that cannot be solved
> programmatically, or at least we don't currently know how to do that.
Thanks, those are useful clarifications. But could we not just fall
back to the replacement on TTY frames instead? Something like:
(defun insert-char-safely (ch repl)
"Insert character CH, if it can be displayed; otherwise insert REPL.
On TTY frames, always insert REPL."
(if (not (display-graphic-p))
(insert repl)
(insert ch)
(unless (font-at (1- (point)))
(delete-char -1)
(insert repl))))
next prev parent reply other threads:[~2023-02-18 9:00 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
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 [this message]
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
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='CADwFkm=veDinWeM8CGPOGjVAnekUPRs+pXyjCMEV5za2s5eYiQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=57693@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@gmail.com \
/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).