From: Carlos Pita <carlosjosepita@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Robert Pluim <rpluim@gmail.com>, 37689@debbugs.gnu.org
Subject: bug#37689: Fringe pixmaps, widgets, etc. look ridiculously tiny in hidpi screen
Date: Sun, 20 Oct 2019 16:17:56 -0300 [thread overview]
Message-ID: <CAELgYhf7DXJN-+92m0cb_Pbq9fmoow=yF9hCV-0wTPpYfZxZMA@mail.gmail.com> (raw)
In-Reply-To: <87zhhvgsgf.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
>
>
> Maybe the value of 'fringe-indicator-alist' should be frame-local?
>
Frames can be moved from one display to another with a different dpi.
> >> Funnily enough, the current fringe bitmaps are too big for me,
> >
> > Too big as in "twice as big as expected" or in "too big for my taste"?
>
> I use a small 10px font, so the customized bitmaps fit the font size.
>
Ah ok, great, so that's not a scale factor issue.
So maybe fridge bitmap size should depend on the font size, not scale?
>
10px fonts are not 10px at other scale factor than 1x. In general you don't
have to change the size of your fonts when duplicating your screen
resolution, even if your fonts were given in px size, because the toolkit
scales them for you under the assumption of some standard ~96dpi base which
allows pixels to be treated as something more than a "number of tiny dots,
whatever their size is" measure.
What can be done is to adjust everything else in emacs to the effective
(not nominal) pixel size of the default face (then scale factor would be
the effective to nominal pixel size ratio of this font). I believe
something like that is done in some places, it's sensible given that emacs
is mostly a grid of characters. But anyway this is clearly not the approach
taken for the fringe and some parts of emacs have geometry not so tightly
coupled to font size, although I would indeed expect high correlation. And
some toolkits (for example, gtk) offer a separate scale factor for font
size, which is then applied on top of the general scale factor and seen
mostly as an accessibility feature.
>
[-- Attachment #2: Type: text/html, Size: 2789 bytes --]
next prev parent reply other threads:[~2019-10-20 19:17 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAELgYhf7DXJN-+92m0cb_Pbq9fmoow=yF9hCV-0wTPpYfZxZMA@mail.gmail.com' \
--to=carlosjosepita@gmail.com \
--cc=37689@debbugs.gnu.org \
--cc=juri@linkov.net \
--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 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.