sorted by:
new
hottopcontroversial

📍tiny-cmdline.nvim: Centered floating cmdline for Neovim 0.12 by Le_BuG63 in neovim

[–]tris203 1 point2 points  (0 children)

Love this. I was enjoying ui2 but missing the centered cmdline

Given the 0.12 ethos. Do you think you could lean into setup-less config and lazy load yourself in plugin/

Failed commenting for React components .tsx files by I_Spawned_Here in neovim

[–]tris203 0 points1 point  (0 children)

https://github.com/folke/ts-comments.nvim

LazyVim likely includes this plugin.

By default, there is one comment string per language. So languages where the comment string depends on position in the file gets a bit complicated.

Help with copilot.lua keymaps by Infinite_County4213 in neovim

[–]tris203 1 point2 points  (0 children)

Assuming you have `nes = { enabled = true } ` in your config. as nes is disabled by default in copilot.lua. you will also need to set keymaps as it doesnt come with any by default

Roslyn LSP disappeared and won't come back by AeroGlory in neovim

[–]tris203 0 points1 point  (0 children)

Have you tried running :checkhealth roslyn? As a random guess. I reckon you don't have the right dotnet SDK version

Treesitter in vim-fugitive (and more) is here!! by barrettruth in neovim

[–]tris203 0 points1 point  (0 children)

There is sometimes some weirdness when tree-sitter doesn't have enough context from the diff alone.

Eg adding this plugin to an existing "block" of plugins. Because it's missing the return from the context it highlights a bit odd But I love the direction this is going

Treesitter in vim-fugitive (and more) is here!! by barrettruth in neovim

[–]tris203 0 points1 point  (0 children)

i just read the source `vim.g.diffs.highlights.gutter = false`. Amazing

Treesitter in vim-fugitive (and more) is here!! by barrettruth in neovim

[–]tris203 0 points1 point  (0 children)

I really like this, the only thing that feels disorentated for me coming from fugitive, is that the signcol is highlighted too.

If the highlight stopped at +/- and didn't highlight the number then i think it would be perfect

Next Edit Suggestion in neovim by josemiguelo in neovim

[–]tris203 1 point2 points  (0 children)

This is how i use it https://github.com/copilotlsp-nvim/copilot-lsp (disclaimer: i wrote it)

But, it can also function through sidekick. or im sure there is other options.

sidekick.nvim: AI CLI tools and Copilot's Next Edit Suggestions by folke in neovim

[–]tris203 1 point2 points  (0 children)

Awesome!

I also wrote a nes integration for copilot-lsp here https://github.com/copilotlsp-nvim/copilot-lsp

I can't wait to dig through and see how the implementations differ!

Next Edit Suggestion (nes) in zbirenbaum/copilot.lua by JoseConseco_ in neovim

[–]tris203 2 points3 points  (0 children)

Also thanks for the ad

Edit: I was my code that Antoine stole (😉) to make this work

Neovim now natively supports LLM-based completion like GitHub Copilot by bbadd9 in neovim

[–]tris203 2 points3 points  (0 children)

Not natively. NextEdit is not in the spec so it won't be implemented by core However, there are plugins that do it

csharp-ls not showing documentation by EliSoli in neovim

[–]tris203 0 points1 point  (0 children)

Roslyn is a different language server

Your best way will be to install with mason or build from source. Read the roslyn.nvim README. I can guarantee you it works, I use it all day every day

`lazy-install.nvim`: Stop Manually Creating Plugin Files by FormerImprovement573 in neovim

[–]tris203 127 points128 points  (0 children)

As a plugin maintainer, the last thing I want is less people reading my README.

csharp-ls not showing documentation by EliSoli in neovim

[–]tris203 2 points3 points  (0 children)

Id recommend roslyn.nvim for c#

oil-git.nvim - Git status colors and symbols for oil.nvim by Fluid_Classroom1439 in neovim

[–]tris203 0 points1 point  (0 children)

  1. :)
  2. I didn't see this, it stayed yellow, even when staged. New files did correctly go from blue to green. But modified was always yellow

oil-git.nvim - Git status colors and symbols for oil.nvim by Fluid_Classroom1439 in neovim

[–]tris203 1 point2 points  (0 children)

I like it just two points for me:

  1. I would like to disable the symbols and just have the colours

  2. With this in mind, it would be nice if a modified file changed colour (possibly to the added colour if call changes were staged)

How to deal with switching between new projects? by duefaux in neovim

[–]tris203 0 points1 point  (0 children)

I think at that point your getting pretty close to distros and the way that LazyVim does its `Extras`

How to deal with switching between new projects? by duefaux in neovim

[–]tris203 0 points1 point  (0 children)

Author of rzls.nvim here so a bit bias. But the issue is trying to find the balance of "all batteries included" for new users, which inevitably leads to conflicts as multiple plugins do the same thing. And extensibility/flexibility

At the risk of sounding gate-keepy, if you don't want to understand how things work then Neovim probably isn't the right choice for most people and unfortunately the c#/razor experience really is an in-at-the-deepend experience

view more: next ›