-
Notifications
You must be signed in to change notification settings - Fork 73
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 about listchars #150
Comments
I cannot reproduce this. I've tried on v0.7.2 and on nightly. I've tried with my normal config and with a minimal config that consists of only vim.o.list = true
require('aerial').setup({}) Could this be caused by some interaction with another plugin you're running? Can you try with a minimal config and see if the issue reproduces? |
I'll make a minimal configuration ASAP. Unluckily it maybe in next weekend. because I'm gonna go to school tomorrow. |
I see this too. If you open Aerial, change focus and go back to the aerial split, then the visual bug disappears |
Still can't get it to repro, but I've switched to using the |
@stevearc The minimal configuration I tried: local o = vim.opt
o.runtimepath:append("~/repos/aerial.nvim/")
o.runtimepath:append("~/repos/indent-blankline.nvim/")
o.runtimepath:append("~/repos/nvim-treesitter")
o.list = true
o.listchars:append("space:⋅")
require('aerial').setup({})
require("indent_blankline").setup({})
for index, value in ipairs({}) do
if index == value then
print(index)
end
end This seems that there is conflict between screenrecorder-2022-09-23_19.59.52.mp4 |
Thanks for the repro! I was able to narrow down the cause. Something aerial is doing does trigger it, but it's an autocmd + some behavior in indent-blankline that's causing the display issue. I've filed lukas-reineke/indent-blankline.nvim#482 to follow up. |
Fixed upstream in version 3 of indent-blankline |
Describe the bug
Listchars of origin window disappear after entering aerial window
System information
To Reproduce
Steps to reproduce the behavior:
:AerialOpen
Screenshots
screenrecorder-2022-09-13_17.56.05.mp4
Additional context
This bug appear after this commit d1e0bcd
The text was updated successfully, but these errors were encountered: