emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "Daniel Ortmann" <daniel.ortmann@oracle.com>,
	"Juan Manuel Macías" <maciaschain@posteo.net>,
	orgmode <emacs-orgmode@gnu.org>
Subject: Re: [External] : Re: missing a character / font in agenda?
Date: Wed, 13 Jul 2022 02:26:45 +0200	[thread overview]
Message-ID: <CADwFkmn2U+AJmbxkPLcP-sf+a9V24JwfyY_=mjYi1OYwgKja-A@mail.gmail.com> (raw)
In-Reply-To: <87mtddhprr.fsf@localhost>

Ihor Radchenko <yantar92@gmail.com> writes:

>>> I think this should be considered a bug, since the glyph used (LEFTWARDS
>>> TRIANGLE-HEADED ARROW / #2b60) is not present in most fonts.

If that is true (I don't know) then maybe we should just use a more
ubiquitous glyph?

> The commit is supposed to fall back to ASCII symbol if the Unicode
> variant is not available, but apparently the check failed for some
> reason:
> Stefan, do you have any idea what can go wrong here?
> The only thing I can think about is warning in the char-displayable-p
> docstring:
> >> On a multi-font display, the test is only whether there is an
> >> appropriate font from the selected frame's fontset to display
> >> CHAR's charset in general.  Since fonts may be specified on a
> >> per-character basis, this may not be accurate.

I don't think we specify a particular font here, do we?  So it seems
like there might be a bug in Emacs here?  I'm not an expert on this
stuff by any means, but I would probably 'M-x report-emacs-bug' to
find out why 'char-displayable-p' would say that a character is
displayable when it's not.

  reply	other threads:[~2022-07-13  0:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 17:18 missing a character / font in agenda? Daniel Ortmann
2022-07-12 17:58 ` Juan Manuel Macías
2022-07-12 18:45   ` [External] : " Daniel Ortmann
2022-07-12 19:52     ` Juan Manuel Macías
2022-07-12 20:03       ` Juan Manuel Macías
2022-07-12 23:04         ` Daniel Ortmann
2022-07-12 23:31           ` Ihor Radchenko
2022-07-13  0:26             ` Stefan Kangas [this message]
2022-07-13 10:01               ` Juan Manuel Macías
2022-07-17  8:58                 ` Ihor Radchenko
2022-07-19  2:11                   ` Max Nikulin
2022-07-13 10:13               ` Max Nikulin
2022-08-05  6:15                 ` Ihor Radchenko
2022-08-05 15:09                   ` Max Nikulin
2022-08-06  8:17                     ` Ihor Radchenko
2022-07-13  8:37     ` Greg Minshall
2022-07-16  9:15 ` Ihor Radchenko
2022-07-18 22:07   ` [External] : " Daniel Ortmann

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmn2U+AJmbxkPLcP-sf+a9V24JwfyY_=mjYi1OYwgKja-A@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=daniel.ortmann@oracle.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    --cc=yantar92@gmail.com \


* 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


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).