swarn

> Maybe we should get some benchmarks I'm happy to do some benchmarking. What numbers are you looking for? Given that the rule callbacks are only called for visible tokens,...

Easier side question: what's a good name/behavior for a command to print a table of current rules? `:LspRuleInfo` in a pop-up?

> I still miss a couple of concrete use-cases where I'd feel like "Oh yes, I'd want that". > I don't care about highlighting much myself, so I mainly see...

Some examples: My current clangd setup Note that I have not bothered to put this inside an `LspAttach` autocommand. But this is a complete setup! In `init.lua`: ``` lua local...

There are many questions and points made in the last few messages, I hope it's OK if I respond to them piecemeal! Why provide a way to disable token highlighting?...

+1 from me on this. My Telescope appearance on iterm2:  My Telescope appearance on Neovide:  This...

Huh, that's weird. It's consistent with the original implementation: ...which doesn't mean that the behavior is desirable. I'll have to dig in deeper.

The root cause of this is that `fzy` adds varying bonuses to letters at the beginning of words. However, the word boundary is not your typical regex `\b`. It's only...

Second point first: I've been on HEAD forever. I only installed `render-markdown` a few days ago, unrelated to the release of 0.11. Later today, I will try to bisect to...

With that additional info, a new `minimal.lua` without `nvim-treesitter`: ```lua for name, url in pairs { "https://github.com/MeanderingProgrammer/render-markdown.nvim", } do local install_path = vim.fn.fnamemodify("nvim_issue/" .. name, ":p") if vim.fn.isdirectory(install_path) == 0...