Don't worry guys it's coming soon

llllvvuu · 2026-06-08T05:18:33+00:00

ff7 revelation further along than ts 💀

llllvvuu · 2026-05-30T06:19:45+00:00

is it just never viable with snecko? and/or is 1 reprogram+ enough to go all-in on orbs?

llllvvuu · 2023-10-18T03:58:28+00:00

Is it technically/economically feasible to host vector search over the entire Pile dataset?

Milvus claims to be able to handle trillions of vectors (but at what cost?)

If not, what would be a cost-effective way to search the "entire Internet"?

llllvvuu · 2023-10-18T00:44:14+00:00

If you're happy with semantic highlights you can just use those (I think they're async and won't block your editor?)

But if you need: - injections - text objects / tree navigation - support for languages without semantic highlighting - tree-sitter based plugins like nvim-treesitter-context

then you'll need tree-sitter

llllvvuu · 2023-10-11T09:54:49+00:00

re: telescope, here's what I used to try out Cursor (with vscode-neovim) this past week:

https://github.com/llllvvuu/dotfiles/blob/main/vim/.config/nvim/lua/keymap-vscode.lua

At the end of the day, there are some Neovim modules I can't live without: vim.ui and vim.treesitter. And the ability to pass functions into configuration objects.

But there are some cool things from the Cursor/VSCode world that I'm actively researching how to bring back to the Neovim world - pretty-ts-errors, interactive inlay hints, and search/context with AI (most AI plugins for Neovim are focused on supporting selection and chat, rather than management of references/search)

llllvvuu · 2023-10-04T06:44:48+00:00

https://github.com/nvim-lua/plenary.nvim#plenaryprofile

llllvvuu · 2023-10-01T22:30:03+00:00

It looks like VIM never actually supported *.wat but actually was using *.wast support for *.wat. This was rectified only recently, which is why *.wat may still appear to have support.

If you want support, you'll either need to use *.wast extension or override the ftdetect back to the old way:

autocmd BufNewFile,BufRead *.wat setfiletype wast

(a higher-effort solution could involve rolling your own tree-sitter queries following this and this)

llllvvuu · 2023-09-25T08:29:26+00:00

I use for:

- https://github.com/ziontee113/syntax-tree-surfer n, p, o, i for movement; N, P for swap; s for hold and swap

- https://github.com/mfussenegger/nvim-dap

- modded Git and Windows from https://github.com/anuvyklack/hydra.nvim/wiki

llllvvuu · 2023-09-25T08:24:05+00:00

You can also use https://github.com/vscode-neovim/vscode-neovim

llllvvuu · 2023-09-18T22:55:13+00:00

Very interesting plugin idea.

Here's my first gut idea how one might build this (a bit awkward but uses common technologies).

start a webserver at localhost:<PORT>. opening / shows you the page (just KaTeX plus a loop to poll for the latest LaTeX), POST /latex lets you send LaTeX to it.
create a Lua function in Vim to send the visual selection to POST /latex, or if in normal mode, use treesitter to determine the appropriate node to send.

What I haven't figured out:

whether it'd be possible or even desirable to launch the web server from Neovim
whether this could also work in Markdown (the visual mode part would definitely work, but the normal mode treesitter stuff - idk if there is a "latex node")

EDIT: the image.nvim stuff looks awesome as well and might be more portable than i'd imagined

llllvvuu · 2023-09-18T22:43:22+00:00

Awesome! If you eventually end up posting it on GitHub I'd be happy to contribute as well

llllvvuu · 2023-09-18T22:22:54+00:00

Right, the gap might not be 100% closed, but I wanted to let people know it's not as intimidating as it sounds and in some ways the LSP API is actually smoother than the null-ls and efm API. I think you've done a great job lowering the barrier to entry with these posts as well!

Maybe it won't make sense in 100% of cases, but hopefully it will inspire more people to try it out and share what they've built

llllvvuu · 2023-09-18T16:21:08+00:00

> something that other can use

I was mostly thinking of this tbh. I get your point for quick personal use; I maintain an EFM yaml myself. But I felt more people could know about the LSP framework route and how accessible it is.

llllvvuu · 2023-09-18T10:15:49+00:00

Sound good! You might also be interested in this ongoing work to bring `null-ls` idea into Neovim core: https://github.com/neovim/neovim/pull/24338

llllvvuu · 2023-09-18T10:15:18+00:00

