barrett/barrettruth.com
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(cp.nvim): typos

Browse source
This commit is contained in:
Barrett Ruth 2025-09-22 08:11:53 -04:00
parent 6396124fd1
commit f068643354
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
src/content/posts/software/cp.nvim.mdx
View file

@ -12,7 +12,7 @@ Things have changed since I last documented my competitive programming setup [he
After many months of using the aforementioned `make` based setup, I had a few qualms:
- <u>I'm lazy</u>: I grew tired of copying (and mis-copying) inputs, outputs, etc from online judges.
- <u>I'm lazy</u>: I frequently submitted incorrect problems after erroneously asserting that my outputs matched those of the sample test cases
- <u>I'm lazy</u>: I frequently submitted incorrect solutions after erroneously asserting that my outputs matched those of the sample test cases
- <u>External dependencies</u>: it unsettles me that my bare-bones setup required copy-pasting an entire suite of scripts
- <u>Non-native NeoVim experience</u>: while composition and the UNIX philosophy are great, there's only so much you can do with pipes and files.
- Raw I/O files meant I couldn't see colored stdin/stdout
@ -34,12 +34,12 @@ The GitHub page documents the plugin well enough so I'll avoid re-hashing it her
- Proper versioning, tagging, and releases
2. <u>The Neovim Community</u>: I'm elated to finally give back to the community (even if no one uses this plugin). [folke](https://github.com/folke), [bfredl](https://github.com/bfredl), and [echasnovski](https://github.com/echasnovski) are my greatest inspirations as an open-source developer and I've had enough of taking without giving back.
- In the coming months I plan to contribute to [NeoVim core](https://github.com/neovim/neovim), including making `:checkhealth` asycnhronous and integrating an [mdx](https://mdxjs.com/) parser.
- In the coming months I plan to contribute to [NeoVim core](https://github.com/neovim/neovim), including making `:checkhealth` asynchronous and integrating an [mdx](https://mdxjs.com/) parser.
3. <u>Learning Random things</u>: I think this plugin is *really* cool by virtue of its efficacy and the miscellany of knowledge I accrued in the 15k+ LOC as of version v0.3.0. Some things I learned include:
- <u>ANSI terminal colors and escape codes</u>: I wrote my own stateful ANSI escape sequence parser to map raw bytes to native NeoVim highlighted text
- <u>Extmarks</u>: NeoVim extmarks (`:h extmarks`) are extremely powerful. Here, I used them to apply dynamic highlighting across various components of the plugin but I also plan to leverage virtual text to catch compile errors in real-time
- <u>VIM filetypes and diffing</u>: Vim is strange and the event-based system is fragile. I faced filetype detection race conditions and odd side effects of functions (such as `:diffthis()` resetting `foldcolumn`).
- <u>VIM filetypes and diffing</u>: Vim is strange and the event-based system is fragile. I faced filetype detection race conditions and odd side effects of functions (such as `:diffthis` resetting `foldcolumn`).
- <u>[LuaCATS](https://github.com/LuaCATS)</u>: apparently writing comments is the best way to typecheck in lua...
- <u>The (Neo)Vim event loop</u>: scraper subprocesses spawned with `vim.system`. Though a powerful API, I often had to obey the event loop and wrap side effects with `vim.schedule` to ensure they ran after jobs finished. This was useful to defer UI updates.
- <u>The (Neo)Vim event loop</u>: Scraper subprocesses spawned with `vim.system`. Though a powerful API, I often had to obey the event loop and wrap side effects with `vim.schedule` to ensure they ran after jobs finished. This was useful to defer UI updates.