CarlosSousa/dotfiles
1
0
Fork 0
mirror of https://github.com/zebrajr/dotfiles.git synced 2025-12-06 00:20:05 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
e2d6eb034f
dotfiles/.config/nvim
History
Carlos Sousa e2d6eb034f renamed all files such that they match they target destination
2025-07-11 14:30:53 +02:00
..
lua renamed all files such that they match they target destination 2025-07-11 14:30:53 +02:00
.gitignore renamed all files such that they match they target destination 2025-07-11 14:30:53 +02:00
init.lua renamed all files such that they match they target destination 2025-07-11 14:30:53 +02:00
lazy-lock.json renamed all files such that they match they target destination 2025-07-11 14:30:53 +02:00
README.md renamed all files such that they match they target destination 2025-07-11 14:30:53 +02:00

README.md

neovim config files

A neovim configuration ready to go.

It will bootstrap on it's own on first launch as long as you have:

  • Required: neovim 0.10+
  • Recommended: nodejs & npm - needed for some LSP

If just starting / want to learn vim motions and not vim, the IDE / the LSP is configured in vscode and you need to get things done now, you can still use it, since it will change keymaps and other QoL changes for VSCode if the vscode-neovim plugin is installed.

Structure

  • init.lua : the main neovim loader
  • lua/ : where everything is organized
    • configs/ : where configuration files for treesitter, lsp servers and others live
    • plugins/ : where each individual plugin is configured. The directory will be autoloaded and autoinstalled
    • themes/ : where the themes live. The directory will be autoloaded and autoinstalled
    • user/ : the main self for neovim - will load keymaps and the plugin manager
    • vscode/: keymaps and configs that will be used if neovim is called from vscode
    • editor_settings.lua - configuration for neovim (the IDE) settings
    • leaders.lua - remaps the leader keys

Plugins