From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35230@debbugs.gnu.org
Subject: bug#35230: char-displayable-p return code is conflictingly documented
Date: Sun, 14 Apr 2019 11:51:36 +0200 [thread overview]
Message-ID: <m2wojwdidz.fsf@gmail.com> (raw)
In-Reply-To: <837ebzmlnf.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Apr 2019 15:51:48 +0300")
>>>>> On Fri, 12 Apr 2019 15:51:48 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com> Date: Thu, 11 Apr 2019
>> 16:49:29 +0200
>>
>> (This comes as a result of the stackexchange question at
>> https://emacs.stackexchange.com/questions/48810)
>>
>> char-displayable-p docstring says
>>
>> Return non-nil if we should be able to display CHAR.
>>
>> The elisp manual says something subtly different:
>>
>> This function returns ‘t’ if Emacs ought to be able to display
>> CHAR. More precisely, if the selected frame’s fontset has a
>> font to display the character set that CHAR belongs to.
>>
>> The function itself is more in line with the docstring:
Eli> Yes, the manual is wrong and should be fixed. Non-nil is
Eli> exactly right, and callers should not depend on any finer
Eli> definition of the return value, as it could be many different
Eli> non-nil objects.
That I can do easily enough in emacs-26
>> (char-displayable-p #xE01EF) => unicode
>>
>> since I donʼt have a font with a glyph for that character, so
>> it ends up displayed as a box with the unicode code point
>> inside it. The code that results in 'unicode has the comment
>>
>> ;; On a text terminal without glyph codes, CHAR is displayable
>> ;; if the coding system for the terminal can encode it.
>>
>> but Iʼm very much on a graphical terminal here, not a text
>> terminal.
Eli> This is a (known) deficiency in char-displayable-p, but one
Eli> which is not easy to fix: no one says that every call to this
Eli> function asks about the selected frame, so we cannot
Eli> unconditionally disable the TTY branch when on GUI frames.
Eli> Perhaps an optional argument could be added for that purpose,
Eli> which is the frame for which to make the test. At least
Eli> some, if not most, of the calls will still need to omit that
Eli> argument, though, because we currently need to know that up
Eli> front to set up the quote-style, for example.
Eli> Perhaps mentioning this caveat in the manual would be good.
Iʼve made an attempt below. Do we want a cross reference to 'Glyphless
Chars' as well?
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index b07999432c..fac883ae16 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -3507,12 +3507,16 @@ Fontsets
@end defun
@defun char-displayable-p char
-This function returns @code{t} if Emacs ought to be able to display
-@var{char}. More precisely, if the selected frame's fontset has a
-font to display the character set that @var{char} belongs to.
+This function returns non-@code{nil} if Emacs ought to be able to
+display @var{char}. More precisely, if the selected frame's fontset
+has a font to display the character set that @var{char} belongs to.
Fontsets can specify a font on a per-character basis; when the fontset
does that, this function's value may not be accurate.
+
+This function may return non-@code{nil} even when there is no font
+available, since it also checks if the coding system for the text
+terminal can encode the character.
@end defun
@node Low-Level Font
next prev parent reply other threads:[~2019-04-14 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 14:49 bug#35230: char-displayable-p return code is conflictingly documented Robert Pluim
2019-04-12 12:51 ` Eli Zaretskii
2019-04-14 9:51 ` Robert Pluim [this message]
2019-04-14 14:10 ` Eli Zaretskii
2020-08-21 15:09 ` Lars Ingebrigtsen
2020-10-11 1:50 ` Lars Ingebrigtsen
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=m2wojwdidz.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=35230@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).