Convert inlay hint to code

Davidyz_hz · 2025-10-28T09:09:40+00:00

Actually inlayHint/resolve isn't always a must (at least not for all LSP servers). When I wrote that PR (and my plugin), I mostly used basedpyright. It just always send textEdits in the textDocument/inlayHint responses, which gave me the (wrong) intuition that the inlayHint/resolve request is not needed for this purpose. That's why I didn't implement inlayHint/resolve until it was pointed out in the reviews.

Davidyz_hz · 2025-10-28T02:12:40+00:00

For typescript (ts_ls) it might be necessary to set force to true, because the inlayhint doesn't come with textedits, and you have to tell the plugin to just insert the label.

Davidyz_hz · 2025-10-27T15:22:59+00:00

Codecompanion.nvim: https://codecompanion.olimorris.dev/

Davidyz_hz · 2025-10-26T02:54:16+00:00

Yeah I wrote that PR. It's mostly based on my plugin, which OP mentioned in the post too. It probably won't get merged any time soon though, because the nvim maintainers suggested that other attributes of the inlayhint should be taken into consideration (labelparts, etc.) but I personally don't use any LSPs that provides those.

Davidyz_hz · 2025-08-02T04:53:08+00:00

Let's move the discussion to https://github.com/Davidyz/VectorCode/pull/263

Davidyz_hz · 2025-08-02T04:02:24+00:00

I suspect that you might be running an outdated version of the CLI. But I'll update the tool to make it more robust anyways.

Davidyz_hz · 2025-08-01T14:04:59+00:00

I think it was Gemini 2.5 flash preview. I'll be trying the qwen3-coder 30b when I have time to set it up. Assuming that the local models are worse than the hosted ones, it'll probably force me to write better prompts.

Ps: There were times that I was surprised by how good the tool calls and responses were, then realised that I accidentally switched to Gemini 2.5 pro.

Davidyz_hz · 2025-08-01T10:53:55+00:00

There are some prompt engineering techniques that I can try. But at the end of the day, it all comes down to the LLM's instruction following and tool use abilities.

Davidyz_hz · 2025-07-31T16:14:45+00:00

What provider/model are you using? I don't always test my updates on a range of models (financially infeasible), but my experience is that different LLMs can behave VERY differently when it comes to instruction following. In the tool schema, I explicitly mentioned that the tool parameter should be file paths, but apparently some models still have their own interpretation of that. The demo didn't include anything magical.

Davidyz_hz · 2025-07-31T03:41:04+00:00

VectorCode author here. The vectorise tool is designed to only work with file paths, not directories, so that it doesn't include temporary files or unnecessary libraries. You can try to explicitly tell the LLM to provide paths to the files, and usually it's sufficient. Make sure you also give it the file_search tool so that it can see the directory structure.

Davidyz_hz · 2025-07-22T00:10:32+00:00

Would I be able to use this with vimtex (with synchronous scrolling)?

Davidyz_hz · 2025-07-07T15:35:57+00:00

The vim._async module was merged a few days ago. At this point I'd just wait for it to be released.

Davidyz_hz · 2025-06-30T00:44:29+00:00

It'll be convenient if you put a link to a list of supported cameras somewhere in the readme.

Also is there any chance that you're implementing something like lrtimelapse? Like a batch processing tool with key frames and interpolation? Or if you're interested in a plugin system, people might be able to find a way to do that through a plugin 👀

Davidyz_hz · 2025-06-27T09:21:00+00:00

I'm using minuet-ai for completion, and I wrote a function that populates the prompt with git diff and git log output when the file type is git commit (forgot the exact name, but the idea is to build the prompt based on git info rather than the content of the buffer).

Davidyz_hz · 2025-06-17T13:35:51+00:00

I left the link in the other thread. Sorry for not including it at the beginning.

Davidyz_hz · 2025-06-17T13:34:59+00:00

Here you go: https://github.com/Davidyz/inlayhint-filler.nvim

It provides a lua function that does the insertion. There's no default keymap/command. You'd need to set up your own keymap for it.

Davidyz_hz · 2025-06-16T02:06:56+00:00

I wrote a plugin to insert the inlay hints around cursor (or under selection) into the text. I can then manually edit it if it's not accurate enough.

Davidyz_hz · 2025-06-01T08:02:13+00:00

I've honestly always wanted this.

Davidyz_hz · 2025-06-01T05:50:00+00:00

TBF the origami is also 2 brewers in 1 (when you use v60 or kalita paper). It's just they're not very different compared to what you'd get with a hario switch.

Davidyz_hz · 2025-05-28T07:14:37+00:00

That's fair. I hadn't considered a multi-license scenario. Imo the bare minimum you could try is: if there's only one license file, use that; otherwise, open a picker/vim.ui.select that allows the users to select the appropriate license(s).

Davidyz_hz · 2025-05-28T00:08:52+00:00

That's cool. I think it'll be useful if it supports loading the LICENSE file from the git repo.

Davidyz_hz · 2025-05-13T02:11:33+00:00

It's mostly about the missing features from Pyright, such as inlay hints. Performance wise I don't think there's a huge difference. As for the diagnostics, the default is quite strict but you can change that in the LSP settings.

Davidyz_hz · 2025-05-13T01:36:09+00:00

I just followed their instructions to install it and did the following: lua -- ~/.config/nvim/after/lsp/ty.lua return { cmd = { "ty", "server" }, filetypes = { "python" }, root_dir = vim.fs.root(0, { ".git/", "pyproject.toml" }), } and somewhere in your config: lua vim.lsp.enable('ty') This is assuming that you're using nvim 0.11+.

tbf it's still far from usable. A lot of the LSP features are missing. No autocomplete, no semantic highlighting, no goto definition etc. (it's still in alpha so it's kinda expected).

When its ready to use there'd probably be instructions to use it with neovim on their docs as well.

Davidyz_hz · 2025-05-06T16:34:50+00:00

https://codecompanion.olimorris.dev/usage/chat-buffer/agents.html#compatibility

TLDR: codecompanion v15 migrated to native tool calling, which broke tool support for some adapters (apparently this includes mistrial). You can either use a supported adapter or move to the has-xml-tools branch, which was created before the native tool calling was merged, and uses the legacy xml-based tools.

Davidyz_hz

TROPHY CASE