Motivation: I have started making a switch to nvim as I increasingly found myself using vim environments for accessing compute platforms and VS Code was simply not rendering well with recurring issues. Sometimes the best fix is migration to another method I guess. Why in this age of agentic tools with optimized workflows? Idk, just testing it and like the ownership aspect of it.
For setup instructions please see SETUP.md
The current config is based on lazy.nvim.
<leader> is <space>.
<leader>ff find files, <leader>fg grep, <leader>e file tree, / search
with centered n/N, <leader>a select all, <leader><space> copy path.
01.mp4
<leader>| / <leader>- split, <C-hjkl> move, <C-arrows> resize,
<leader>H/J/K/L new edge buffer, <leader>ws swap mode, <leader>x close,
<leader>z close others.
02.mp4
<leader>t floating terminal that keeps running when hidden, <leader>ss save
session for the folder, <leader>sr restore it.
03.mp4
<leader>k show diagnostic, <leader>fm format, p paste without losing the
clipboard, Tab/S-Tab indent in visual mode, <leader>ci copy selection as
SVG.
04.mp4
<leader>ll live compile to Skim, <leader>lr grammar review (a accept, n
next), <leader>fm format and flatten $$ blocks.
05.mp4
<leader>lm render $$ formulas inline, re-renders on save.
06.mp4
<leader>ll live render HTML in the browser, reloads on save, again to stop.
07.mp4
MIT Do whatever you like.