From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [External] : Re: missing a character / font in agenda?
Date: Fri, 5 Aug 2022 22:09:52 +0700 [thread overview]
Message-ID: <tcjbs1$kdg$1@ciao.gmane.io> (raw)
In-Reply-To: <87r11vnrlp.fsf@localhost>
On 05/08/2022 13:15, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> DejaVuSansMono has at least
>> - "\u{21fd}" "⇽" LEFTWARDS OPEN-HEADED ARROW
>> https://util.unicode.org/UnicodeJsps/character.jsp?a=21fd
>> - "\u{2190}" "←" LEFTWARDS ARROW
>> https://util.unicode.org/UnicodeJsps/character.jsp?a=2190
>> from https://en.wikipedia.org/wiki/Arrows_(Unicode_block)
>
> "⇽" looks better on my system. However, I do not see "⇽" LEFTWARDS
> OPEN-HEADED ARROW in Liberation Fonts used by default in Emacs on my
> system. Though I only tested using emacs -Q + M-x describe-char
You are right. Courier New is immortal and fonts created to be
metric-compatible with it will outlive this font. I forgot about such
compatibility test.
Another approach would be assuming reasonable set of modern fonts and
providing some defcustom to switch to legacy compatibility mode.
next prev parent reply other threads:[~2022-08-05 15:10 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 [this message]
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='tcjbs1$kdg$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/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).