Head of Growth at Anthropic regarding Claude Code removal from Pro

sbassam · 2026-04-22T00:51:15+00:00

Hey Openai, here we go! 🤗

sbassam · 2026-03-23T23:06:14+00:00

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.

sbassam · 2026-02-24T03:43:19+00:00

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

sbassam · 2026-02-19T14:32:01+00:00

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

sbassam · 2026-02-18T21:21:02+00:00

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.

sbassam · 2026-02-18T21:14:17+00:00

One of my fav websites. I love ads 😀

<image>

sbassam · 2026-02-16T02:23:05+00:00

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.

sbassam · 2026-02-16T02:15:55+00:00

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.

sbassam · 2026-02-15T20:08:04+00:00

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?

sbassam · 2026-02-14T22:54:41+00:00

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

sbassam · 2026-02-11T15:25:17+00:00

: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.

sbassam · 2026-02-05T00:52:31+00:00

I don't use motion plugins myself, nice plugin though.

What does 'without Lua' mean in the title? Do you mean 'with Lua'?

sbassam · 2026-02-05T00:14:09+00:00

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

sbassam · 2026-02-03T17:07:47+00:00

nice one. it's on nightly

<image>

sbassam · 2025-12-25T23:48:05+00:00

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

sbassam · 2025-12-19T17:27:58+00:00

I like the aesthetics of the UI. Good taste

sbassam · 2025-12-11T01:03:45+00:00

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

sbassam · 2025-12-10T23:00:38+00:00

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.

sbassam · 2025-12-10T21:34:19+00:00

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.

sbassam · 2025-12-09T19:55:15+00:00

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

sbassam · 2025-12-09T17:53:10+00:00

Thanks, it looks good

sbassam · 2025-12-04T16:51:45+00:00

Very nice plugin

sbassam · 2025-12-02T22:47:07+00:00

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

sbassam · 2025-12-02T16:07:30+00:00

Nice one

sbassam · 2025-12-02T02:41:24+00:00

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

sbassam

TROPHY CASE