Iordanis Petkakis

@folke Sorry for pinging you, but I missed when this was marked as stale and didn't manage to make a comment to unstale it. I believe this is a valid...

Either that or in the old `lazyfile` i had added the option there right after setting `vim.bo[buf].syntax = ft` when there's no treesitter parser available and it seemed to work....

Yes, removing it also works. I just created a `test.txt` with contents `tyyypo` and tested with and without that option and it seems to work. Please see also for yourself....

It will be on [13.1.0](https://github.com/LazyVim/LazyVim/pull/4733), but a new release hasn't been made yet. You might want to follow latest HEAD if you'd like as described in the [docs](https://www.lazyvim.org/configuration/lazy.nvim).

Not a bug. You have incorrect order of imports in your `lazy.lua` file. For beginners imports should be avoided and just use the command `:LazyExtras` to enable the Extras that...

That warning is for new users who don't know what they're doing. You can have imports in other files as well as long as you know what you're doing. However,...

It would indeed be better if that example was removed in my personal opinion, but I'm just a simple user like you and maintainer has the final say. I just...

Whatever you install is via `:LazyExtras` is saved in file `lazyvim.json`, so if you version control that file you can share it across different systems. When a user uses `import`...

You're using single quotes instead of double quotes for the stylua error. And the other error is about not having a `recommended` section, which languages Extras are required to have....

The `preset = "luasnip"` is a shorthand by blink to not define all the previous fields (like `expand` in your case). Shouldn't this be fixed in blink instead if the...