Skip to content

POST-INSTALL.md

Latest commit

 

History

History
207 lines (149 loc) · 4.61 KB

POST-INSTALL.md

File metadata and controls

207 lines (149 loc) · 4.61 KB

bugsvim Post-Installation Setup

After running the installation script, follow these steps to ensure everything works correctly.

npm PATH Configuration

The installation scripts configure npm to use ~/.npm-global for user-level global packages to avoid permission issues.

Verify npm Configuration

npm config get prefix --location=per-user
# Should output: /home/your-username/.npm-global

Add npm to Your Shell PATH

The npm packages installed in ~/.npm-global/bin need to be in your PATH. Add the following to your shell configuration:

For Bash (~/.bashrc)

export PATH=~/.npm-global/bin:$PATH

For Zsh (~/.zshrc)

export PATH=~/.npm-global/bin:$PATH

For Fish (~/.config/fish/config.fish)

set -gx PATH ~/.npm-global/bin $PATH

Apply Changes

After editing your shell configuration, reload it:

# Bash
source ~/.bashrc

# Zsh
source ~/.zshrc

# Fish
source ~/.config/fish/config.fish

Or simply open a new terminal window.

Verify Language Servers are Available

After setup, verify the language servers are in your PATH:

# LSP servers
lua-language-server --version
clangd --version
pyright --version

# Formatters
stylua --version
prettier --version
shfmt --version
clang-format --version

# npm packages should now be accessible
which lua-language-server
which bash-language-server
which stylua
which prettier

Troubleshooting

Command not found: lua-language-server

Problem: npm packages installed but not in PATH

Solution:

  1. Check npm prefix: npm config get prefix --location=per-user
  2. Ensure ~/.npm-global/bin is in your PATH
  3. Add PATH export to your shell config file
  4. Reload shell: source ~/.bashrc (or equivalent)

Permission denied errors

Problem: npm tries to write to system directories

Solution:

  1. Verify npm config: npm config get prefix --location=per-user
  2. Should return: /home/username/.npm-global
  3. If not, reset with: npm config set prefix '~/.npm-global' --location=per-user

Packages missing in verification

If verification shows some packages missing:

Debian/Ubuntu:

npm install -g lua-language-server bash-language-server
npm install -g @johnnymorganz/stylua-bin prettier @fsouza/prettierd
pip3 install --user pyright ruff

Arch Linux:

npm install -g bash-language-server
npm install -g @johnnymorganz/stylua-bin prettier @fsouza/prettierd

Fedora/RHEL:

npm install -g bash-language-server
npm install -g @johnnymorganz/stylua-bin prettier @fsouza/prettierd

Clone bugsvim Configuration

Once language servers are verified working:

# Clone the bugsvim configuration
git clone https://github.com/ddubs/bugsvim ~/.config/nvim

# Launch NeoVim
nvim

# Plugins will auto-install on first launch (lazy.nvim)

Verify NeoVim LSP

Inside NeoVim, check that LSP servers are connected:

:LspInfo
:checkhealth

Optional: Install Additional Packages

Hyprland LSP (hyprls)

Arch:

yay -S hyprls
# or if using paru:
paru -S hyprls

Debian/Ubuntu: Build from source:

git clone https://github.com/hyprwm/hyprland /tmp/hyprland
cd /tmp/hyprland
make hyprls
sudo cp hyprls /usr/local/bin/

Fedora: Similar to Debian, build from source.

Nix LSP (nil)

Arch (AUR):

yay -S nil

Debian/Ubuntu/Fedora: Install via Nix:

nix run github:oxalica/nil

Frequently Asked Questions

Q: Why use ~/.npm-global instead of system npm?

A: Avoids permission issues and doesn't require sudo for global installs. Each user maintains their own npm packages.

Q: Do I need to reinstall if I switch shells?

A: No, the npm configuration is persistent. Just add the PATH export to your new shell's config file.

Q: Can I use system npm with sudo?

A: Not recommended. The installation scripts configure npm for user installs to prevent permission issues.

Q: What if I already have npm packages installed globally?

A: The installation scripts use --needed flags and check for conflicts. Existing packages won't be reinstalled.

Next Steps

  1. ✓ Run installation script
  2. ✓ Configure shell PATH for npm
  3. ✓ Verify language servers are in PATH
  4. ✓ Clone bugsvim configuration
  5. ✓ Launch NeoVim and verify LSP
  6. Start editing!

Support

For issues with:

  • Language servers: Check if executables are in PATH with which <command>
  • npm permissions: Verify npm config with npm config get prefix --location=per-user
  • NeoVim LSP: Run :LspInfo and :checkhealth inside NeoVim
  • Specific packages: Refer to the troubleshooting section above