I’m trying out to install I3 after having installed EOS with KDE using the live iso.
Following the instruction on the endeavouros-i3wm-setup page. At the second step, after having cloned and changed directory to etc/skel one of the commands is as follows:
cp .Xresources ~/.Xresources
However I’ve noticed that the file in the git repo isn’t called .Xresources but just Xresources
After checking the install script, it also uses the command cp .Xresources
Furthermore, doing a clean I3 install using the live ISO results in a user home directory with the file ~/Xresources instead of ~/.Xresources
Thanks for the welcome! It has been a good endeavour so far
One slightly OT question but still related to the eos customisation of i3.
I’m really curious what logic is behind key custom key-bindings for navigation, i.e. I3 by default uses $mod+j $mod+k $mod+l and $mod+; for focus left down up and right (i.e. they are all on the ‘home row’), but with the eos config this has been mapped to $mod+j $mod+k $mod+b and $mod+o.
I know it is easily changed, but I’m very curious about the reasoning why up and down got mapped to $mod+b and $mod+o. It feels very random, or I’m missing something obvious?
It is very much a community effort in conjunction with @joekamprad. Some of the bindings are joe’s others came later from the community. So in the end EndeavourOS i3 is very much a “custom” spin on i3.
It is also designed to make the transition of new users to a tiling WM easier.
I will definitely give this “custom spin” a try, but yes, I will have to change those default key bindings. The b which is “on the bottom of the keyboard” is to focus up, and o vice-versa, is just
the keybindings have a lot limitations, it is simply not possible to have them all in a logical place for all sort of layouts and in addition adding some needed on top of the defaults was impossible.
I was already thinking about to change all defaults back to i3 defaults and start over.
But limitations are in the way…
