thanks to chaos.jetzt12 for making me visit Flensburg - this is now the northmost hackerspace I've visited so far! ;p |
||
|---|---|---|
| .config | ||
| .local/share/applications | ||
| etc | ||
| screenshots | ||
| scripts | ||
| usr | ||
| .XCompose | ||
| example.png | ||
| README.md | ||
dotfiles
jade's dotfiles, nothing too surprising.
Note
These dotfiles will go through heavy reworks soon-ish(tm) — the reason for that is a new niri release, finally allowing me to split up various parts of the configuration file.
Where to copy files to
- Scripts can go into
~/if you absolutely want to - you can also just leave the files there. - the
etcfolder goes into/, since that contains the configuration files forgreetdas well asvconsole.conf, the greeter configured here. You can skip this if you're coming from GNOME or KDE or want to use a completely different greeter altogether. - the
.configfolder goes into~/.
Note
The
.configfolder also contains a configuration file for Discord, disabling its need to check for patches every time it gets launched (to skip the annoyance of it complaining as soon as a new patch is out). If you want to change the behaviour back to Discord's default, just delete the.config/discordfolder in this case.
Generating different wallpaper variants
By default, with some of the scripts bundled [1], you just need to copy your wallpaper of choice to ~/Pictures/background.jpg, and the scripts will take care of the rest [2].
[1]: in this case, refresh-wallpaper.sh, make-blurry-wallpaper.sh and unfuck-swaybg.sh
[2]: making a blurred duplicate to ~/Pictures/background-blur.jpg for use by swww, and copying said blurred duplicate to /usr/share/backgrounds/userbg.jpg for use by greetd-gtkgreet.
Required software
Note
This list is incomplete. You can potentially help by double-checking and expanding it.
alacritty
nautilus
niri
waybar
swaybg
swayidle
swaylock-effects
hyprlock
swww
greetd
greetd-gtkgreet
xwayland-satellite
fuzzel
mako
screen
brightnessctl
pipewire-zeroconf (if using PipeWire)
jq
Semi-required software (due to keybinds and such)
Note
There's always the option to switch software, though it would deviate from the already-existing configurations and make future changes impossible to merge seamlessly. Since these are dotfiles, of course they'd be at least a little opinionated.
nautilus
bluetuith
nmtui
pavucontrol
helvum
cava
avahi / avahi-zeroconf
darkman (for automatic theme switching depending on your daytime and location)
geoclue
Required font packages
[ot]tf-fira-(mono|sans) (for everything once you hit the GUI)
[ot]tf-fira-go (for more international character support, replaces Fira Sans in some places)
terminus-font (for the virtual console)
noto-fonts
noto-fonts-cjk
noto-fonts-emoji
More or less optional software
Tip
You can consider this to be more of a "value-add" stash of software. It doesn't add much to the experience, though it could definitely smooth out your experience using this configuration as-is.
For cross-device stuff:
kdeconnect
For screenshots, in case you want a better tool:
flameshot
For the shell:
fish and pkgfile
For a lockscreen supporting fingerprint authentication (with some nice additions from my end):
hyprlock, playerctl (for MPRIS)
For a system-wide colour picker:
eyedropper
For a system tray applet making it easier to switch networks:
network-manager-applet
For an on-screen keyboard to use with touchscreens and such:
sysboard
Consider changing the following things:
- Create a symlink in
.config/fish/functions(like this:ln -s fish_prompt.sh fish_prompt_$HOSTNAME.sh) to whichever colour of prompt you want to have. (I recently changed my dotfiles to accommodate my new naming scheme.) - Create a
~/.ownerinfo.txtfile in your home directory, either just a stub ($ touch ~/.ownerinfo.txt) or edit that file by opening it in your favourite$EDITOR. This text then shows up whenever you lock your computer (or laptop, where it's most ideal).
Important
Anything below this is considered "legacy" documentation and will only stick around for the purpose of documenting fixes to said dotfiles.
fixed by telling swaylock-effects to take a screenshot instead ;p.config/swaylock/configto not point at/home/jade, but your respective userfixed by calling.config/niri/config.kdlto not point at/home/jadewhen it comes to theswaybgprocess that starts whenever you log in, but your respective usersh -c "swaybg [the entire set of arguments]"instead ;p
(I'll look into pointing both of them to actual reproducible values)
Tip
There's one thing you can (and probably should) still customise, though, and that's the key repeat interval in
.config/niri/config.kdlwithin the input/keyboard section.
The only reason why I set it so rapidly is because of a silly thing I still do with a friend of mine (if you read this, hi riley :3), so yeah lol-
Credits
- to unit ⛧-440729 for parts of its script to show more details to the currently connected WiFi network (adapted to make it work with NetworkManager, and outside of Nix(-compatible) environments)
Terms of use
do whatever you want with it idk
well except if you're a corporation, then just don't. thanks. <3
so yeah consider this CC BY-NC-SA 4.0 or something despite not even really fitting the first C of CC (*Creative* Commons). lol