From e4d08ebda11a2eecdae8d5c467bd323007c3c1a9 Mon Sep 17 00:00:00 2001 From: Barrett Ruth Date: Tue, 30 Sep 2025 18:33:11 -0400 Subject: [PATCH] fix(software): correct link --- src/content/posts/software/cp.nvim.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/posts/software/cp.nvim.mdx b/src/content/posts/software/cp.nvim.mdx index aafe481..fb2f6ea 100644 --- a/src/content/posts/software/cp.nvim.mdx +++ b/src/content/posts/software/cp.nvim.mdx @@ -20,7 +20,7 @@ After many months of using the aforementioned `make` based setup, I had a few qu The solution was to leverage Neovim's great APIs to give me granular control over every aspect of my problem-solving experience. -# the solution: [cp.nvim](http://localhost:4321/posts/software/my-cp-setup.html) +# the solution: [cp.nvim](https://barrettruth.com/posts/software/my-cp-setup.html) The GitHub page documents the plugin well enough so I'll avoid re-hashing it here. Instead, what's more interesting to document is why I thought this was a worthwhile experience.