My dots

Reqs

creds

~/s/g/private/credentials.fish file with following variables set:

$GITHUB_KEY

hardware-configuration

Should have your correct hardware-configuration.nix at /etc/nixos/hardware-configuration.nix. In my setup hosts normally include their associated hardware-configuration.nix files, but they are used as a backup in case /etc/nixos/hardware-configuration.nix is not found.

config location

This configuration MUST be located in ~/nix, (because I didn't find a way to get the actual positions of the files in which the code being ran is written at runtime, so many things assume ~/nix to be the config root.

Installation

Set the INSTALL_PATH, then run

sh << 'EOF'
INSTALL_PATH="..."
if [ "$INSTALL_PATH" = "..." ]; then
    echo "set the INSTALL_PATH to the target installation path, then rerun the command"
    return 1
fi
mkdir -p "$(dirname "$INSTALL_PATH")" && \
git clone --depth=1 https://github.com/valeratrades/nix "$INSTALL_PATH" && \
cd "$INSTALL_PATH"
EOF

Manual adjustments

Introduced MANUAL keyword in config next to things that require manual adjustments and cannot be proceduralized. Do not guarantee surjectivity.

Currently:

• git config in ./os/configuration.nix must be adjusted for the correct username and email
• set up nyxt

   git clone https://github.com/aartaka/nx-dark-reader.git ~/.local/share/nyxt/extensions/nx-dark-reader

Usage

fhs

Spawns an fhs-compatible shell

Dev

Currently config is impure. For possibility of reversion, all known places that introduce impurities are marked with #IMPURE

Other

Philosophy

• No convenience optimisations should be made for suboptimal actions/behaviors/patterns. For example, I will never have Spotify pinned to a designated workspace, as it is desirable to maximize friction around these.

• Declarative > Situational. That's the reason I don't end up using shortcuts for switching panes. All my tools must be designed with this in mind: it's fine if more work is required for the same action, as long as this leads to it being pure; and then all situational, impure, shortcuts should not be introduced at all, as it only convolutes the manpage. The largest change in behavior this should prompt: getting rid of all toggles, unless it is meant to be evoked exclusively via keybind, (meaning can't add on / off), and there is a keybind deficit.

Cli

Target length for general aliases is 2 characters, if they are important enough. One-letter cases are mostly reserved for custom scripts, local to the project, eg: commands initialized when I cs into a directory with run.sh in it.