unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Mendler <mail@daniel-mendler.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59243@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#59243: 28.2.50; Larger Fringe Bitmaps
Date: Sun, 13 Nov 2022 14:08:06 +0100	[thread overview]
Message-ID: <d64a53d1-75fa-e88e-7dba-03664ad3f46c@daniel-mendler.de> (raw)
In-Reply-To: <83k03zkrdp.fsf@gnu.org>

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. This way they work better with bigger screens and larger
font sizes while still retaining the thin fringe width. The downside is
that the bitmaps look more compressed horizontally - there is less
breathing space to the text right next to the fringe.

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?

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.

Daniel





  reply	other threads:[~2022-11-13 13:08 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 [this message]
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=d64a53d1-75fa-e88e-7dba-03664ad3f46c@daniel-mendler.de \
    --to=mail@daniel-mendler.de \
    --cc=59243@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@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.
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).