emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Daniel Ortmann <daniel.ortmann@oracle.com>,
	Stefan Kangas <stefan@marxist.se>
Cc: "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 07:31:20 +0800	[thread overview]
Message-ID: <87mtddhprr.fsf@localhost> (raw)
In-Reply-To: <80a8e4c8-87cf-245a-57a4-c77c19017507@oracle.com>

Daniel Ortmann <daniel.ortmann@oracle.com> writes:

> Ihor,
> What are your thoughts?
>
> On 7/12/22 15:03, Juan Manuel Macías wrote:
>> Juan Manuel Macías writes:
>>
>>> The most reasonable thing would be to use a more
>>> common symbol. But I'm still intrigued by the origin of that symbol...
>> It seems that the culprit is in line 1592 of org-agenda.el
>>
>> I think this should be considered a bug, since the glyph used (LEFTWARDS
>> TRIANGLE-HEADED ARROW / #2b60) is not present in most fonts.

The offending commit is 998a0aacd from Stefan.
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:

(defcustom org-agenda-current-time-string
  (if (and (display-graphic-p)
           (char-displayable-p ?⭠)
           (char-displayable-p ?─))
      "⭠ now ───────────────────────────────────────────────"
    "now - - - - - - - - - - - - - - - - - - - - - - - - -")
  "The string for the current time marker in the agenda."
  :group 'org-agenda-time-grid
  :version "29.1"
  :type 'string)

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.

Best,
Ihor


  reply	other threads:[~2022-07-12 23:31 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 [this message]
2022-07-13  0:26             ` Stefan Kangas
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87mtddhprr.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=daniel.ortmann@oracle.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    --cc=stefan@marxist.se \
    /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/org-mode.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).