From: Stefan Kangas <stefankangas@gmail.com>
To: Angelo Graziosi <angelo.g0@libero.it>, Eli Zaretskii <eliz@gnu.org>
Cc: info@protesilaos.com, emacs-devel@gnu.org
Subject: Re: Emacs master: different (ugly) font in org-mode [Windows, macOS]
Date: Wed, 6 Oct 2021 17:40:31 -0400 [thread overview]
Message-ID: <CADwFkm=bfT++VC=s6AdquHhHWFEEdA=FdSohO=t__zHJVLprLA@mail.gmail.com> (raw)
In-Reply-To: <1296031966.62064.1633554406095@mail1.libero.it>
Angelo Graziosi <angelo.g0@libero.it> writes:
> What Protesilaos suggested seems to work and it is what I will use on
> Windows and macOS.
It seems unfortunate if org-mode will suddenly come with a poorly
rendered font on a major platform, where IIUC we previously had
something that was at least okay.
Are the org-mode developers aware of this issue, and what do they have
to say about it?
next prev parent reply other threads:[~2021-10-06 21:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 21:40 Emacs master: different (ugly) font in org-mode Angelo Graziosi
2021-10-02 4:47 ` Protesilaos Stavrou
2021-10-02 9:08 ` Angelo Graziosi
2021-10-04 19:11 ` Emacs master: different (ugly) font in org-mode [Windows, macOS] Angelo Graziosi
2021-10-04 19:40 ` Protesilaos Stavrou
2021-10-05 11:47 ` Eli Zaretskii
2021-10-05 13:41 ` Angelo Graziosi
2021-10-05 15:46 ` Eli Zaretskii
2021-10-05 19:45 ` Angelo Graziosi
2021-10-06 11:48 ` Eli Zaretskii
2021-10-06 12:09 ` Protesilaos Stavrou
2021-10-06 21:06 ` Angelo Graziosi
2021-10-06 21:40 ` Stefan Kangas [this message]
2021-10-07 4:27 ` Protesilaos Stavrou
2021-10-07 4:57 ` Ihor Radchenko
2021-10-07 5:04 ` Protesilaos Stavrou
2021-10-07 5:24 ` Ihor Radchenko
2022-04-20 5:06 ` Ihor Radchenko
2022-04-20 6:12 ` Bastien
2021-10-07 7:32 ` Eli Zaretskii
2021-10-07 7:31 ` Eli Zaretskii
2021-10-07 7:05 ` Eli Zaretskii
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='CADwFkm=bfT++VC=s6AdquHhHWFEEdA=FdSohO=t__zHJVLprLA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=info@protesilaos.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).