From: Eli Zaretskii <eliz@gnu.org>
To: "André Silva" <andre.beat@gmail.com>
Cc: 52888@debbugs.gnu.org
Subject: bug#52888:
Date: Thu, 13 Jan 2022 21:49:04 +0200 [thread overview]
Message-ID: <83a6fz2z7z.fsf@gnu.org> (raw)
In-Reply-To: <CANfyKeD2-sP4tO0dH0rbjbyD+rR+ahiDgBn+Pnx89EG1iKqiYg@mail.gmail.com> (message from André Silva on Thu, 13 Jan 2022 18:20:20 +0000)
[Forwarding to the bug tracker. Please use Reply All.]
> From: André Silva <andre.beat@gmail.com>
> Date: Thu, 13 Jan 2022 18:20:20 +0000
>
> OK then maybe my expectations were wrong. My change restores the visual behavior I was seeing before
> these font attributes checks were introduced (but maybe it was wrong to begin with). It seems that now in
> certain places different font styles are being used (they seem to be thinner in some places although I'm not
> 100% sure whether it's the same font or not). The font I am using is JetBrains Mono. I am sorry for the
> noise, as the behavior changed I just assumed that this was buggy. Since I am not providing much
> information I understand that this is not entirely actionable right now so feel free to ignore it.
Thanks.
prev parent reply other threads:[~2022-01-13 19:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 5:28 bug#52888: 29.0.50; font_{delete_unmatched,score} do not handle nil FONT_WEIGHT_INDEX Sean Whitton
2021-12-30 7:33 ` Eli Zaretskii
2021-12-30 17:13 ` Sean Whitton
2021-12-30 18:39 ` Eli Zaretskii
2022-01-01 0:30 ` Sean Whitton
2022-01-01 2:35 ` Sean Whitton
2022-01-01 7:15 ` Eli Zaretskii
2022-01-01 22:31 ` Sean Whitton
2022-01-03 2:04 ` Sean Whitton
2022-01-05 2:10 ` Sean Whitton
2022-01-05 12:37 ` Eli Zaretskii
2022-01-05 13:55 ` Robert Pluim
2022-01-05 14:08 ` Eli Zaretskii
2022-01-06 5:41 ` Sean Whitton
2022-01-06 12:29 ` Eli Zaretskii
2022-01-06 18:10 ` Sean Whitton
2022-01-12 14:56 ` Eli Zaretskii
2022-01-12 21:41 ` Sean Whitton
2022-01-13 6:52 ` Eli Zaretskii
2022-01-01 6:56 ` Eli Zaretskii
2022-01-01 21:49 ` Can't set conditional break point using AREF/NILP Sean Whitton
2022-01-02 6:42 ` Eli Zaretskii
2022-01-02 22:38 ` Sean Whitton
2022-01-03 12:28 ` Eli Zaretskii
2022-01-04 21:57 ` Sean Whitton
2022-01-05 12:11 ` Eli Zaretskii
2022-01-06 18:20 ` bug#53058: etc/DEBUG could say more about --enable-check-lisp-object-type Sean Whitton
2022-01-06 20:11 ` Eli Zaretskii
2022-01-06 23:46 ` Sean Whitton
2022-01-07 6:58 ` Eli Zaretskii
2022-01-07 20:41 ` Sean Whitton
2022-01-08 6:55 ` Eli Zaretskii
2022-02-03 0:19 ` Sean Whitton
2022-02-03 7:28 ` Eli Zaretskii
2022-01-13 11:54 ` bug#52888: André Silva
2022-01-13 16:40 ` bug#52888: Eli Zaretskii
[not found] ` <CANfyKeBjec0z2c33Fph1=ESr-4ACH0BNKXq_wW-Vtr6sEfJ_VA@mail.gmail.com>
2022-01-13 18:13 ` bug#52888: Eli Zaretskii
[not found] ` <CANfyKeD2-sP4tO0dH0rbjbyD+rR+ahiDgBn+Pnx89EG1iKqiYg@mail.gmail.com>
2022-01-13 19:49 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6fz2z7z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52888@debbugs.gnu.org \
--cc=andre.beat@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.