Closed bgerstle-lookback closed 7 years ago
Thanks for the report, @bgerstle-lookback. Something tells me this is a regression, as I don't recall this happening in the past.
Likely suspects: 85949ce and/or 595976e.
Back from my personal account 😅 Confirmed that this is a regression: rolling back to 5.0.0 restored CommandTOpen
functionality.
I think I know what's wrong. I'll push a fix in a bit.
Sometimes I do desire the bugged behavior. Can it be made available somehow?
Why do I want it (not all the time, but sometimes)?
Let's say I have this layout where I'm editing file2
in tab1
while giving a look at related files file1
and fileX
_______________________ _______________________
|tab1 | |tab2 |
----------------------- -----------------------
| | | | | |
| fileX | | | | |
| | | | | |
|---------| file2 | | | file4 |
| | | | | |
| file1 | | | file3 | |
| | | | | |
----------------------- -----------------------
then I go to tab2
where I have to edit file4
while giving a look at file3
and fileX
(the same as the other tab).
Usually I'd move to tab2
-file3
(well, this can be done with the non-bugged version of the functinality you fixed here, ahahah), hit Ctrl-ws, and then use this plugin to open fileX
. However, since fileX
is already opened in the other tab, the focus jumps there.
Steps:
FileA
FileB
in a new tab (e.g.:tabe FileB
):CommandTOpen e FileA
(or select from:CommandTBuffer
list)Expected results:
vim switches to
FileA
.Actual results:
vim opens
FileA
in current tab..vimrc
is setup via my dotfiles. I've added theset switchbuf=usetab
, andCommandTOpen
works for buffers in split panes, but not buffers in another tab.