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've recently been looking for a solution that implements per-tab buffer lists.
This is handy, and not a new idea. The use case is usually for browsing large code bases. You may want a tab for two particular packages in a large code base. When you're in one tab, you only want the buffers associated with files inside that package, not the other.
I'm using this currently, but I also use coc and fzf-preview. It would be nice if I did not need vim-ctrlspace and could obtain per-tab buffer lists via fzf preview.
Thanks!
The text was updated successfully, but these errors were encountered:
I don't know much about ctrlspace, so I'll have to check and see if it's possible.
I will check when I have time, but do you know if ctrlspace makes it possible to get the values you are using as API?
However, it would be nice if ctrlspace was not required. Would it be possible for fzf-preview to have a vimscript which did some tab -> window -> buffer grokking.
For example when I issue "fzf.preview.TabBuffers" fzf vim looks at the current tab, finds the windows in that tab, and then only displays the buffers of those windows for selection. Something of that nature.
This is a feature request.
I've recently been looking for a solution that implements per-tab buffer lists.
This is handy, and not a new idea. The use case is usually for browsing large code bases. You may want a tab for two particular packages in a large code base. When you're in one tab, you only want the buffers associated with files inside that package, not the other.
There is a project which does this well. https://github.com/vim-ctrlspace/vim-ctrlspace
I'm using this currently, but I also use coc and fzf-preview. It would be nice if I did not need vim-ctrlspace and could obtain per-tab buffer lists via fzf preview.
Thanks!
The text was updated successfully, but these errors were encountered: