Skip to content

Latest commit

 

History

History
110 lines (77 loc) · 3 KB

README.md

File metadata and controls

110 lines (77 loc) · 3 KB

Slydragonn's dotfiles

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

neovim setuo

📦 Included Configurations

Tool Description Config Path
Neovim IDE-like setup with Lazy.nvim ~/dotfiles/nvim/lazy/
PowerShell Profile/aliases/scripts ~/dotfiles/powershell/
Qtile Window manager config ~/dotfiles/qtile/

📚 Articles

🚀 Installation

Prerequisites

  • 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

Automated Setup

Linux/macOS

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

Windows (Admin PowerShell)

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

Manual Setup

Follow the individual README instructions:

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

🔧 Features

Neovim Setup

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

🧩 Structure

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

⚠️ Troubleshooting

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

🤝 Contributing

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