From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [External] : Re: missing a character / font in agenda?
Date: Sat, 06 Aug 2022 16:17:20 +0800 [thread overview]
Message-ID: <87y1w1lran.fsf@localhost> (raw)
In-Reply-To: <tcjbs1$kdg$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
> Another approach would be assuming reasonable set of modern fonts and
> providing some defcustom to switch to legacy compatibility mode.
This whole thread is about a single defcustom already.
I do not see much point providing yet another defcustom on top.
`char-displayable-p' check should be good enough in most cases, except
some strange font mapping settings. In the latter cases, users can
always customize org-agenda-current-time-string manually.
Ideally, we need to find a more reliable alternative to
`char-displayable-p'.
Best,
Ihor
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-08-06 8:17 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
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 [this message]
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=87y1w1lran.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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/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).