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 15:48:54 +0200 [thread overview]
Message-ID: <83edu7klrt.fsf@gnu.org> (raw)
In-Reply-To: <d64a53d1-75fa-e88e-7dba-03664ad3f46c@daniel-mendler.de> (message from Daniel Mendler on Sun, 13 Nov 2022 14:08:06 +0100)
> Date: Sun, 13 Nov 2022 14:08:06 +0100
> Cc: 59243@debbugs.gnu.org, dgutov@yandex.ru
> From: Daniel Mendler <mail@daniel-mendler.de>
>
> On 11/13/22 12:47, Eli Zaretskii wrote:
> > 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.
>
> My idea here would be to just replace the existing bitmaps with the ones
> proposed in bigger-fringe.el. They have the same width, but are a little
> bit higher.
They seem too large to me, but I wonder what do others think.
In any case, if we accept the bigger defaults, the built-in bitmaps in
fringe.c should be updated.
> Another alternative could be to provide an alternative larger fringe
> bitmap set which is used at larger resolution, if the
> left/right-fringe-width is larger than 8. Would you prefer that?
Yes, but the problem is how to do that automatically. I think people
have tried in the past but bumped into difficulties.
> If we indeed want to go the route to auto scale the bitmaps, then I
> would go the route via characters or via svg, since scaling the bitmaps
> will probably not give great results in contrast to hand-crafted bitmaps.
Probably. Indeed, supporting SVG icons on the fringes would be a
useful feature.
next prev parent reply other threads:[~2022-11-13 13:48 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
2022-11-13 13:08 ` Daniel Mendler
2022-11-13 13:48 ` Eli Zaretskii [this message]
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=83edu7klrt.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).