21–30 of 192 posts
I have a 2013 Chrome Pixel, with 240 dpi, and I’ve also found that the Xft.dpi setting takes care of nearly everything, although there are some interface elements in some applications that still display tiny type. The author seems to be suggesting that 163 DPI is high resolution; is it commonly understood to be so? Because that would look a bit fuzzy to me.
I have a 2013 Chrome Pixel, with 240 dpi, and I’ve also found that the Xft.dpi setting takes care of nearly everything, although there are some interface elements in some applications that still display tiny type. The author seems to be suggesting that 163 DPI is high resolution; is it commonly understood to be so? Because that would look a bit fuzzy to me.
Every screen’s density of pixels are different.
This article makes it seem like these steps are necessary for most Linux setups, when in reality you can do per monitor fractional scaling from a GUI as long as you're using GNOME on Wayland. No need to fiddle with per app settings, it works transparently.
Except the author is using X11 as many people will. And what this shows is how many different environments / toolkits / settings there are out there. It would be nice if distributions would do a better job of handling this for you. I’ve run into the same issues myself, and it’s kind of hard to believe that I even had to figure out these configuration dpi settings in 2021.
The author brought up mouse acceleration, which reminded me of why I switched back from Linux to a Mac: the mouse curves were terrible IMHO, with seemingly no way to change it. The parameters you can tweak in X11 didn’t let me change the fundamental curve, and to me where so much worse than Apple’s it rendered the system frustrating to use. I don’t know if wayland suffers from the same issue or not, but certainly goo…
If you, like me, are blind as a bat may I recommend `Xcursor.size` as well.
Anyone know how to get mouse cursor comet trails in Linux?
Xresources:
Xft.dpi:120
st.font: monospace:size=14
# haven't had time to dig into this, some systems need
# DPI set twice
xSetDpi () { xrandr --dpi "$1"; xrandr --dpi "$1"; }
emacs.d/init.el:
(set-face-attribute 'default nil :height xxx)
qutebrowser/config.py:
# even with DPI set, I typically find web text too small
c.zoom.default = '175%'
I value having a system that is configured exactly to my preferences. I recognize that having multiple configs is a turnoff for some. I can't debate personal preference.
I have spent much more time trying to get something like Gnome to behave in a way I want than I have on all of my current config. XFCE is a pretty good experience for a DE and configuring scaling through system settings.
Machines:
1. 11" HD, OpenBSD current
2. 12" FHD, Artix Linux
3. 2x27" WQHD, Artix Linux
Earlier quoted context omitted.
Every screen’s density of pixels are different.
No, I once saw two that were the same.
Earlier quoted context omitted.
No, I once saw two that were the same.
This is not true. Your pixel density is a function of your resolution and dimensions. “HiDPI” is a nebulous term that refers to high resolution screens that are also relatively small.
And what is “not true”?
Not related to HiDPI, but looking at the picture of his monitor setup: From an ergonomics standpoint (i.e. the health of your neck), the upper edge of your monitor shouldn't be higher than your eye level. Looking straight or looking down is fine. Thus the monitor on the left is probably not very ergonomic.
Then I realized: I spend most of my time staring at the bottom half, to bottom edge, of the screen. Typing in a terminal, adding functions at the bottom of a file, etc. I moved my monitor such that my eyes are almost dead-center, vertically, and haven't had any issues since, neither neck nor shoulders. I kept the improved posture too, so I'm sure that ultimately helped too.
I'm sure the recommended is recommended for a reason, and works for most, but hopefully my experience is useful to some.