mirror of
https://github.com/donovanglover/nix-config.git
synced 2025-01-24 06:38:36 +01:00
My NixOS configuration with Nix Flakes, Home Manager, Stylix, and Hyprland.
207ef19a7b
I've gone through a lot of terminal emulators by now, and have always switched between URxvt and Termite (due to the features they support). For URxvt, this is particularly cumbersome since the version in the official repositories does not have the patches required for practical use. Even with patches applied, URxvt supports neither true color nor emoji. Termite worked well, but it lacked image support. Kitty features all of the following: - True color support - Image support - Emoji support - Icon fonts support - Transparency support Additionally, projects like Ranger and Neofetch have already taken the initiative to support the Kitty image protocol (which, luckily for me, are the only programs I use with images in the terminal). Why not Alacritty, the other GPU-based terminal? --- Although Alacritty is also very performant, there are several things that keep me away from this terminal emulator. Alacritty, as of this writing, renders neither images nor emoji. Although it is certainly possible to use a terminal emulator without either of these, the lack of these features limits what you can do with the program you (presumably) spend the most time with on your computer. The current config setup is "all or nothing"; I cannot remove defaults from my alacritty.yml and expect those same defaults to carry over. Even common terminal escape sequences are hard-coded into the config file, which cannot be removed without breaking things. Some other benefits of kitty: - Full image support in transparent terminals - w3m hack + loop is no longer necessary for persistent images - No weird artifacts around the image - Can highlight text without affecting the image - Images aren't lost after switching between desktops |
||
|---|---|---|
| .archlinux | ||
| .fedora | ||
| bspwm | ||
| code | ||
| editorconfig | ||
| extras | ||
| fish | ||
| git | ||
| gpg | ||
| plasma | ||
| ssh-agent | ||
| tmux | ||
| vim | ||
| xmodmap | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
Dotfiles
TODO: Screenshots
Usage
Step 0. Clone this repository
Add --depth 1 to only fetch the latest commit.
git clone https://github.com/GloverDonovan/dotfiles.git --depth 1
Step 1. Install stow
- Arch Linux:
pacman -S stow - Fedora:
dnf install stow
Step 2. Install the dotfiles you want
For example, to use my vim config, run:
make package=vim
Since my dotfiles are managed with Stow, any of your existing dotfiles will not be overridden or changed.
List of dotfiles
- bspwm - All the config files relating to my window manager setup.
- code - My config for Code, a reasonable editor for non-vim users.
- editorconfig - Spaces or tabs? Just use
.editorconfig. - extras - A collection of miscellaneous other dotfiles I use.
- fish - My settings for fish, the friendly interactive shell.
- git - The standard version control tool.
- gpg - My settings for GPG.
- plasma - Dotfiles specific to KDE Plasma.
- systemd - User services, such as ssh-agent and urxvtd.
- tmux - A vim-like terminal multiplexer that gets out of your way.
- vim - The settings I use for vim, also known as the best editor.
- xmodmap - Make caps lock function as ctrl and escape.
Uninstall
If you don't want to use some of my dotfiles anymore, they can be easily uninstalled. For example, if you don't want to use my .vimrc anymore, run:
make uninstall package=vim
This will only remove the files that Stow owns, while keeping your other files intact.