Git-Mirrors/Qubes-Community-Content
1
0
Fork 0
mirror of https://github.com/Qubes-Community/Contents.git synced 2025-01-25 05:46:48 -05:00
Code Issues Packages Projects Releases Wiki Activity

various fixes

Browse Source
This commit is contained in:
taradiddles 2018-04-15 08:12:22 +03:00
parent 9401efe5d2
commit c554cd2aef
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/customization/dpi-scaling.md
View File

@ -16,7 +16,7 @@ The simplest way to set dpi scaling in dom0 is to use the desktop environment's
VMs VMs
--- ---
We'll make use of the `Xft.dpi` [X resource](https://en.wikipedia.org/wiki/X_resources) in VMs. Most (all ?) toolkits and applications honor it so it is the prefered way to set dpi scaling instead of using toolkit-specific features. We'll make use of the `Xft.dpi` [X resource](https://en.wikipedia.org/wiki/X_resources) in VMs. Most toolkits and applications honor it so it is the prefered way to set dpi scaling instead of using toolkit-specific features.
Get the current value of `Xft.dpi`: Get the current value of `Xft.dpi`:
@ -24,18 +24,19 @@ Get the current value of `Xft.dpi`:
xrdb -query | grep Xft.dpi xrdb -query | grep Xft.dpi
~~~ ~~~
Test with a different dpi value: in a terminal issue the following command and then start an application to check that the menus/fonts' size is increased/decreased (replace '144' accordingly with a number that is a multiple of 6, or even 12, as numbers that aren't sometimes result in annoying rounding errors that cause adjacent bitmap font sizes to not increment and decrement linearly): Test with a different dpi value: in a terminal issue the following command and then start an application to check that the menus/fonts' size is increased/decreased (replace '144' accordingly with a number that is a multiple of 6 as numbers that aren't sometimes result in annoying rounding errors that cause adjacent bitmap font sizes to not increment and decrement linearly):
~~~ ~~~
echo Xft.dpi: 144 | xrdb -merge echo Xft.dpi: 144 | xrdb -merge
~~~ ~~~
Once you found a value that fits your setup you'll likely want to permanently set the dpi resource. You can do so on a per-template or per-VM basis: Once you found a value that fits your setup you'll likely want to permanently set the dpi Xresource. You can do so on a per-template or per-VM basis:
- add a `Xft.dpi: xxx` line to the TemplateVM's Xresource file (`/etc/X11/Xresources` or `/etc/X11/Xresources/x11-common` for whonix-ws-template).
- or, add a `Xft.dpi: xxx` line to .Xresources file in *each* VM's user profile (`$HOME/.Xresources`) - add (or modify) `Xft.dpi: xxx` in the TemplateVM's Xresource file (`/etc/X11/Xresources` or `/etc/X11/Xresources/x11-common` for whonix-ws-template).
- or, add `Xft.dpi: xxx` to `$HOME/.Xresources` in each AppVM.
Note for R3.2: the `Xft.dpi` resource should be used by applications; if you have issues you may want to try the following (replace `2` and `0.75` accordingly): Note for R3.2: the `Xft.dpi` resource should work but if you have issues you may want to try the following (replace `2` and `0.75` accordingly):
~~~ ~~~
gsettings set org.gnome.desktop.interface scaling-factor 2 gsettings set org.gnome.desktop.interface scaling-factor 2