unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 35230@debbugs.gnu.org
Subject: bug#35230: char-displayable-p return code is conflictingly documented
Date: Sun, 14 Apr 2019 17:10:14 +0300	[thread overview]
Message-ID: <83bm18k795.fsf@gnu.org> (raw)
In-Reply-To: <m2wojwdidz.fsf@gmail.com> (message from Robert Pluim on Sun, 14 Apr 2019 11:51:36 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: 35230@debbugs.gnu.org
> Date: Sun, 14 Apr 2019 11:51:36 +0200
> 
>  @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

Thanks.  I think we should tell more about the testing of text
terminal capabilities, because otherwise the reference to terminal
encoding comes out of the blue without being mentioned anywhere else,
since the preceding text talks only about fonts and fontsets,
i.e. only about GUI frames.





  reply	other threads:[~2019-04-14 14:10 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
2019-04-14 14:10     ` Eli Zaretskii [this message]
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=83bm18k795.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35230@debbugs.gnu.org \
    --cc=rpluim@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).