Marty Oehme
6fabac6cd8
Finally made the switch from alacritty to kitty. I have been thinking about this for a while. Both, fundamentally, serve my purposes just fine. Both are fast, customizable, gpu accelerated, and so on. Kitty feels a little faster on the input, but this should not provide major differences. One big difference, however, is now very apparent and I can feel it: Alacritty, on wayland, does not support any picture preview. It does not support sixel, and things like w3mimg or ueberzug are based on and require X11 to run. Kitty brings its own graphics display library and it seems both pretty stable and fast. I have not done much more with it than use it in things like vifm image previews but it should be much more stable than things like ueberzug, much faster than things like sixel. Time will tell. Switched other modules to make use of kitty instead of alacritty: vifm uses kitty previews, river spawns kitty instances, systemd units use kitty instances, waybar presents extra mouse-click interactions through kitty, and styler contains a processor to style kitty permanently. I would love to converge this all a bit more on the `$TERMINAL` env var, but this is unfortunately difficult for things like systemd and waybar. For waybar I currently see no real way except for a custom `ideal-terminal` script which just goes down the list of terminal emulators I want to run, depending on which is installed, since it does not read env vars, while for systemd it might be feasible to import user environment variables, but also connected to additional complexity and overhead which it does not seem worth for the currently two simple service units it affects. Also removed some obsolete sxhkd and sh settings from the move to wayland. |
||
|---|---|---|
| .. | ||
| .config/sh | ||
| .local/bin | ||
| README.md | ||
sh
The bare minimum terminal configuration for a working system. Contains:
- an XDG compliant home directory setup
- several basic environment variables
- simple aliases
- an optional fzf default setup
- X autostart
While other modules are largely optional, this module is the only one strictly necessary for the system to really work at all.
Additionally contains two scripts on which some other modules build:
- a simple script to detect if applications exist (and optionally warn the user if they don't)
- and a script to check if internet connectivity exists