dotfiles/README.md

Dotfiles

Personal configuration files for an Arch Linux workstation (Hyprland + Neovim + VST plugin), managed with GNU Stow.

Layout

Directory	Contents
term/	Fish + kitty + starship + nvim + tmux + yazi + fastfetch + opencode terminal environment
hypr/	Hyprland compositor config, kitty theme, wpaperd wallpapers
kreation/	VST plugin (MT-PowerDrumKit.vst3)
_install_skripte/	Miscellaneous install helper scripts

Each top-level directory is a stow package. stow symlinks the files from the repository into your home directory (e.g. term/.config/... → ~/.config/...).

Prerequisites

• Arch Linux (or a distro with pacman)
• stow
• Relies on git, sudo, curl

Quick start

# 1. Clone the repo
git clone https://github.com/<user>/dotfiles.git ~/.dotfiles
cd ~/.dotfiles

# 2. Install a target and symlink its files
make term       # terminal + fish + kitty + nvim
make hypr       # Hyprland (also pulls in basic + term)
make kreation   # VST plugin (also pulls in basic)

Run make <target> from the repository root. Each target first runs the relevant install script and then stows the package.

The install scripts require sudo and may prompt for your password.

Targets

Target	What it does
make term	Runs term/setup.sh (installs terminal packages, sets fish as default shell, clones tmuxifier), then stow term
make basic	Runs install_basic_pcks.sh, stows nvim, runs nextcloud.sh
make hypr	make basic, installs Hyprland packages, stows hypr, runs the Hyprland setup scripts (ensure-env.sh, portal-host-override.sh, fix_dolphin_file_associations.sh)
make kreation	make basic, installs VST runtime, stows kreation
make buntes-monster	Everything (basic + hypr + kreation), then wires up symlinks

Managing terminal packages

The terminal package list lives in a single editable file:

term/packages.txt

Add/remove packages on separate lines. Lines starting with # are ignored, and you can switch between package sources with section markers:

@pacman   # install via pacman (default)
@aur      # install via yay (AUR)
@npm      # install via npm -g

The default section is @pacman. Any AUR dependency (yay) is bootstrapped automatically by term/setup.sh.

What the install scripts do

• term/setup.sh – enables multilib, updates the system, installs yay if missing, reads term/packages.txt and installs all packages with --needed (skips already-installed ones), sets fish as the default shell (chsh -s /usr/bin/fish), clones tmuxifier, adds the git yazi plugin, and runs sudo updatedb. It is idempotent and safe to re-run.

Stow: resolving conflicts with existing paths

stow refuses to create a symlink where a real file or directory already exists on the target (your home directory). When you first set up a machine that already has configs in ~/.config, you typically see an error like:

WARNING: stowing term would cause conflicts:
  * existing target is neither a link nor a directory: .config/fish/config.fish

The recommended workflow is to back up the affected paths and remove them from the target location so stow can take over, then restore anything you want to keep as an overlay on top of the symlink. There are a few common approaches:

1. Back up and remove (recommended for first-time setup)

Point stow elsewhere so it only reports conflicts without touching anything, then handle the listed paths yourself:

# Dry-run to see exactly which paths conflict
cd ~/.dotfiles
stow --verbose --simulate term

# Inspect the conflicts, then back them up on the target side
mkdir -p ~/.config-backup
mv ~/.config/fish ~/.config-backup/fish      # example — repeat for each conflicting path

# Now stow can create the links
stow term

Afterwards you can restore your old configs on top of the symlinks if you want a custom overlay:

cp -r ~/.config-backup/fish/* ~/.config/fish/

The backup dir lives outside the stow packages, so stow never touches it.

2. Use --adopt with care

git stash        # only if you have uncommitted repo changes you want to keep
cd ~/.dotfiles
stow --adopt term
git checkout .   # discard any files that stow pulled into the repo

stow --adopt moves conflicting files from your home dir into the repository (overwriting what's stored there), then creates the symlink. This is convenient but destructive to the repo copy of those files — always review with a simulate run first and reset via git afterwards if you didn't intend to change the tracked config. Prefer approach #1 unless you deliberately want to recapture your live config into the repo.

3. Skip conflicts you don't manage in the repo

If a path simply shouldn't be managed by stow, use --ignore:

stow --ignore='\.config/(local|misc)' term

---

When in doubt: run stow --verbose --simulate <target> first — it prints what would happen (linking) without changing anything. Never rm -rf the ~/.config of something you still want to keep; move it to a backup directory instead.