From: Samuel Kyletoft <samuel@kyletoft.se>
To: Po Lu <luangruo@yahoo.com>
Cc: 68467@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#68467: 29.1; Fringe fonts + hidpi
Date: Mon, 22 Jan 2024 14:28:47 +0100 [thread overview]
Message-ID: <CA+srmogu24VKF0VDmcAZcx6r31n9u5XsWV8ePxT5A5Sb-Dg1Fg@mail.gmail.com> (raw)
In-Reply-To: <877ck4uwm0.fsf@yahoo.com>
I had a very vim-mindset when writing the initial report and didn't
even consider that it could be an image rather than a character
in a custom font. But yes, I guess I do mean the bitmaps. But setting
`(set-face-attribute 'fringe nil :font "Cascadia Code" :height 220)`
will scale it correctly, so it can scale it if set explicitly, it just won't
do it automatically.
On Sat, 20 Jan 2024 at 11:29, Po Lu <luangruo@yahoo.com> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Samuel Kyletoft <samuel@kyletoft.se>
> >> Date: Mon, 15 Jan 2024 06:49:56 +0100
> >>
> >> I use Emacs at 200% on xwayland in GNOME. Most things respect the 200%
> >> scaling without any configuration, but not the fringe font. See
> >> attached screenshots at 100% and 200% scale.
> >> To reproduce: Open Emacs on a 200% monitor, use any package that
> >> annotates the fringe.
> >
> > Po Lu, any suggestions?
> >
> > Thanks.
>
> What is the "fringe font" in this context? If by that you (Samuel) mean
> the size of individual fringe bitmaps, then the reason it cannot scale
> is that the code for magnifying fringe bitmaps by the display scale
> factor has yet to be written. PGTK and NS builds are unaffected by this
> deficiency because the toolkit assumes responsibility for doing so.
>
> Thanks.
next prev parent reply other threads:[~2024-01-22 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 5:49 bug#68467: 29.1; Fringe fonts + hidpi Samuel Kyletoft
2024-01-20 9:38 ` Eli Zaretskii
2024-01-20 10:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-22 13:28 ` Samuel Kyletoft [this message]
2024-01-22 13:29 ` Samuel Kyletoft
2024-01-22 14:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CA+srmogu24VKF0VDmcAZcx6r31n9u5XsWV8ePxT5A5Sb-Dg1Fg@mail.gmail.com \
--to=samuel@kyletoft.se \
--cc=68467@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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).