3 ms·
Are you the only user? Do you always use i3? If yes to both, you could have your bashrc (or you shell's equivalent) start X and i3 on a TTY login? https://wi
by doubled112 4y ago
Are you the only user? Do you always use i3?
If yes to both, you could have your bashrc (or you shell's equivalent) start X and i3 on a TTY login?
https://wiki.archlinux.org/title/Xinit#Autostart_X_at_login https://wiki.archlinux.org/title/Xinit#Autostart_X_at_login
- LargoLasskhyfv 4y agoAn even more lazy approach is logging into the console, regardless if textmode or framebuffer, and simply do upward arrow & enter, since whatever starts your session is the last entry in shell history anyways :-) This way there is less surprise/annoyance with flickering/crashing X, like you could have when starting X unconditionally after login, which could happen after you modified something to test. On another console, to not spoil the history for that upward arrow & enter thing ;-) Which works regardless of shell/WM/DE/OS/whatever, at least it does so for me.
- 1MachineElf 4y agoIs this an approach that works well with screen locking, or is a display manager really necessary for that feature?
- ankurdhama 4y agoYou don't need display manager to lock screen in i3. Just run or bind a key to run i3lock (or other lockers like slock)