From 6475b91999702c3ecc25604bd2b2fad9c7f3f490 Mon Sep 17 00:00:00 2001 From: Kleidi Bujari Date: Fri, 17 Jan 2025 17:13:35 -0500 Subject: post vimcompilers --- mod/web/blog/content/posts/vim-compilers.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 mod/web/blog/content/posts/vim-compilers.md (limited to 'mod/web') diff --git a/mod/web/blog/content/posts/vim-compilers.md b/mod/web/blog/content/posts/vim-compilers.md new file mode 100644 index 0000000..f735228 --- /dev/null +++ b/mod/web/blog/content/posts/vim-compilers.md @@ -0,0 +1,20 @@ +--- +title: "Neovim's built-in compilers" +date: "2025-01-17" +--- + +Today I learned that neovim's `:make` comes with many +[backends](https://neovim.io/doc/user/quickfix.html#_6.-selecting-a-compiler) +already configured. +This works for checking c/cpp and python files, among other, but I was +most interested to see [Typst] and [Pandoc] listed as well. + +I was looking to add this functionality with a plugin or implementing it +manually, +where a document can be compiled on the fly from the editor. +After setting `:compiler pandoc`, +generating a pdf is done with `:make pdf`, +with other pandoc options just appended afterwards if needed. + +[typst]: https://typst.app +[pandoc]: https://github.com/jgm/pandoc -- cgit v1.3.1