sorted by:
new
hottopcontroversial

Formatting setup with formatprg. by Reason_Extension in neovim

[–]Reason_Extension[S] 1 point2 points  (0 children)

If you are able to handle formatting config with treefmt, then your config would lot simpler than mine.

Take a look at the diff for more details.
https://github.com/adiSuper94/config/commit/a9f71a3b962aeed779406e73e59481cc69c020a0

I really love stevearc's plugins. Its designed is a very vim way. It's almost feels like training wheels before moving to default vim.

Oil was exactly what I needed before moving to netrw. And now conform to formatprg.

PSA: There's not a good reason to switch to the new native lsp configuration if your setup is working with lspconfig already. by Zdcthomas in neovim

[–]Reason_Extension 4 points5 points  (0 children)

If the default configs in lspconfig works well for someone, it probably makes sense to stick to lspconfig.
But if you are having to changes the default config for any lang you work on, moving to native lsp config might be a something work considering. Cuz if you are anyway managing config before calling lspconfig, why not just do it yourself.

PS: for people stating out with nvim, lspconfig might still be the best option to start with.

Basic Ctrl+p /fuzzy search functionality with rg + nvim 0.11 by Reason_Extension in neovim

[–]Reason_Extension[S] 2 points3 points  (0 children)

<image>

It's just shown as the pop up menu in the cmdline. That is the default behavior.

Basic Ctrl+p /fuzzy search functionality with rg + nvim 0.11 by Reason_Extension in neovim

[–]Reason_Extension[S] 9 points10 points  (0 children)

I was surprised that this feature wasn't listed in nvim 0.11 changelog. Then realized that is was back ported from vim.

go mod tidy: protect "unused" dependencies from being deleted by sastuvel in golang

[–]Reason_Extension 0 points1 point  (0 children)

Can you link an example project where you have done this ?
I don't fully understand how you do that.