kylo252
kylo252
Hmm, nothing really stands out to me. - did you try running `:TSUpdate`? - what's the output of `:lua print(vim.inspect(lvim.builtin.treesitter))`?
I still don't see anything specifically wrong 🤔 - try uninstalling all the other parsers ```lua -- first run `:TSUninstall all` lvim.builtin.treesitter.ensure_installed = {"c", "lua"} ``` - try a minimal...
What happens if you comment out that `load_config` function completely in the minimal init? you kinda need to bisect the config file to isolate the problematic setting/plugin.
@nacknime-official, I recommend a complete fresh installation of neovim, maybe even build it from source.
@itsrxmmy, please check https://github.com/LunarVim/LunarVim/pull/1893, we need help testing that
> `C-t` will work even without this line. try something other than ``, here are more examples: ```lua lvim.builtin.terminal.execs[#lvim.builtin.terminal.execs + 1] = { "lf", "", "lf file manager", "float" }...
The way I see it is that it's much easier to not use this API or even undo its changes if necessary, simply do this ```vim :tunmap ``` compared to...
See https://github.com/LunarVim/LunarVim/issues/1902 for more info with regards to a new `config.example_windows.lua`
I've been thinking about this for a while for the `commit` part which has now become relevant, so we still need to handle the rest of the supported attributes. I'm...
@argapost, is this still an issue?