You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to highlight items that don't have a TS parser, it throws the following error:
"nvim/.config/nvim/lua/plugins/quicker.lua" 29L, 628B
....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: no parser for 'git_config' language, see :help treesitter-parsers
stack traceback:
[C]: in function 'error'
....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: in function 'add'
...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:111: in function 'get_string_parser'
...l/share/nvim/lazy/quicker.nvim/lua/quicker/highlight.lua:181: in function 'get_heuristic_ts_highlights'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:269: in function <...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:225>
[C]: in function 'xpcall'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:128: in function <...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:116>
....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: no parser for 'tmux' language, see :help treesitter-parsers
stack traceback:
[C]: in function 'error'
....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: in function 'add'
...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:111: in function 'get_string_parser'
...l/share/nvim/lazy/quicker.nvim/lua/quicker/highlight.lua:181: in function 'get_heuristic_ts_highlights'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:269: in function <...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:225>
[C]: in function 'xpcall'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:128: in function <...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:116>
....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: no parser for 'tmux' language, see :help treesitter-parsers
stack traceback:
[C]: in function 'error'
....10.1/share/nvim/runtime/lua/vim/treesitter/language.lua:107: in function 'add'
...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:111: in function 'get_string_parser'
...l/share/nvim/lazy/quicker.nvim/lua/quicker/highlight.lua:181: in function 'get_heuristic_ts_highlights'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:269: in function <...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:225>
[C]: in function 'xpcall'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:128: in function 'do_next_highlight'
...cal/share/nvim/lazy/quicker.nvim/lua/quicker/display.lua:139: in function ''
vim/_editor.lua: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>
What is the severity of this bug?
tolerable (can work around it)
Steps To Reproduce
Perform a search that would span files that don't have an installed TS parser
Error pops up
Expected Behavior
I think it's reasonable to just not do syntax highlight for files that don't have TS enabled
Minimal example file
No response
Minimal init.lua
-- DO NOT change the paths and don't remove the colorschemelocalroot=vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .reprofor_, nameinipairs({ "config", "data", "state", "cache" }) dovim.env[("XDG_%s_HOME"):format(name:upper())] =root.."/" ..nameend-- bootstrap lazylocallazypath=root.."/plugins/lazy.nvim"ifnotvim.loop.fs_stat(lazypath) thenvim.fn.system({
"git",
"clone",
"--filter=blob:none",
"--single-branch",
"https://github.com/folke/lazy.nvim.git",
lazypath,
})
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
{
"stevearc/quicker.nvim",
config=function()
require("quicker").setup({
-- add your config here
})
end,
},
-- add any other plugins here
}
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
Additional context
The text was updated successfully, but these errors were encountered:
Neovim version (nvim -v)
v0.10.1
Operating system/version
macOS
Describe the bug
When trying to highlight items that don't have a TS parser, it throws the following error:
What is the severity of this bug?
tolerable (can work around it)
Steps To Reproduce
Expected Behavior
I think it's reasonable to just not do syntax highlight for files that don't have TS enabled
Minimal example file
No response
Minimal init.lua
Additional context
The text was updated successfully, but these errors were encountered: