Skip to content

replace neovim/lazy.nvim setup with plain vim - #246

Merged
viqueen merged 1 commit into
mainfrom
chore/vim-editor-setup
Oct 3, 2026
Merged

viqueen merged 1 commit into
mainfrom
chore/vim-editor-setup

Conversation

@viqueen

@viqueen viqueen commented Oct 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • Drops the nvim + lazy.nvim + mason/lspconfig/telescope/treesitter stack in favor of a single-file, plugin-free vim config (cli/.vimrc).
  • config_vim now symlinks cli/.vimrc to ~/.vimrc (vim's standard config path) and sets core.editor, so plain vim picks up the config everywhere (interactive shell, dev edit, git commit) without an alias or -u flag.
  • Uses vim's built-in retrobox colorscheme (bundled since vim 9, gruvbox-style muted/dark) instead of vendoring a custom colorscheme file, so there's nothing extra to maintain.
  • Removes the neovim tool from .mise.toml and updates the README's editor section accordingly.

Test plan

  • Verified syntax on + retrobox load automatically via a bare vim invocation against a symlinked ~/.vimrc, with no alias or flags
  • Verified trailing-whitespace-on-save autocmd still strips trailing spaces
  • Verified .eslintrc/.babelrc filetype association still sets json
  • Confirmed prettier --check . passes on the full diff

Drop the nvim + lazy.nvim + mason/lspconfig/telescope/treesitter stack
for a single-file vim config with no plugin manager. config_vim now
symlinks cli/.vimrc straight to ~/.vimrc (vim's standard lookup path)
and sets core.editor, so vim picks up the config everywhere - shell,
scripts, and git commit - without needing an alias or -u flag.

Uses vim's built-in retrobox colorscheme (bundled since vim 9) instead
of vendoring a custom one, so there's no colorscheme file to maintain.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
@sonarqubecloud

sonarqubecloud Bot commented Oct 3, 2026

Copy link
Copy Markdown

@viqueen
viqueen merged commit 81195c6 into main Oct 3, 2026
3 checks passed
@viqueen
viqueen deleted the chore/vim-editor-setup branch October 3, 2026 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant