https://github.com/benlubas/advent_of_code_2024
aoc in neovim commands (or rust or q) depending on how impossible it is to do with neovim commands
https://github.com/benlubas/advent_of_code_2024
Last synced: 2 months ago
JSON representation
aoc in neovim commands (or rust or q) depending on how impossible it is to do with neovim commands
- Host: GitHub
- URL: https://github.com/benlubas/advent_of_code_2024
- Owner: benlubas
- Created: 2024-12-01T14:17:11.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2024-12-01T18:28:22.000Z (6 months ago)
- Last Synced: 2025-03-19T01:46:02.142Z (3 months ago)
- Size: 1.95 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# advent_of_code_2024
## what
See [last year's repo](https://github.com/benlubas/advent_of_code_2023) for some deeper commentary
and explanation. Here's a brief description of what I'm doing:
I'm solving these problems by opening the input text in a neovim buffer and then manipulating the
text in the buffer until only the answer remains. I then write these commands to a plaintext file.
And I can source the file after opening the input text buffer and it will run them automatically and
produce the result.
These exact commands might not work for you. I'm using noice.nvim which deals with the press enter
menu, which I think causes things to fail. I also don't always use `:norm!` sometimes I use `:norm`
which means that remaps can cause issues.
I'm allowing simple `eval` calls, but I'm not going to use full on vimscript or lua. Mostly I use
`:norm!`, `:let` to "record" macros to registers that I later play, and `:s` for substitutions. But
of course other `:` commands are fair game as well.
## why
It's fun, and it gets funny reactions from people.