aboutsummaryrefslogtreecommitdiff
path: root/src/cmd/tbl/mkfile
diff options
context:
space:
mode:
authorGabriel Díaz <gdiaz@qswarm.com>2018-11-14 06:19:29 +0100
committerRuss Cox <rsc@golang.org>2018-11-14 00:19:29 -0500
commit000c1a3b19a8d3f8bbaefba84131995cb62c889f (patch)
treea6dfaa9747977a7c9bb574cedb3b8e39c6335a2a /src/cmd/tbl/mkfile
parenta791787a384745b90fa0eb704cd9cbbe8c758684 (diff)
downloadplan9port-000c1a3b19a8d3f8bbaefba84131995cb62c889f.tar.gz
plan9port-000c1a3b19a8d3f8bbaefba84131995cb62c889f.tar.bz2
plan9port-000c1a3b19a8d3f8bbaefba84131995cb62c889f.zip
devdraw: set displaydpi on devdraw x11 attach (#178)
See https://plan9port-review.googlesource.com/c/plan9/+/1470 for discussion of the approach, especially Michael Stapleberg's comment: Note that chromium, firefox and others have tried this and then switched to using the Xft.dpi X resource, see e.g. https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/ui/libgtk2ui/gtk2_ui.cc and especially http://sources.debian.net/src/gnome-settings-daemon/3.18.2-1/plugins/xsettings/gsd-xsettings-manager.c/?hl=824#L80 for some anecdata about why this approach doesn’t work out. The Xft.dpi resource is being set accurately by desktop environments (GNOME, KDE, …) and can easily be changed by users of niche window managers by editing ~/.Xresources. I suggest we check only Xft.dpi, without considering the DPI environment variable or the monitor width/height.
Diffstat (limited to 'src/cmd/tbl/mkfile')
0 files changed, 0 insertions, 0 deletions