My personal dotfiles for Neovim (Packer/Lazy), PowerShell, and Qtile configurations.

• Ultimate Neovim Setup Guide: lazy.nvim Plugin Manager
• How to Set up the Windows terminal with Powershell and Oh My Posh
• How to Set up Neovim for Windows and Linux with Lua and Packer

• Bash (Linux/macOS) or PowerShell (Windows)
• Neovim ≥ 0.10 (for Lazy.nvim config)
• Git
• Nerd Fonts
• NodeJS with npm
• Lazy.vim
• A C compiler in your path and libstdc++ installed: Windows support

git clone https://github.com/slydragonn/dotfiles.git ~/dotfiles
cd ~/dotfiles
chmod +x install-dotfiles.sh
./install-dotfiles.sh

git clone https://github.com/slydragonn/dotfiles.git $env:USERPROFILE\dotfiles
cd $env:USERPROFILE\dotfiles
Set-ExecutionPolicy Bypass -Scope Process -Force
.\install-dotfiles.ps1

Follow the individual README instructions:

• lazy setup
• packer setup

Or via Symlinks:

# Neovim
ln -s ~/dotfiles/nvim/lazy ~/.config/nvim

# PowerShell (Linux/macOS)
ln -s ~/dotfiles/powershell/profile.ps1 ~/.config/powershell/Microsoft.PowerShell_profile.ps1

# Qtile
ln -s ~/dotfiles/qtile ~/.config/qtile

• Lazy.nvim plugin manager
• Pre-configured LSP
• Telescope fuzzy finder
• Custom keymaps (see lua/slydragonn/maps.lua)

dotfiles/
├── nvim/               # Neovim configs
│   ├── lazy/           # Lazy.nvim setup
│   └── packer/         # Legacy Packer.nvim setup
├── powershell/
└── qtile/

Neovim issues:

1. Run :checkhealth
2. Ensure Node.js ≥ 16.x is installed
3. Delete ~/.local/share/nvim if plugins misbehave

PowerShell:

• Enable scripts first:

  Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Pull requests welcome! For major changes, please open an issue first.