Closed miversen33 closed 2 years ago
what you could do is, you could schedule it. So m()
-> vim.schedule(m)
seems to work for me.
Is this still relevant ?
Is this still relevant ?
I think wrapping the call in schedule
is a viable solution (though it might be worth including something along those lines in the documentation for situations where a dev tries to open Telescope before the UI is available).
Feel free to close this out :)
An Issue is some form of documentation :laughing:
Description
When you attempt to create a picker from the
BufReadCmd
event, you end up in a state where your cursor is in the buffer under the floating window, and it doesn't appear you can force your way back into the telescope buffer. Additionally, it appears you cannot kill the floating window without completely killing your neovim session. Potentially related Issue 1804 Issue 1595 PR 1600Neovim version
Steps to reproduce
Open your preferred neovim version with the below test configuration and some file
Expected behavior
I would expect the floating window to load, though there may be some shenanigans with how the floating window is created within the startup lifecycle of vim
Actual behavior
It seems as if the floating window is created and the focus is shifted to the underlying buffer that was created (likely after the floating window is created). Its possible that this is a neovim issue and not a telescope issue, I am unsure.
Minimal config