all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bigger fringe bitmaps
Date: Thu, 17 Mar 2022 08:31:53 +0800	[thread overview]
Message-ID: <87h77xpgg6.fsf@yahoo.com> (raw)
In-Reply-To: <87sfrhu6et.fsf@wavexx.thregr.org> (Yuri D'Elia's message of "Wed, 16 Mar 2022 18:57:30 +0100")

Yuri D'Elia <wavexx@thregr.org> writes:

> I recently switched to a higher-resolution screen to basque in all the
> hidpi glory.
>
> And all is good. Pretty darn amazing for text rendering, in fact.
>
> Except for the fringe.
>
> Even at 16x16, these bitmaps are now indistinguishable from specks of
> dust. At least on lucid the bitmaps do not get upscaled by setting a
> larger fringe size.
>
> I suspect upscaling with nearest-neighbor would be a possibility for the
> moment, but it's the API surrounding the fixed bitmap sizes that doesn't
> look future-proof to me.

It should be reasonably future-proof, since we can always add
higher-resolution fringe bitmaps later.

Scaling of display elements (such as face boxes, tool-bar margins and
bitmaps, and fringes) is something I'm working on, but progress is
limited since I don't have any HiDPI hardware to test on.



  parent reply	other threads:[~2022-03-17  0:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 17:57 Bigger fringe bitmaps Yuri D'Elia
2022-03-16 18:23 ` Eli Zaretskii
2022-03-17  0:31 ` Po Lu [this message]
2022-03-17  7:43   ` Yuri D'Elia
2022-03-17  8:21     ` Eli Zaretskii
2022-03-17  8:34       ` Yuri D'Elia
2022-03-17  9:30         ` Eli Zaretskii
2022-03-17  9:44           ` Yuri D'Elia
2022-03-17 12:57             ` Eli Zaretskii
2022-03-17 21:21               ` Yuri D'Elia
2022-03-18  6:22                 ` Eli Zaretskii
2022-03-18  9:29                   ` Yuri D'Elia
2022-03-18 14:52                   ` [External] : " Drew Adams
2022-03-18 15:31                     ` tomas
2022-03-18 16:08                       ` Drew Adams
2022-03-18 17:19                         ` tomas
2022-03-18 23:14                         ` Po Lu

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=87h77xpgg6.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=wavexx@thregr.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 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.