![]() ![]() Then change the resolution with xrandr and finally restart the awesome-client. If you find anything useful here, you can: star a repo - this really motivates me to work on. Clone repository under /.config/awesome folder. Xresources using sed and then call xrdb to apply that change. This is a project page of the github repo with set of widgets for Awesome Window Manager plus few articles on widget creation/customization. They will first change the DPI-setting in. bashrc to help me with that:Īlias 1440p="sed -i -E s/^Xft.dpi:144/Xft.dpi:96/ ~/.Xresources & xrdb ~/.Xresources & xrandr -output HDMI-A-0 -mode 2560x1440 -pos 0x0 -rotate normal -rate 120 -dpi 96 & echo 'awesome.restart()' | awesome-client"Īlias 2160p="sed -i -E s/^Xft.dpi:96/Xft.dpi:144/ ~/.Xresources & xrdb ~/.Xresources & xrandr -output HDMI-A-0 -mode 3840x2160 -pos 0x0 -rotate normal -rate 60 -dpi 144 & echo 'awesome.restart()' | awesome-client" Sometimes I like to use 1440p resolution with 120Hz instead of 2160p and 60Hz (for games like RDR2), but only changing the resolution and refresh rate will make everything look too big, so I created two aliases in my. Any layout can be applied dynamically, optimizing the. Run "xrandr -output HDMI-A-0 -mode 3840x2160 -set "scaling mode" "None" -pos 0x0 -rotate normal -rate 60 -dpi 144"Īt the bottom of. It manages windows in different layouts, like floating or tiled. You can check that the rules are applied when you restart awesome (with the firefox window open on the wrong tag, it should move to the right one). Xrandr launches with my autostart.sh and looks like this: Did you restart awesome to make sure the config changes are applied If yes, then I suspect something like 'the rules are applied when the client first exists, but it doesn't have this class yet'. I had to put DPI-settings in two places: autostart.sh and. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |