From: Christoph Groth <christoph@grothesque.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 28: bitmap fonts, vector font character spacing
Date: Mon, 24 Jul 2023 17:28:52 +0200 [thread overview]
Message-ID: <871qgx72h7.fsf@drac> (raw)
In-Reply-To: 835y69s9st.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
Eli Zaretskii wrote:
> > From: Christoph Groth <christoph@grothesque.org>
> > Date: Mon, 24 Jul 2023 15:15:24 +0200
> >
> > I noticed the following entry in NEWS:
> >
> > > ** The Cairo graphics library is now used by default if present.
> > > '--with-cairo' is now the default, if the appropriate development
> > > files are found by 'configure'. Building with Cairo is known to
> > > cause some problems with bitmap fonts. This may require you to
> > > adjust your font settings, or to build with Xft support instead.
> >
> > Unfortunately, this is not very specific. Do “some problems” mean
> > that fonts like Terminus no longer work and that I have to recompile
> > Emacs if I want to use them, or is there some workaround? I tried
> > to find one, but so far without success.
>
> Basically, Cairo dropped support for bitmap fonts. So I'd expect them
> not to work at all in an Emacs built with Cairo.
Thanks for the quick clarification! Perhaps that NEWS entry could be
reformulated to be more categorical? “Some problems” sounded to me like
there could be ways to work around the problem, and I wasted too much
time trying to find one. (As strange as it sounds, after staring at
Terminus for a couple of hours on most days for many years I grew
attached to it...)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next reply other threads:[~2023-07-24 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 15:28 Christoph Groth [this message]
2023-07-24 15:37 ` Emacs 28: bitmap fonts, vector font character spacing Robert Pluim
2023-07-24 16:14 ` Eli Zaretskii
2023-08-10 11:28 ` Gregory Heytings
2023-08-10 14:53 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 11:12 Christoph Groth
2023-07-24 16:10 Christoph Groth
2023-07-24 16:29 ` PierGianLuca
2023-07-24 13:15 Christoph Groth
2023-07-24 13:45 ` Eli Zaretskii
2023-07-24 13:56 ` PierGianLuca
2023-07-24 14:41 ` Hongyi Zhao
2023-07-25 9:49 ` Manuel Giraud via Users list for the GNU Emacs text editor
2023-07-27 8:37 ` PierGianLuca
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=871qgx72h7.fsf@drac \
--to=christoph@grothesque.org \
--cc=help-gnu-emacs@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.
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).