forked from extern/nix-config
3e77f8f992
It turns out that since tmux sessions will stay active after you close a terminal window, it is easy to end up with a lot of empty sessions. This makes it difficult to detach and re-attach the appropriate tmux sessions. Additionally, some features of kitty (notably terminal images and dynamic background opacity) will not work inside tmux. Since kitty has its own window manager, this caveat can be easily circumvented. By invoking tmux manually instead, we also avoid the problem of nested tmux sessions. |
||
---|---|---|
.. | ||
.config | ||
.icons/default | ||
.xinitrc | ||
.Xresources | ||
README.md |
bspwm
I use bspwm
as my window manager of choice. My setup is optimized for HiDPI, so you will have to manually adjust the numbers if you aren't using a HiDPI display.
Dependencies
- bspwm - Window manager
- polybar - Panel
- dunst - Notifications
- rofi - Window switcher, application launcher, and dmenu replacement
- sxhkd - Keybinds
- rxvt-unicode-patched - Terminal with image support
- termite - Terminal with true transparency, icon fonts, true color, and emoji support
- python-pywal - A universal color scheme changer
- feh - Used to set the background image
Installation
make package=bspwm
Usage
Either startx
directly or use a display manager. Assuming you have the necessary dependencies installed, and assuming you configured your system properly, everything should just work.
Note
When you use wal
to change the color scheme, add -o ~/.config/wal/done.sh
to run the done script. The fish abbreviation w
does this automatically for you.