From: Carlos Pita <carlosjosepita@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Third <alan@idiocy.org>, Robert Pluim <rpluim@gmail.com>,
37689@debbugs.gnu.org
Subject: bug#37689: Fringe pixmaps, widgets, etc. look ridiculously tiny in hidpi screen
Date: Mon, 14 Oct 2019 12:06:45 -0300 [thread overview]
Message-ID: <CAELgYhdGGboMLg0-ooTQX3XtyB-4wT-S4jGQHVp8ZQx00i9KWw@mail.gmail.com> (raw)
In-Reply-To: <83pnizidi3.fsf@gnu.org>
> Maybe I'm confused: I thought we were talking about fringe bitmaps.
> But you seem to be talking about a more general issue. I'm not sure
Yes, remember how all this started:
> make an inventory of all the things that should be fixed towards hidpi
Above I've been mostly talking about two things: i. fringe bitmaps and
ii. widgets (checkbox-like stuff). My main interest is in (i) since
I'm ok with text-only widgets but there is no replacement for fringe
bitmaps. Anyway, I would like to fix both things at the same time.
Moreover, there are other problems, which might be addressed by the
same changes or not, take for example tetris, which looks laughably
small in my screen.
So I could go and change get_fringe_bitmap_data and hopefully fix the
fringe issue but:
i. This won't fix any other hidpi issues.
ii. This might introduce regressions in backends that I'm unable to
test (windows, macos) because they might be doing the scaling
themselves.
Therefore I believe a more nuanced understanding of how emacs is
approaching the matter, if there is any strategy at all, is in order.
next prev parent reply other threads:[~2019-10-14 15:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 6:28 bug#37689: Fringe pixmaps, widgets, etc. look ridiculously tiny in hidpi screen Carlos Pita
2019-10-10 8:12 ` Eli Zaretskii
2019-10-10 13:26 ` Robert Pluim
2019-10-10 13:37 ` Carlos Pita
2019-10-10 13:47 ` Robert Pluim
2019-10-10 13:36 ` Carlos Pita
2019-10-10 14:21 ` Robert Pluim
2019-10-10 14:33 ` Carlos Pita
2019-10-10 14:37 ` Carlos Pita
2019-10-10 15:06 ` Eli Zaretskii
2019-10-10 15:43 ` Carlos Pita
2019-10-10 15:05 ` Eli Zaretskii
2019-10-10 15:51 ` Carlos Pita
2019-10-10 16:01 ` Carlos Pita
2019-10-10 17:35 ` Eli Zaretskii
2019-10-10 17:39 ` Carlos Pita
2019-10-11 3:26 ` Carlos Pita
2019-10-11 3:48 ` Carlos Pita
2019-10-12 0:51 ` Carlos Pita
2019-10-12 7:28 ` Eli Zaretskii
2019-10-12 7:56 ` Carlos Pita
2019-10-12 8:26 ` Carlos Pita
2019-10-14 0:40 ` Carlos Pita
2019-10-14 8:33 ` Eli Zaretskii
2019-10-14 13:19 ` Alan Third
2019-10-14 14:00 ` Eli Zaretskii
2019-10-17 11:48 ` Alan Third
2019-10-14 14:37 ` Carlos Pita
2019-10-14 14:54 ` Eli Zaretskii
2019-10-14 15:06 ` Carlos Pita [this message]
2019-10-14 15:15 ` Eli Zaretskii
2019-10-14 15:32 ` Carlos Pita
2019-10-14 16:52 ` Eli Zaretskii
2019-10-14 19:59 ` Carlos Pita
2019-10-14 23:42 ` Carlos Pita
2019-10-14 23:49 ` Carlos Pita
2019-10-15 1:50 ` Carlos Pita
2019-10-15 9:30 ` Eli Zaretskii
2019-10-15 23:01 ` Carlos Pita
2019-10-16 4:25 ` Carlos Pita
2019-10-16 9:16 ` martin rudalics
2019-10-16 16:31 ` Carlos Pita
2019-10-16 16:40 ` Carlos Pita
2019-10-16 19:01 ` Carlos Pita
2019-10-17 8:13 ` Robert Pluim
2019-10-15 9:27 ` Eli Zaretskii
2019-10-20 16:03 ` Juri Linkov
2019-10-20 17:37 ` Carlos Pita
2019-10-20 18:52 ` Juri Linkov
2019-10-20 19:17 ` Carlos Pita
2019-10-24 17:09 ` Carlos Pita
2019-10-26 10:45 ` 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=CAELgYhdGGboMLg0-ooTQX3XtyB-4wT-S4jGQHVp8ZQx00i9KWw@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--cc=37689@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.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).