When I login and attempt to use dmenu, it will take a moment before that
is possible and I thought that having it load before I try to use it
would be nice. Then I found an issue about it and PR that closed it, but
didn't notice the commit is not in any released version so I typed this
in advance.
Firefox is going to annoy me by not floating sooner or later, so I think
it's better to float it and keep using it as the only thing in one
workspace.
* pgup/down navigation for workspaces, I may not use them, but I was
playing around
* add a lot of comments
* read the fine manual of i3lock, enable cursor that I often use to
check the device is alive, turn both backgrounds black and enable
showing of failed login attempts
* disable notify-send:ing volume changes when media keys are used as
pasystray does that by itself
* unfloat Firefox for now, even if I will likely need to float it again
when I attempt to use it on Zaldaryn.
Tor Browser requires floating even more than Firefox as there
privacy.resistfingerprinting is enabled by default and it warns you if
your window is bigger than it sets as that can be used for
fingerprinting.
I removed Galculator keybind accidentally in commit
a78dcdf452 and I have picked it, because
it's the default calculator app in MATE.
Adjusted from Jens Erat from
https://faq.i3wm.org/question/125/how-to-change-the-systems-volume.1.html
According to a comment this only works when something is playing, but I
think that is the only case when I need volume keys and is improvement
over it stopping working with volume devices changing. The proposed
cutting running again resulted to three devices being listed and thus
doesn't work.
I also have the volumeicon which I can use to adjust volume if I really
need to while there is nothing playing.
* remove some comments
* add Microsoft Corp. Wired Keyboard 600 (model 1576) keybinds for keys
I recognised and may use. Closes#98
* added keyboard layout setting to autostart
* set wallpaper to solid black
I don't think I like this very much, but it's supposed to be easier on
eyes and maybe I will get used to it especially after some migraine
light sensitivity attacks...
It appears that I have been doing locales wrong for years and only now
something has decided to not accept the incorrect versions?
Alternatively Debian has decided to stasrt doing it somehow different
from others, but I don't think so.
Nowadays I am mainly on laptop which the 11px is very small and
uncomfortable to look at. I don't know if it's just that or that I have
gotten older (hah).
I hope that this doesn't look bad in other environments.
For older systems use tmux-old-ncurses.bash (also added in this commit)
for forcing screen-256color instead.
From what I have understood the difference is that screen-256color
doesn't handle italics or something.
It doesn't fix LOT, but I don't care and I should be sleeping and not
committing things.
Also changed `doesn't` to `does not` as `xrdb` cared too much about the
`'` even if it was in comment.
This reverts commit 74d57e0b0f.
* * * * *
Apparently my tests were flawed as seen after reboot and there is no
terminfo for tmux-256color even in Arch stable repos yet.
