Can config be changed on-the-fly?

[MunifTanjim]

If I want to test the UI to see how it is rendered for different configs, what are my options?

Can config be changed inside each it(...) block?

Or do I need run nvim --headless --noplugin -u tests/....lua -c "lua require('plenary.test_harness')... command for each config?

[cseickel]

Config can be changed on the fly by calling the setup() function again. The caveat here being that I don't think this is 100% clean. In particular, an existing tree may retain state that is related to the prior config.

It should work as desired if you call setup with your new config, then create a new tab and close the original tab. Closing the tab will dispose of all state in that tab.

[cseickel]

Actually, you could also directly called require("neo-tree.sources.manager").dispose_tab(1) to dispose all data in the first tab. There is also a corresponding dispose_window which takes a window id for position = "current" trees.

[MunifTanjim]

What does the _clear_state do?

neo-tree.nvim/lua/neo-tree/sources/manager.lua

Line 64 in 2f850ca

M._clear_state = function()

[cseickel]

Exactly what you want it to do! I forgot that was there. It does clear everything.

I would call that first and then call setup() with your new config.