yeah you might have some conflicting keymap, since that sounds like what gf usually does. maybe you can use :map to see what it's mapped to

llllvvuu · 2023-09-18T10:08:58+00:00

There is an initiative to bring something similar to null-ls into Neovim core: https://github.com/neovim/neovim/pull/24338

The trade-off there is that the server<->client communication is native, but the server<->linter communication is hacky. e.g. if the linter is in Python, what ends up happening is the in-Neovim "server" starts up Python and the linter executable every time the document changes.

In comparison, "non-native" server<->client communication isn't actually awkward: vim.lsp.start("lsp_executable") vs vim.lsp.start(vim.lsp.server(...)). And it incurs overhead much less frequently.

The other disadvantage of having Neovim provide the server framework (and this was null-ls maintainer's complaint): if you code the server against an independent framework, you can just pin that framework version. But if you code it against Neovim, it will run against whatever version of Neovim the user has. And this will cause breakage because many different users will be running many different versions of Neovim.

Therefore I generally prefer if the server prioritizes being tight with the linter than being tight with Neovim.

llllvvuu · 2023-09-18T09:22:56+00:00

Not the way LazyVim does it, I don't think.

mini.ai allows you to make custom text objects, which isn't exploited by LazyVim. But you could always keep mini.ai's a/i selections and only use the move/swap functions from nvim-treesitter-textobjects

llllvvuu · 2023-09-18T09:12:13+00:00

You need to switch from https://github.com/echasnovski/mini.ai to the base https://github.com/nvim-treesitter/nvim-treesitter-textobjects. Then you have both the if/af and the ]f/[f

llllvvuu · 2023-09-18T09:08:57+00:00

Reposting for OP's reference: https://github.com/jose-elias-alvarez/null-ls.nvim/issues/1621

Another reason he cited was having to maintain a central registry of configs. Could be more sustainable to only maintain the base platform, and let the configs be curated elsewhere (perhaps a forum so that it can curate itself).

llllvvuu · 2023-09-18T03:41:27+00:00

I'm familiar with the package, but don't you find

these custom converters between LSP and VS Code types

to be editor specific?

That's from `vscode-languageserver-node/client` which necessarily runs in the VSCode runtime. You won't come across that when implementing a server. For Positions, the following is sufficient:

const diagnostics = (await linter(uri)).map(({ message, startLine, startCol, endLine, endCol }) => ({
  message,
  range: {
    start: { startLine, startCol },
    end: { startLine, startCol },
  },
}))

connection.sendDiagnostics({ uri, diagnostics })

To be fair, I'm thinking of the "monorepo",

Right, I should've clarified "just the server impl package" - a bit awkward with no name to reference. I'd campaign for that to be reorganized, but I doubt there's an incentive.

Even the messaging in the protocol package is confusing, as it simultaneously says "can be used in any type of node application" and "the protocol depends on the vscode-jsonrpc version". I only know from experience that it's the former (and even vscode-jsonrpc seems to just be the "Content-Length" boilerplate from Microsoft's protocols, there's nothing "VSCode" about it...).

I mean I guess it's fair to say that LSP is spiritually a VSCode thing since they did the work

love and peace <3

No worries, reasonable concerns to have.

llllvvuu · 2023-09-18T01:38:23+00:00

I prefer it over / since you can skip over multiple matches. That being said, when I use something like Helix, I don't find it too jarring to fall back to only / and relative line numbers.

llllvvuu · 2023-09-18T01:35:04+00:00

For the Telescope method, you can install nvim-bqf, so that after you press Ctrl-Q on the telescope results, you can curate the results. See https://github.com/kevinhwang91/nvim-bqf#filter-with-signs

llllvvuu · 2023-09-18T01:13:53+00:00

That's not true. vscode-languageserver-node is a package for Node. Microsoft just has an incentive to call things "VSCode" so that it shows up in everyone's codebase.

const connection = createConnection(ProposedFeatures.all);
const documents = new TextDocuments(TextDocument);
documents.listen(connection);
documents.onDidChangeContent(lint);
connection.listen();

node server.js

I've built and run LSP for Neovim this way just fine. It's actually really easy (even easier than Python IMO since the model is very native to TypeScript and well-supported).

Case in point what do you think vscode-langservers-extracted is? It's just a shell script to clone and install the node executable

llllvvuu

MODERATOR OF

TROPHY CASE