jade's dotfiles, nothing surprising.
⛧-128293 [jade arson.] d0d41c7021 [scripts] add one more hackerspace
thanks to chaos.jetzt12 for making me visit Flensburg - this is now the northmost hackerspace I've visited so far! ;p
2026-02-21 23:40:17 +01:00
.config [scripts/waybar-wifi] add blinking text to add attention to whether the space is closed or not 2026-02-17 21:16:57 +01:00
.local/share/applications [keyring-shenanigans] technology was a mistake. i wanna run into the woods instead of dealing with this bullshit 2025-08-04 22:22:04 +02:00
etc [systemd-things] add config files for zram-generator.conf as well as kernel parameters for zram swap 2025-10-04 20:13:03 +02:00
screenshots [readme] add more info about what could/should be customised 2025-08-10 17:45:59 +02:00
scripts [scripts] add one more hackerspace 2026-02-21 23:40:17 +01:00
usr [darkman] add darkman (more or less optional, current implementation makes it possible to stick with just niri and keyboard shortcuts) 2025-09-04 10:59:31 +02:00
.XCompose [XCompose] add dollcode key combinations :3 2025-05-27 14:53:18 +02:00
example.png [screenshots] updated screenshot to better represent the current state (yet again) 2025-11-11 11:02:20 +01:00
README.md [readme] add OSK as an option 2025-12-02 02:25:09 +01:00

dotfiles

jade's dotfiles, nothing too surprising.

An example screenshot showcasing the dotfiles in their setup on a laptop. It also features a terminal in the floating state, showing the obligatory neofetch.


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 etc folder goes into /, since that contains the configuration files for greetd as well as vconsole.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 .config folder goes into ~/.

Note

The .config folder 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/discord folder 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.txt file 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.

  • .config/swaylock/config to not point at /home/jade, but your respective user fixed by telling swaylock-effects to take a screenshot instead ;p
  • .config/niri/config.kdl to not point at /home/jade when it comes to the swaybg process that starts whenever you log in, but your respective user fixed by calling sh -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.kdl within 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-
two messages of mine: very long "bnuuuuu", and "the very efficient bnuuu'ing(tm)"


Credits


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