We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimal config (using lazy.nvim):
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "--single-branch", "https://github.com/folke/lazy.nvim.git", lazypath, }) end vim.opt.runtimepath:prepend(lazypath) plugin_list = { { "nvim-treesitter/nvim-treesitter", dependencies = { { "filNaj/tree-setter" }, }, build = ":TSUpdate", config = function() require("nvim-treesitter.configs").setup({ tree_setter = { enable = true }, }) end, }, } require("lazy").setup(plugin_list, {})
Given a file test.rs, with the following content:
test.rs
if f(x) { let a = true; }
When I press "o" in line 2 in normal mode, the code gets mangled:
The example is a bit silly, it's an over simplified version of the code that produced this behavior originally.
Specific commits involved (lazy-lock.json):
{ "lazy.nvim": { "branch": "main", "commit": "dac844ed617dda4f9ec85eb88e9629ad2add5e05" }, "nvim-treesitter": { "branch": "master", "commit": "2ee71c1a2fa74c10692be10ae420ff0c3a02eb3c" }, "tree-setter": { "branch": "master", "commit": "2cb29fa95d91e8c6c8615587fe4102e518e6b6c0" }, }
The text was updated successfully, but these errors were encountered:
I too see some weird behaviors with rust:
Sorry, something went wrong.
No branches or pull requests
Minimal config (using lazy.nvim):
Given a file
test.rs
, with the following content:When I press "o" in line 2 in normal mode, the code gets mangled:
The example is a bit silly, it's an over simplified version of the code that produced this behavior originally.
Specific commits involved (lazy-lock.json):
The text was updated successfully, but these errors were encountered: