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
I tried using this config segment, but it didn't work immediately. In the video below, after successfully opening trouble, the content inside is empty. Moving the cursor to the trouble view doesn't refresh the content instantly. It only refreshes after a certain action (as shown in the video, it refreshes when I move the cursor back to the main buffer; although the cursor doesn't actually go back to the main buffer, which might be a clue).
2024-07-11.194241.mp4
The current default fold-level setting is achieved by extracting an attribute from the window. In my opinion, configuring it this way might not be very user-friendly for the end-user: it means we need to obtain its winid before even opening trouble. I am unsure if this configuration is intended to be open; I might have missed something, so this might not be a bug.
Regards !
Steps To Reproduce
See above
Expected Behavior
See above
Repro
-- 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", "https://github.com/folke/lazy.nvim.git", lazypath, })
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
{ "folke/trouble.nvim", opts= {} },
-- add any other plugins here
}
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
The text was updated successfully, but these errors were encountered:
Did you check docs and existing issues?
Neovim version (nvim -v)
lastest
Operating system/version
linux
Describe the bug
I noticed that the code here can set the default fold level.
trouble.nvim/lua/trouble/view/init.lua
Lines 638 to 645 in 4453fea
I tried using this config segment, but it didn't work immediately. In the video below, after successfully opening trouble, the content inside is empty. Moving the cursor to the trouble view doesn't refresh the content instantly. It only refreshes after a certain action (as shown in the video, it refreshes when I move the cursor back to the main buffer; although the cursor doesn't actually go back to the main buffer, which might be a clue).
2024-07-11.194241.mp4
The current default fold-level setting is achieved by extracting an attribute from the window. In my opinion, configuring it this way might not be very user-friendly for the end-user: it means we need to obtain its winid before even opening trouble. I am unsure if this configuration is intended to be open; I might have missed something, so this might not be a bug.
Regards !
Steps To Reproduce
See above
Expected Behavior
See above
Repro
The text was updated successfully, but these errors were encountered: