narze dotfiles

You can install the dotfiles using a one-line shell command. Using the ASK=1 environment variable allows you to customize your name during the first installation. If you omit ASK=1, the script will use the maintainer's names for the machine configuration.

Note that the first installation will skip encrypted files; you must retrieve your GPG private key manually later. Because the script may not complete fully on the first pass, you should run chezmoi -k apply repeatedly until the setup is complete.

ASK=1 sh -c "$(curl -fsSL https://raw.githubusercontent.com/narze/dotfiles/master/remote_install.sh) -k -v"

This repository includes a starter template for LazyVim. To configure or customize your Neovim environment using this template, refer to the official LazyVim installation documentation for specific setup steps and requirements.

https://lazyvim.github.io/installation

To apply custom CSS modifications to the Vivaldi browser interface, follow these steps:

1. Place your custom .css files into the ./custom_ui_modifications directory within the dotfiles repository.
2. Enable CSS styling in Vivaldi by navigating to vivaldi://experiments in the address bar and enabling the option to allow using Styles.
3. In Vivaldi's settings, locate the Custom UI Modifications folder setting and point it to the directory containing your CSS files.
4. Restart Vivaldi to apply the changes.

# No runnable code provided; follow manual steps in Vivaldi settings

To ensure you are using the native ARM version of Kitty on Apple Silicon, you may need to build it from source and replace the Homebrew binary:

1. Get the source: ghq get -l kovidgoyal/kitty
2. Build using Python: /opt/homebrew/bin/python3 setup.py kitty.app
3. Move to Applications: cp -r kitty.app /Applications/kitty.app
4. Replace the CLI link: Remove the Homebrew version and symlink the new launcher.

ghq get -l kovidgoyal/kitty
/opt/homebrew/bin/python3 setup.py kitty.app
cp -r kitty.app /Applications/kitty.app

# Replace CLI
rm /opt/homebrew/bin/kitty
ln -s $PWD/kitty/launcher/kitty /opt/homebrew/bin/kitty

The dotfiles are managed using Chezmoi. Use the following commands to manage your configuration:

• Initialize/Customize: Use ASK=1 chezmoi init to change variables or chezmoi edit-config to edit the configuration.
• Apply changes: To change data or scripts, run chezmoi cd to enter the chezmoi directory, edit the files, and then run chezmoi apply.
• Set encryption password: Run SETPASS=1 chezmoi init to set your encryption password.
• Force apply: Use chezmoi apply -k (keep going) to continue applying even if some errors occur.

# Change variables
ASK=1 chezmoi init

# Edit config
chezmoi edit-config

# Apply changes after editing files in chezmoi directory
chezmoi cd
# ... edit files ...
chezmoi apply

On Debian, chezmoi init prompts you to select a setup profile. This profile is stored in your configuration and can be changed by re-running chezmoi init.

Available profiles:

• minimal (default): Installs base essentials (apt packages: zsh, git, curl, unzip) and mise.
• homelab, ai-agent, etc.: These run on top of the minimal base.

Adding a new profile: Create a new folder within the profile directory. .chezmoiignore automatically discovers these folders and runs only the active one. Scripts are located in:

• .chezmoiscripts/debian/ for run-once installs.
• scripts/linux-debian/<profile>/ for optional per-apply scripts.

You can influence how the wrapper executes the underlying rubocop-daemon using the following environment variables:

Note: The script also detects asdf automatically and will use asdf exec if available.

The repository includes a Makefile with the following commands:

• make help: Print the command list.
• make dotfiles: Update dotfiles.
• make apply: Run chezmoi apply.
• make macos: Run the macOS specific setup script.

$ make
help                           Print command list
dotfiles                       Update dotfiles
apply                          Run chezmoi apply
macos                          Run macos script

The executable_wait_for_nas script relies on the following environment variable to determine which mount point to monitor:

NAS_PATH: The absolute path to the NAS directory that needs to be mounted.

The murder command accepts a single argument to determine the target type. Use the following patterns:

usage:
murder 123    # kill by pid
murder ruby   # kill by process name
murder :3000  # kill by port

The wrapper supports the following flags to handle standard input (STDIN):

-s, --stdin
    Read input from STDIN. The wrapper preserves final new lines when ingesting from STDIN.