Instructions not included.
I typically just keep this repo cloned at ~/Projects/dots
and then use symlinks in
my home, ~/.config
, and ~/.local
folders, pointed at the appropriate resources.
Allows for easy "continuous development" of sorts.
The only exception to this approach, is the ./emptty
folder, which contains its own
README that explains what to do with it.
I've tried to keep everything as "user agnostic" as possible, except for a couple limitations:
./.config/aria2/aria2.conf
won't allow you to use~
,%h
, or$HOME
to complete a user's home directory. So unfortunately, download and session directories are hardcoded.
As of 2024-08-23
the above is no longer the case. The offending lines have been removed
from the configuration file, and instead are set in the start-aria2c
script as
command parameters.
- Some files in
./.local/bin
may have hardcoded paths, and would need a quick glance over before you try to use them. I'd instead suggest just cherry picking files in this directory to suit your needs.
This isn't an exhaustive list, but here are some of the tools/apps/services employed by or referenced within my dots:
amfora
- Gemini clientaria2c
- Download session managerblueman
- Bluetooth managerdeluge
- Torrent clientdunst
- Notification serviceemptty
- CLI-based desktop managererdtree
- Directory information appfzf
- Fuzzy-searching selectorherbstluftwm
- Tiling windows managerkitty
- Terminallibrewolf
- Security-hardened Firefox forkmpv
- Media playernitrogen
- Wallpaper managernmcli
- CLI client for Network Manageroh-my-zsh
,powerline10k
- Shellphetch
- Gopher clientpicom
- Compositorpolybar
- Task barrofi
- App/command Launchersabnzbd
- Usenet clientsystemd
- It's not that bad, reallytupimage
- Terminal image servicewebapp-manager
- Web app creatorweechat
- IRC clientwireguard
- VPN protocolwmctrl
- Window manager toolsxsecurelock
- Secure screen lockerxss-lock
- Screen locking serviceyt-dlp
- Fuck the police