Nvim: Difference between revisions
Appearance
Created page with "= Neovim = ''LazyVim configuration for writing in the dark'' == Overview == Current setup uses LazyVim as a base, stripped down to essentials. Like everything else, optimized for solitary work at 3am. == Plugin Stack == === Core === * '''LazyVim''' - Base configuration, most defaults disabled * '''init.lua''' - <code>require("config.lazy")</code> and nothing else === Visual === * '''ayu.lua''' / '''ayu-toggle.lua''' - Dark theme that doesn't burn retinas at night * ''..." |
(No difference)
|
Revision as of 18:15, 9 June 2025
Neovim
LazyVim configuration for writing in the dark
Overview
Current setup uses LazyVim as a base, stripped down to essentials. Like everything else, optimized for solitary work at 3am.
Plugin Stack
Core
- LazyVim - Base configuration, most defaults disabled
- init.lua -
require("config.lazy")
and nothing else
Visual
- ayu.lua / ayu-toggle.lua - Dark theme that doesn't burn retinas at night
- auto-dark-mode.lua - Follows system, though it's always dark anyway
- twilight.lua - Dims inactive code like thoughts you're not ready to process
- zen-mode.lua - Full screen focus mode for when the world needs to disappear
Minimal Interfaces
- minimal-statusline.lua - Just enough info to know the file saved
- minimal-telescope.lua - Fuzzy finding without the fuzzy thinking
- minimal-git.lua - Git integration stripped to essentials
Philosophy
Every plugin evaluated by modified TCWM scoring:
- Time saved vs configuration time
- Cognitive load when context switching
- Weight on startup time
- Multi-file editing capability
Current setup boots in ~50ms. Fast enough to capture thoughts before they escape.
Usage Patterns
- Primary: Markdown/Wiki editing for the archive
- Secondary: Quick scripts for data munging
- Tertiary: Viewing JSON responses from personal APIs
TODO
- [ ] Document specific keybindings
- [ ] Add configuration for LSP (when needed)
- [ ] Consider removing more defaults from LazyVim