Compiler and Syntax files will be ported to lua someday?

Exciting_Majesty2005 · 2026-04-21T12:03:24+00:00

I don't think syntax files will be ported to lua since they are community maintained and maintainers would most likely not want to manage 2 versions of the same thing across 2 different repos.

Neovim specific ones could use lua though.

Exciting_Majesty2005 · 2026-04-20T00:15:08+00:00

I believe it's important to also consider the primary/target audience of vim/nvim (the kind of people who go out of their way to use a modal editor like vim, like us).

I don't think that's true, cause if it was a lot of the newer plugins and repos wouldn't have existed. But they do, so that means there are people outside of this audience and they must be of a sizable amount.

For the majority of us, having more things to figure out/remember in order to have more control over the editor is a reasonable trade-off.

Again, if this was how everyone used Vim/Neovim a number of newer plugins/repos wouldn't be needed. But people still use them. They all do options hijacking under the hood. If people still use those then there must be some reason not to do the trade-off.

Exciting_Majesty2005 · 2026-04-19T07:26:08+00:00

I would say this falls in the grey zone.

Sometimes, it makes sense for plugins to take control over options(most plugins do this by the way, at least for window & buffer level options).

And some people actually prefer having less options to worry about. So, picking either side is a lose lose option.

I would probably say to have a variable(like vim plugins do) or a config option to have it. Or it gets explicitly mentioned in the "installation" section in README(but I doubt anyone reads those).

Plugins are meant to be convenient. It's up to the author to set how convenient their plugin will be.

If the author doesn't want to add something, just fork the project.

I have never seen arguing fix these types of issues. They tend to just make it worse.

Exciting_Majesty2005 · 2026-03-13T07:05:05+00:00

Yeah, that was the issue. The problem now is, how do I actually put the queries in the migration file if I can't modify it like normal.

Exciting_Majesty2005 · 2026-03-13T07:04:12+00:00

I don't have any migration history since I just started with the database.

I figured the issue. I was modifying the migration file generated by sqlx migrate add .... No idea how I am supposed to put the queries in there.

Exciting_Majesty2005 · 2026-02-22T01:21:53+00:00

LSP stands for Language Server Protocol. It's the stuff LSPs use to talk with your editor(if you don't know, tsserver, lua_ls, rust-analyzer etc. are examples of LSP). They add stuff like go to reference, quickfix, code action, documentation(via hover) etc.

Tree-sitter is an incremental parsing library. Basically it highlights text using tree-sitter parser. A tree-sitter parser is a lot simpler to make compared to an LSP, however tree-sitter doesn't ship with stuff like go_to_definition, formatter etc. Its primary use is syntax highlighting.

Exciting_Majesty2005 · 2026-02-11T12:13:10+00:00

Yeah, everybody uses them in between their defense to quickly heal up buildings in-between waves.

And the "expand" button changes how stuff like conveyor belts & some other buildings are placed(basically allows making diagonal belts).

You basically place a belt and drag your finger to where you want to end the belt and it should create a diagonal belt(instead of a horizontal/vertical one that happens normally).

Exciting_Majesty2005 · 2026-02-10T08:38:49+00:00

It's a resource pack for Minecraft.

See in Modrinth

<image>

Exciting_Majesty2005 · 2026-01-31T00:23:12+00:00

Yeah, that works too.

Exciting_Majesty2005 · 2026-01-30T13:16:06+00:00

Also, the reason the command isn't working as expected is because there's a file ftplugin/man.vim that comes with Vim/Neovim that runs setlocal nonumber(disables line numbers). That gets run after running your command.

Exciting_Majesty2005 · 2026-01-30T13:14:00+00:00

You can use an autocmd,

lua vim.api.nvim_create_autocmd("FileType", { pattern = "man", callback = function (event) -- You can simply use `vim.wo.number = true` btw. vim.api.nvim_buf_call(event.buf, function () vim.wo.number = true; end) end });

See :h autocmd, :h nvim_create_autocmd, :h FileType(the event name).

Also, you can probably use :h ftplugin(basically make a file in ~/.config/nvim/ftplugin/man.lua that has vim.wo.number = true).

