summaryrefslogtreecommitdiff
path: root/weblog/better-current-word-search-vim.md
diff options
context:
space:
mode:
Diffstat (limited to 'weblog/better-current-word-search-vim.md')
-rw-r--r--weblog/better-current-word-search-vim.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/weblog/better-current-word-search-vim.md b/weblog/better-current-word-search-vim.md
index fa06126..44cc443 100644
--- a/weblog/better-current-word-search-vim.md
+++ b/weblog/better-current-word-search-vim.md
@@ -2,6 +2,8 @@
post_date: 2022-07-03
---
+> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp`
+
# Better current word search in vim
I noticed something when I was refactoring my vim configs for the Nth time last week, which [I wrote about in a bit more detail here](./neovim-lua.md). It's a bit of vim configuration that I've been copying forward without thinking about it for years and years, never even remotely considering pruning it because it's so useful. I also came up with it myself but havne't ever really put any effort into sharing it, so here we are.
@@ -24,5 +26,3 @@ The mappings above copy that behavior (perform it as you would do it directly, e
You see by the default naive cword search, any larger words which fully contain your search term would also show up as results. Try searching for a single letter variable that way and you'll have a bad time.
I think of this as a fantastic example of the utility of programmatic configuration (the sort that's made all the more powerful by using lua over VimL) - you're free to make the editor better in a hundred minor ways to smooth out your editing workflows, and in a way which is itself very much like maintaining code: build yourself a useful abstraction and don't have to think about it too much any more.
-
-> Note: This was ported from my old gemini capsule, still served on gemini at `gemini.ctrl-c.club/~tjp`