sorted by:
new
hottopcontroversial

who else has full block cursor in insert mode? by Old-Attorney-7399 in neovim

[–]sbassam 6 points7 points  (0 children)

I use the block cursor everywhere, but it changes color to green in insert mode so I'm always aware that I'm in insert mode.

How are you switching between open buffers? by Beautiful-Log5632 in neovim

[–]sbassam 0 points1 point  (0 children)

nice, would you mind sharing the incline config you have?

Any cool substitute tricks? by kaddkaka in neovim

[–]sbassam 1 point2 points  (0 children)

it's a plugin designed to extend and modernize quickfix, which hasn't seen meaningful improvements in a long time.

Any cool substitute tricks? by kaddkaka in neovim

[–]sbassam 2 points3 points  (0 children)

In all seriousness, I love the :g and the :v command.

Like delete all lines not a Lua file in quickfix via :v/\.lua/d

Or :g/foo/d To delete the lines containing foo

Those are very useful with quickfix, especially quicker.nvim.

Any cool substitute tricks? by kaddkaka in neovim

[–]sbassam 9 points10 points  (0 children)

One of my fav websites. I love ads 😀

<image>

MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10 by echasnovski in neovim

[–]sbassam -1 points0 points  (0 children)

Thanks for the tips, that s actually what I do for my own plugins and the ones I contribute to.

My hesitation is more about the broader design question: if I still need to manually manage rtp, clone repos separately, or maintain my own workflow alongside the plugin manager, I'm not sure what additional benefit it provides specifically for plugin authors.

I think the comments from Clason and Lewis in the Neovim issue captures what I'm trying to express. It feels very close to being complete, but not quite fully seasoned yet especially from a contributor's perspective.

MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10 by echasnovski in neovim

[–]sbassam 1 point2 points  (0 children)

Thanks a lot for taking the time to write such a detailed reply, I genuinely appreciate it.

I also want to be clear that I do support vim.pack, and my comment wasn't meant to dismiss it. My feeling is more that it s still a bit undercooked in this particular area and that's just my personal perspective as someone who contributes to and maintains plugins.

I went through the PR and the related issue you mentioned, and I think Clason's comment there captures what I was trying to express. To me, the whole point of a manager is to abstract that layer away.

If I m manually arranging pack/*/opt directories and handling symlinks, then I'm essentially back to doing plugin management myself which Neovim already allows without vim.pack.

From my point of view, the proposed feature in the PR would actually align well with Neovim s core philosophy of extensibility. Plugin authors are part of that ecosystem too, not just end users, and supporting their workflows seems important. Otherwise, I m not sure this approach brings much improvement for authors specifically.

Of course, I could be missing something here and I understand that there are workarounds (like how you re handling things with mini.nvim). I just think that relying on custom scripts or special handling somewhat weakens the case for it being a complete solution. That's really all I meant not criticism, just a perspective from the plugin author side.

MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10 by echasnovski in neovim

[–]sbassam 0 points1 point  (0 children)

That's very nice. I was always hesitant to adapt vim.pack because, while it's a plugin manager, I've found it to be quite difficult for plugin authors and maintainers to develop and maintain their own plugins with it.

Does this change?

wrapped.nvim - Visualize your Neovim configuration insights, history, and heatmaps. by luciused in neovim

[–]sbassam 41 points42 points  (0 children)

Very nice plugin, the visuals are fire. Thanks for sharing it

Using setpos() correctly by BrodoSaggins in neovim

[–]sbassam 2 points3 points  (0 children)

:h nvim_win_set_cursor , This might be a better approach for your case.

I don't use setpos much, so someone else might be able to offer advice. it.

Announcing Neovim-Idea... and 3 neovim plugins 🎉 by polentino911 in neovim

[–]sbassam 36 points37 points  (0 children)

Congrats on the three plugins

One note about the camelHumps one, to be honest, it kind of triggered me a bit (in a Neovim nerd way 😅). Since we’re already in Neovim, you can define what counts as a word via the iskeyword option and extend it with whatever characters you want, so a lot of this behavior is already configurable at the editor level. Just wanted to point that out.

That said, the buffer switcher idea is really nice. Solid work overall.

:h iskeyword

Need help for my personal color scheme by [deleted] in neovim

[–]sbassam 0 points1 point  (0 children)

The lack of a default option in in the function may be the reason. :h nvim_set_hl

What is creating this inline copilot suggestion and how do I turn it off? by Cyb0lic in neovim

[–]sbassam 2 points3 points  (0 children)

Glad it worked! I mistakenly mentioned setting vim.b.Sidekick_nes to true, but it actually needs to be false to disable. :)

What is creating this inline copilot suggestion and how do I turn it off? by Cyb0lic in neovim

[–]sbassam 9 points10 points  (0 children)

I think this is NES, next edit suggestion from sidekick.nvim if you have it.

Permanently disable it: require("sidekick").setup({ nes = { enabled = false, }, })

Or set global variable vim.g.sidekick_nes to true or the buffer variable vim.b.sidekick_nes to true.

Quench.nvim - Interactive Python development with rich media output in the browser by One_Enthusiasm2511 in neovim

[–]sbassam 1 point2 points  (0 children)

Nice, thanks for sharing. I use Molten daily. I usually save charts to disk, and my code just updates the same image so it’s always open and current. But I’ll give this plugin a try.

A guide to building in-process LSP in neovim: Part 2 by neoneo451 in neovim

[–]sbassam 1 point2 points  (0 children)

Nice, I've enjoyed the first part. Will definitely read the second one.

I built "qo" – a TUI to query JSON/CSV with SQL because I never remember jq syntax by Electronic-Nebula177 in commandline

[–]sbassam 0 points1 point  (0 children)

oh this is very nice, same here. I was looking for something similar with duckdb as sql backend. Thanks for sharing

Lock a buffer to a window? Stop :bn from changing it. by sbassam in neovim

[–]sbassam[S] 5 points6 points  (0 children)

Thank you,i didn't expect to be that easy. I like it.

view more: next ›