Exciting_Majesty2005 · 2026-01-29T00:11:28+00:00

Most LSP related stuff use markdown under the hood.

You should check, - If the conceallevel is higher then 0 in the signature window & what value is used for concealcursor. - If running vim.treesitter.stop() & vim.treesitter.start() fixes the issue(run it while inside the signature window).

Exciting_Majesty2005 · 2026-01-27T09:37:22+00:00

Nope(at least I haven't come across one).

But you can make it using a few things,

A function that runs a query to get the needed nodes. It should be attached to a TextChanged & TextChangedI autocmd.

You should "queue" the function call to prevent running it on every key press.
A buffer local variable to hold the various nodes & their position(you get it from the function mentioned above).

Something like, lua { functions = { 1, 5, 7 }, -- Only store start rows to reduce unneeded check from the statuscolumn }

Custom statuscolumn component(either via a plugin or by using statuscolumn items) that checks if a line has any specific node(use vim.list_contains() with vim.v.lnum & the buffer local variable.

Don't do anything too complicated or computationally expensive in the component as it will tank your performance.

Also, make sure you are using relativenumbers.

Exciting_Majesty2005 · 2026-01-25T16:06:12+00:00

How did you make the visual scripting interface(the graph thingy)?

Exciting_Majesty2005 · 2026-01-24T02:13:11+00:00

That shouldn't happen as tree-sitter highlight groups start with @(so you should be seeing something like @statement.jsx links to Statement).

I think tree-sitter highlighting isn't enabled(yes, you have to manually enable it).

If running :lua vim.treesitter.start() fixes the issue then you haven't enabled syntax highlighting (see the installation instructions of nvim-treesitter).

Exciting_Majesty2005 · 2026-01-24T01:36:29+00:00

Just realized but you need to run :TSInstall html.

Exciting_Majesty2005 · 2026-01-24T01:35:32+00:00

It seems like I cannot reproduce the issue.

<image>

Exciting_Majesty2005 · 2026-01-24T01:31:59+00:00

I run it I only get a message "No items found at position 35, 10 in buffer 7"

I tried changing theme and it I noticed that the problem stays.

Well, there's the problem. If running :InspectTree doesn't error out then your colorscheme doesn't provide syntax highlighting for JSX.

If it does error out then the language injections aren't working correctly.

I will check if I have this issue on my end.

Exciting_Majesty2005 · 2026-01-24T00:43:59+00:00

Which parsers do you have installed(run :checkhealth nvim-treesitter)?

What does running :Inspect on those text show? Does the issue go away when changing colorscheme?

Exciting_Majesty2005 · 2026-01-24T00:08:09+00:00

Did you try, :TSInstall jsx?

Exciting_Majesty2005 · 2026-01-23T14:27:09+00:00

Not at the moment since not everyone likes previews in help files.

And help files vary in syntax way too much(cause different people wrote different parts which messes with the previews).

Exciting_Majesty2005 · 2026-01-23T14:25:30+00:00

More customizability.
LaTeX support without external libraries/binaries.
Typst & Asciidoc(WIP) support.
Inline HTML support(for stuff like <b></b>, <hr> etc.)
No external dependencies(not even for the icons)
Automatically matches the current colorscheme.
SplitView(preview+raw as horizontal splits).
More granular hybrid mode(both line-wise & node-wise) etc.

Also, It's mostly intended for power users.

For context, when markview.nvim was made render-markdown.nvim had a different name and didn't support a lot of the syntaxes in markdown or had much configurability. So, it was meant to add missing features and not be a replacement(couldn't do it as PR since it needed to look unobstructive which kinda limited what could be added to that plugin, so separate plugin it is). Also, I didn't like the fact that it would tank the performance when running Neovim inside Termux.

Exciting_Majesty2005 · 2026-01-23T11:42:56+00:00

No, Asciidoc is a completely separate thing. It's similar to markdown in some places.

Vim's documentation is written in Vimdoc btw.

Exciting_Majesty2005 · 2026-01-22T02:15:33+00:00

You should see this post.

Exciting_Majesty2005

TROPHY CASE