From: Jon Fineman <jon@fineman.me>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: emacs 28.2 after upgrade lowercase s is broken
Date: Sun, 12 Mar 2023 17:13:03 -0400 [thread overview]
Message-ID: <87bkkx8yhs.fsf@ryzen.jonjfineman.com> (raw)
In-Reply-To: <83zg8it4i1.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Jon Fineman <jon@fineman.me>
>> Date: Sun, 12 Mar 2023 10:23:36 -0400
>>
>> On OpenBSD after I upgraded the OS and EMACS and updated my packages,
>> the lowercase s is now not displayed correctly. This is using X with
>> awesomewm.
>> > This is GNU Emacs 28.2 (build 1, x86_64-unknown-openbsd, GTK+ Version 3.24.37, cairo version 1.17.8)
>> > of 2023-03-10
>>
>> Only the lower curvy part of the s is sohwn. I.e. The complete upper
>> part is missing. If the s is bold is or highlighted appears.
>>
>> I can recreate this with launching emacs -q and typing s in the
>> scratch buffer. See attached. Also note the status line the s in Lisp.
>
> Note that s in bold is OK there.
>
>> Any thoughts on how to debug this?
>
> Try a different font?
Changing the fonts worked, thank you.
With the menu bar I explored a few different fonts and checked the use
system font and unchecked it.
Not that I necessarily want to undo what I did, I have no idea what I
changed. My init.el and custom-vars.el files were not updated.
The original font was:
name (opened by): -PfEd-DejaVu Sans Mono-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1
full name: DejaVu Sans Mono:pixelsize=13:foundry=PfEd:weight=normal:slant=normal:width=normal:spacing=100:scalable=true
file name: /usr/X11R6/lib/X11/fonts/TTF/DejaVuSansMono.ttf
size: 13
height: 17
baseline-offset: 0
relative-compose: 0
default-ascent: 0
ascent: 13
descent: 4
average-width: 8
space-width: 8
max-width: 8
prev parent reply other threads:[~2023-03-12 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 14:23 emacs 28.2 after upgrade lowercase s is broken Jon Fineman
2023-03-12 14:43 ` Eli Zaretskii
2023-03-12 21:13 ` Jon Fineman [this message]
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=87bkkx8yhs.fsf@ryzen.jonjfineman.com \
--to=jon@fineman.me \
--cc=eliz@gnu.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).