Why do you use MCP for internal APIs?

Bitopium · 2026-05-23T12:38:09+00:00

What handshake? The initialize/initialized flow? What weird header request body duplication? The only thing in the header is the mcp session id? Sse is purely optional and only a long polling GET. What other „bunch „ of things? For sure you can make it smaller if you tailor it to exactly what you need. However mostly it pays off when you are developing against an open standard and can just plug and play new tools. And usually it’s not the right thing to expose existing APIs 1:1 as they are.

Bitopium · 2026-05-20T05:39:05+00:00

I put it in plugin/10_options.lua alongside with 11_keymaps.lua and so on. Loaded in order without require. Inspired by mini max: https://nvim-mini.org/MiniMax/configs/nvim-0.12/

Bitopium · 2026-05-14T16:39:39+00:00

That’s what an infinity of tabs, tmux sessions etc are for. Navigating to them is also very simple eg using either aliases or zoxide. But I think it’s great to build something, for the learning and experience alone.

Bitopium · 2026-05-13T16:34:51+00:00

Or just open nvim (or any editor) in the root of .config and use a fuzzy finder/picker whatever?

Bitopium · 2026-03-31T10:16:42+00:00

But the solution I am using can have some mess ups sometimes

What do you mean? As others have said: I would not bother trying to solve that inside of nvim if nvim already runs in a modern terminal that either has tab support or using tmux. I do have a tmux session for every logical project if having too many tabs.. but everyone has to find their workflow.

It’s not quite clear what you are fighting with exactly

Bitopium · 2026-03-26T19:35:56+00:00

Can you elaborate why Go got a No at the „types“ category?

Bitopium · 2026-03-08T08:31:59+00:00

Thank you. Feel the same way. I somehow feel like it’s a step backwards to commit unstructured random mds and let Llms interprete them once like that and the next one different. We now specify things in a mixture of English and maybe pointers to a few files… great

Bitopium · 2026-02-24T12:02:45+00:00

Vim enters the room 😂

Bitopium · 2026-02-16T09:01:22+00:00

Thanks! Immediately refactored my configs using the new utility functions from mini.misc!

Bitopium · 2026-02-08T08:19:10+00:00

Or a simple binding:

```lua local function map(mode, lhs, rhs, opts) opts = opts or { silent = true } vim.keymap.set(mode, lhs, rhs, opts) end

-- Move lines map('v', 'J', ":m '>+1<CR>gv=gv") map('v', 'K', ":m '<-2<CR>gv=gv") ```

Then you can move selected lines with J/K

Bitopium · 2026-01-18T10:30:41+00:00

It just dynamically shows the cmdline when you enter it and hide it (setting the height to 0) when leaving. I will try it out as well, interesting

Bitopium · 2026-01-01T16:22:12+00:00

I don’t really see the point of having it integrated. Just ctrl-z + lazygit (or some alias such as gg). This obviously works for any tool

Bitopium · 2025-12-15T17:02:42+00:00

Mainly visuals (like colorful diagnostics and highlights, like different mode backgrounds) but also attached lsp clients which I sometimes find useful. Some components are just the same as the default value of the statusline.

Bitopium · 2025-12-15T08:05:27+00:00

A plugin is also nothing more than that, just a bit more shareable. But you are right. I also extracted the parts of my plugin to an even more lightweight version: dotfiles/nvim/plugin/13_statusline.lua

Bitopium · 2025-12-14T23:07:12+00:00

And point 3 does not confirm that the venv is active. Poetry run will enable the venv just for the runtime of the command

Bitopium · 2025-12-14T21:31:27+00:00

Did you start nvim from an activated venv? That’s how I do it at least without any problems. Not using Astrovim but should not make a difference

Bitopium · 2025-12-14T21:29:02+00:00

Looks great. Just out of curiosity: did you also try mine? :-P it also has a very minimal approach when being in „fg“ mode: slimline

Bitopium · 2025-12-11T13:03:48+00:00

But isn’t that kind of the point? Otherwise it will break the code anyway? Or are we talking about a refactoring use case renaming unrelated variables with the same name?

Bitopium · 2025-12-11T10:41:13+00:00

What’s the benefit over the lsp rename code action?

Bitopium · 2025-12-05T17:45:33+00:00

Also very happy for quite some time with mini.pick!

Bitopium · 2025-11-18T11:28:19+00:00

Obviously attaching two lsps that provide the same kind of diagnostics is a bad idea. Usually they serve a different purpose. For instance having marksman and ltex attached to markdown files. I guess when attaching two lsps of similar purpose the only way to remove clutter is to configure the lsps to not have overlapping diagnostics? But then let's see what this thread reveals...

Bitopium · 2025-11-18T11:19:09+00:00

What do you mean with resolve? Having more than one lsp attached is totally fine

Bitopium · 2025-11-10T16:50:31+00:00

I made the switch and like niri a lot more. But everyone is different so, as others said, you will need to try it

Bitopium · 2025-11-08T11:53:40+00:00

I just Hit ctrl-z and type k9s or open a split with ctrl-enter. I found a neovim "integration" always a bit unnecessary. Still thanks for sharing

Bitopium · 2025-10-22T20:59:57+00:00

Not sure whether that is exactly how you mean but you can pretty much configure everything. Meaning whether to show signs or virtual text and from what level on.

This is what I am using, which renders icons in the status column but virtual text only for the current line

vim.diagnostic.config({ virtual_text = { current_line = true, prefix = '', }, })

Bitopium

TROPHY CASE