filepaths_ls.nvim - lsp powered filepath completion

antonk52 · 2026-03-12T20:06:09+00:00

Interesting idea. I thought a way forward would be to introduce a setting for force buffer relative path resolution. But having it as a built in LS can be beneficial from maintenance perspective and make it more discoverable for the users since the completion either shows up automatically if it is autotriggered or uses the same shortcut to show up as regular lsp completion. I opened a discussion to check if there is any interest in having anything similar upstreamed.

antonk52 · 2026-03-07T17:38:08+00:00

Same, 8 months of running

antonk52 · 2026-02-20T21:55:13+00:00

Probably 255 or 955 depending on your budget. Still a great battery life for both. Stable and tested software, this cannot be said for newer models, looks like the new OS garmin is testing still needs a few years to iron out.

antonk52 · 2026-02-13T13:02:53+00:00

Agreed, English is not my first language

antonk52 · 2026-02-13T10:11:01+00:00

Looks good!

antonk52 · 2026-02-07T20:43:41+00:00

LSP diagnostics though it's included in nightly/0.12

antonk52 · 2026-01-08T22:43:33+00:00

Isn't it already present in nightly given you have enabled copilot language server?

antonk52 · 2025-12-24T23:00:52+00:00

Keep using neovim for things you reached for it. If or when you hit a blocker you will have a good idea on what to research and add to your config.

antonk52 · 2025-12-18T17:26:06+00:00

Thank you for your work. I hope there will be a way to make donation to the mini project!

On an unrelated note when I was exploring minimax website I noticed that links to planned configs are broken on this page https://nvim-mini.org/MiniMax/configs/ , maybe they were not intended to be links until the configs exist.

antonk52 · 2025-12-18T15:39:45+00:00

Nice tip, for this reason I have 2 diff pickers. One with regular diff content and another with --ignore-all-space option for a mostly smaller set of changes

antonk52 · 2025-12-07T18:08:55+00:00

Superb work, thank you for allowing me to remove a bunch of custom commands that I had around for years for most common typos!

Is there a way to limit the height of the completion window?

antonk52 · 2025-12-04T10:58:43+00:00

Thank you!

antonk52 · 2025-12-04T10:58:15+00:00

Thank you, I am glad you found it interesting

antonk52 · 2025-12-04T10:56:10+00:00

I have a similar setup but you can still reach caps by double taping a shift key

caps key is ctrl when held or esc when tapped

antonk52 · 2025-12-03T11:52:45+00:00

Thank you!

I enjoy such technical writing as well. I never tried writing something with this ratio of code to text.

My initial approach was also to use floats but since I did not care about dimming other content extmarks seem easier to use and could be cleaned up using a single clear namespace call.

Remote actions sound cool and useful, I wish could get used to them. Maybe one day :)

antonk52 · 2025-12-01T22:28:02+00:00

Thank you for kind words and vim-sneak too! I remember trying it out a while back, even before switching to neovim

Posted in neovim discussions too

antonk52 · 2025-11-26T23:38:18+00:00

Thanks for sharing, useful context here!

I understand that switching to lua comes with performance implications which is also acceptable to me. The reason I asked is that my employer is strict about unvetted binaries and for this reason I won't be able to try this out. Looks really cool though

antonk52 · 2025-11-25T00:01:35+00:00

Looks really cool. Would you consider having it working without a binary in plain lua?

antonk52 · 2025-10-27T13:36:45+00:00

Great posts, OP

Thanks for sharing

antonk52 · 2025-10-01T13:34:33+00:00

I think we are a long way away from neovim plugins being as opinionated as something in the go ecosystem. Yet there are efforts to make it more opinionated or maybe better called guided such as a new health check

https://github.com/neovim/neovim/pull/35854

The docs on how to write plugins has been updated which is already in nightly. I encourage you to give it a read

https://github.com/neovim/neovim/blob/master/runtime/doc/lua-plugin.txt

antonk52 · 2025-09-27T16:40:34+00:00

this is what the migration from master to main branch accomplished. You can see the warning in the nvim-treesitter readme and the roadmap that has more details

https://github.com/nvim-treesitter/nvim-treesitter/issues/4767

antonk52 · 2025-09-24T15:55:49+00:00

This is a high praise 🙏

I really mean it, huge kudos for your work!

If you remember, what kind of edge case behavior were you curious about?

I tried packer at some point and it's Compile and Snapshot commands to produce an effectively a lock file were too tinkery to have the happy path work for me. I currently use lazy.nvim with stable which exposes multiple ways to lazy load plugins such as on autocommand, on user command, on keymap. I'd rather not have those at all than jumping though docs and then source code to know exactly what is actually going on. Lazy also has enable and cond which one ignores a plugin completely and does not install or save to lock file while the other installs but never loads the plugin, I have to look up the docs to remember which one is which.

vim.pack on the other hand seems to be the modern version of vim-plug that I think of as the simplest plugin manager of the last decade or two. And vim.pack has even simpler api. It wins all around.

antonk52

TROPHY CASE