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
When I used emacs, it was always possible to search and open one of your "special" buffers, e.g. a non-file buffer that might contain something like test results. This made it easy to access results from various tasks in new windows, even after the original had been closed.
In vim, there are similar special buffer types, which include things like scratch buffers and unlisted buffers, but it seems that there is no obvious way to access them with tools like Telescope or FzfLua.
Is there a picker that could be used for this, or perhaps a configuration option that doesn't exclude them? From this line it looks like such buffers are excluded from results by default, but it would be really useful to be able to include them so that one could easily list and access such "under-the-hood" buffers more readily.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for getting back to me! Yes, if I comment that line out then I can see the unlisted buffers. Not that they're all necessarily named useful things... but they're at least there, which is a start!
When I used emacs, it was always possible to search and open one of your "special" buffers, e.g. a non-file buffer that might contain something like test results. This made it easy to access results from various tasks in new windows, even after the original had been closed.
In vim, there are similar special buffer types, which include things like scratch buffers and unlisted buffers, but it seems that there is no obvious way to access them with tools like Telescope or FzfLua.
Is there a picker that could be used for this, or perhaps a configuration option that doesn't exclude them? From this line it looks like such buffers are excluded from results by default, but it would be really useful to be able to include them so that one could easily list and access such "under-the-hood" buffers more readily.
Thanks!
The text was updated successfully, but these errors were encountered: