Missing installation step

[Cyb3rN3xus]

The error DOTFILES: unbound variable occurs because the bin/dot script expects the environment variable DOTFILES to be set to the absolute path of the dotfiles directory. The script uses set -u (nounset) to treat unset variables as errors, so it fails when DOTFILES isn’t defined.

Step-by-step installation

1. Navigate into the dotfiles directory (if not already there):

   cd /path/to/nicknisi_dotfiles   # or the directory you renamed it to

2. Set the DOTFILES environment variable to the current directory’s absolute path:

   export DOTFILES="$(pwd)"

3. Verify the setup by running the help command:

   ./bin/dot help

   This should now display the available commands without errors.

4. Install the dotfiles – typically the main command is install or bootstrap. Check the help output, but a common one is:

   ./bin/dot install

   or

   ./bin/dot bootstrap

   This will symlink configuration files to your home directory, install Homebrew packages (if on macOS), and set up other tools.

5. If you’re on Linux, note that the dotfiles include a Brewfile (Homebrew). You may need to install Homebrew for Linux first, or manually adapt the package installation to your system’s package manager.

Additional tips

• The script may also rely on the directory being named dotfiles (e.g., for some hardcoded paths). To avoid any issues, you can rename the folder back:

  mv nicknisi_dotfiles dotfiles
  cd dotfiles
  export DOTFILES="$(pwd)"

• Always review the README.md in the repository for the most accurate and up‑to‑date instructions.
• After installation, you may want to add export DOTFILES="/path/to/dotfiles" to your shell startup file (e.g., ~/.bashrc or ~/.zshrc) so that it persists across sessions.

If you encounter any further errors, check the script’s output – it often gives hints about missing dependencies or required system configurations.