Dotfile management and organization

This repo contains scripts that help with dotfile management and organization across a variety of my workspaces.

Clone locally

On a new machine, reproduce this using git: git clone https://github.com/BarunKGP/dotfiles.git

This fetches all dotfiles. Ideally you would have GNU stow as well to set up symlinks automatically. If not, there are a few helper scripts to set things up

Setting up Neovim as an IDE

Most server environments I work on are painfully old (some don't even have Git 2.0!) In such cases, it is best to use an nvim.appimage to keep things lightweight and portable. You can always install the fully decked out version of Neovim if you so choose.

Setting up helper scripts

After cloning this repo, run the setup_nvim.sh helper script using

./setup_nvim.sh

The script is set to use bash but you could edit the first line to reflect the shell of your choice. (I have to keep switching between bash, ksh). It installs the nvim.appimage, makes it an executable and pulls in the config files from kickstart.nvim. This also sets up the $HOME/.config/nvim directory separately which is needed if you aren't using stow. It also sets an alias for nvim so that you can use Neovim as usual by calling nvim <dir/file>

---

Other setup actions

This repo contains configurations for:

• tmux
• Neovim
• espanso

Espanso

espanso is a text expander based on YAML, which I use to store frequently used snippets such as emails, personal information, (names, addresses, phone numbers), etc., which I can then quickly populate in any new machine.

Steps:

1. Install espanso for your system.
2. Pull these stored snippets and configurations.
3. Move the espanso folder to the [https://espanso.org/docs/get-started/#configuration](location expected by espanso). Alternatively, you could explore how the edit the location where espanso looks for configs and matches, and then you can store this folder wherever you choose.
4. Reload the espanso config if needed. You should now be ready to use these snippets on your system

---

NOTE:

1. You should not store passwords and secrets in espanso. Do not treat it as a security solution.
2. If you do store any sensitive information on your local config (not recommended), make sure they are ignored during backup. Any passwords and tokens will be detected by Github and the push will fail.

Restoring espanso matchers

• Ensure you have the ESPANSO_PATH environment variable set up pointing to the match directory
• Copy the matcher files from espanso/match/ to $ESPANSO_PATH/match
  • This may overwrite existing matchers. Make sure you create a backup for your existing matchers
• You can also copy the config files from espanso/config/ to ESPANSO_PATH/config
• Restart espanso to load your new matchers: espanso restart
  • NOTE: This command should be run on the host system where you installed espanso. If you have espanso on Windows and are using WSL to setup dotfiles, this command needs to be run on the Windows system itself.