README.md

nvim config

Only tested against Neovim latest release. Don't use what you don't understand.

pictured: Neovim in WezTerm with font Maple Mono and vim-colors-meh.
Tabline: the cwd is a project root; dev branch; there is one dirty buffer out of four total; and we are connected to nvim.sock
Winbar: Tree-sitter highlighting is enabled, orange filenames are dirty files, and there are no diagnostic issues.
Signs: gitsigns is active.
Status: Normal mode; type is searched with one occurrence found; ruler

Tool	Link
Plugin manager	lazy.nvim
Colorscheme	vim-colors-meh
Completions	blink.cmp
Status/tab/winbar	heirline.nvim
Local LSP	efm-langserver
File finder	snacks.nvim

custom things

• LSPs and external tools are expected to be installed via mise (as opposed to something like mason.nvim). This allows them to be used in neovim, in the CLI, and by coding agents alike.
• mappings should be defined in mappings.lua or the mappings subdirectory.
• the preferred way command to open files is with e
  • it will create a new nvim.sock if one does not exist
  • it will use a single Neovim instance over the socket otherwise
• if using my WezTerm config, <C-S-d> will toggle the terminal and Neovim theme between light and dark mode.
• LSP/tool config is done in dko/tools.lua
  • Both vtsls and coc.nvim are configured for JS/TS(x), but vtsls is what I am currently using and maintaining. coc.nvim is under review for removal.
    • Change coc.enabled in dko.settings to switch
    • When using coc, you can still trigger regular completions for other LSPs using <C-Space>
• formatting is handled in dko/utils/format.lua
  • of note is a pipeline that runs, based on project configuration one of:
    • ESLint exclusively
    • ESLint followed by prettier, or
    • prettier exclusively

---