-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
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
BUG: UI gets all screwed up when scrolling on code or the neo-tree itself #1534
Comments
I am afraid we are going to need more details on this. Can you tell us what version exactly of neo-tree you're using? I suppose additionally, this might not be an issue with neotree at all and could be related to something higher up the stack. I say this because I notice that when you move the cursor to the neo-tree buffer, it "fixes" the line that you are on in neo-tree. There is no logic in neo-tree that does per-line refreshing so this might be related to another plugin or neovim altogether. Lastly, please don't omit the configuration that is provided in the bug report. I cannot recreate your issue, here is the config I used (I took your config and put it in the lazy config we provide in the bug report template) -- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end
-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)
-- install plugins
local plugins = {
"folke/tokyonight.nvim",
-- add any other plugins here
}
local neotree_config = {
"nvim-neo-tree/neo-tree.nvim",
dependencies = { "MunifTanjim/nui.nvim", "nvim-tree/nvim-web-devicons", "nvim-lua/plenary.nvim" },
cmd = { "Neotree" },
keys = {
{ "<Leader>e", "<Cmd>Neotree<CR>" }, -- change or remove this line if relevant.
},
opts = {
-- Your config here
{
"nvim-neo-tree/neo-tree.nvim",
branch = "v3.x",
dependencies = {
"nvim-lua/plenary.nvim",
"MunifTanjim/nui.nvim",
"3rd/image.nvim",
},
config = function()
require("neo-tree").setup({
close_if_last_window = true,
default_component_configs = {
git_status = {
symbols = {
-- Change type
added = "+", -- or "✚", but this is redundant info if you use git_status_colors on the name
modified = "~", -- or "", but this is redundant info if you use git_status_colors on the name
deleted = "-", -- this can only be used in the git_status source
renamed = "~", -- this can only be used in the git_status source
-- Status type
untracked = "",
ignored = "",
unstaged = "",
staged = "",
conflict = "",
}
},
indent = {
with_expanders = true, -- if nil and file nesting is enabled, will enable expanders
expander_collapsed = "",
expander_expanded = "",
with_markers = false,
expander_highlight = "NeoTreeFileIcon"
},
name = {
use_git_status_colors = false
},
},
filesystem = {
filtered_items = {
hide_dotfiles = false,
hide_gitignored = false,
hide_hidden = false
}
},
window = {
position = "right",
width = 30
}
})
end
}
},
}
table.insert(plugins, neotree_config)
require("lazy").setup(plugins, {
root = root .. "/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here This was tested against |
Note, I notice you are using wezterm. Probably worth checking out 4607, I remember seeing some weird artifacting with neovim in wezterm's muxer (IIRC it was the muxer). Anyway, see if this fixes your issue:
|
Did the same as you, ran the config you used with Tried See it, please: 2024-07-28.13-33-57.mp4 |
For giggles, try running the minimal configuration I provided with the following command nvim --clean -u minimal.lua Also, can you provide the output of nvim --version You are experiencing some weird buffer arficating. This is not neotree causing this issue (at least not directly) but its possible that there is some weird setting that has been modified on splits and the like. I say its not neotree causing the issue because when you are scrolling in the right buffer, it is partially overwriting the cells on the right side of the left (neotree) buffer. This is neovim doing weird stuff. |
|
It appears you are a slightly older version of neovim. What happens if you try the current stable version? |
Just compiled from the git repo and the same thing happened: 2024-07-29.09-02-15.mp4 |
Did you check docs and existing issues?
Neovim Version (nvim -v)
0.10.
Operating System / Version
openSuse Tumbleweed
Describe the Bug
When i scroll my code the Neo-Tree interface gets all bugged
Screenshots, Traceback
2024-07-27.11-34-28.mp4
Steps to Reproduce
Just open it and scroll code
Expected Behavior
Not to be bugged
Your Configuration
The text was updated successfully, but these errors were encountered: