From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 59243@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#59243: 28.2.50; Larger Fringe Bitmaps
Date: Sun, 13 Nov 2022 13:47:46 +0200 [thread overview]
Message-ID: <83k03zkrdp.fsf@gnu.org> (raw)
In-Reply-To: <9fc85987-cc78-2f9b-60e1-b893dbe9b848@daniel-mendler.de> (message from Daniel Mendler on Sun, 13 Nov 2022 11:08:19 +0100)
> Cc: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 13 Nov 2022 11:08:19 +0100
> From: Daniel Mendler <mail@daniel-mendler.de>
>
> on Emacs 28, when using large screens, I find the fringe bitmaps
> barely recognizable. I've seen there has been a previous discussion
> about using characters for the fringe, such that we get scaling, but
> this seems to be a longer term effort.
>
> For now if we want to stick to bitmaps of width 8, we could still do
> a bit better by using thicker lines, by using the space more
> completely and by increasing the height of the bitmaps slightly.
>
> Please consider the fringe bitmaps I've defined in bigger-fringe.el.
> This is a cheap change which nevertheless should increase
> accessibility a little bit. I override the bitmaps defined in
> fringe.c, flymake.el, diff.el and diff-hl.el. The file
> bigger-fringe.el contains the command `fringe-bitmap-test', which
> I've used to create a screenshot of the updated fringe bitmaps. I've
> attached the screenshot for comparison.
Thanks, but is the intent of bigger-fringe.el to have the user load it
manually? If so, this is sub-optimal: Emacs should switch to larger
fringe bitmaps automatically based on the screen DPI, or perhaps scale
them.
next prev parent reply other threads:[~2022-11-13 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 10:08 bug#59243: 28.2.50; Larger Fringe Bitmaps Daniel Mendler
2022-11-13 11:47 ` Eli Zaretskii [this message]
2022-11-13 13:08 ` Daniel Mendler
2022-11-13 13:48 ` Eli Zaretskii
2022-11-13 17:49 ` Juri Linkov
2022-11-13 18:17 ` 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=83k03zkrdp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59243@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mail@daniel-mendler.de \
/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).