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
-- Cache may not have been populated. Query luarocks.
api.query_luarocks_rocks(function(luarocks_rocks)
callback(luarocks_rocks[rock_name] or {})
end)
end
But I don’t get any error when I manually run that command with luarocks 3.11.1-dev version.
Even :=require("rocks.api").query_luarocks_rocks(function(res) vim.print(res["tree-sitter-rust"]) end) was fine.
I guess some initialization hasn’t executed before the FileType autocommand but couldn’t find it.
The text was updated successfully, but these errors were encountered:
boltlessengineer
changed the title
[Bug] luarocks fails when neovim opened file with arguments
[Bug] luarocks fails when neovim opened with file as an argument
Jul 14, 2024
thanks for the report.
This is an issue with the luarocks locking mechanism.
As a workaround, I guess we have to synchronise all invocations of the luarocks CLI.
I found error when opening neovim with file as an argument without tree-sitter parser.
Loading file with
:e test.rs
after opening neovim is fine.Reproduce
nvim test.rs
:Rocks log
:Rocks log
output:rocks.toml
By adjusting some internal code, I found the error was happening while running first
search --all
command:which was executed from:
rocks-treesitter.nvim/lua/rocks_treesitter/highlight.lua
Lines 40 to 50 in 59903dc
But I don’t get any error when I manually run that command with luarocks
3.11.1-dev
version.Even
:=require("rocks.api").query_luarocks_rocks(function(res) vim.print(res["tree-sitter-rust"]) end)
was fine.I guess some initialization hasn’t executed before the
FileType
autocommand but couldn’t find it.The text was updated successfully, but these errors were encountered: