-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Veritical split opening of already opened file doesn't work. #339
Comments
The code responsible for this behavior is in: command-t/autoload/commandt.vim Lines 172 to 185 in 7147ba9
It's basically trying to prioritize switching to a pre-existing view of buffer rather than opening a new one. I can see, though, why you might want to deprioritize things when the operation was explicitly "open this result in a vertical split" (and similarly for horizontal splits and probably tabs too). There are a lot of subtle nuances though (see wincent/wincent@8a95c3d for example), so may want to think about this carefully before making a change. |
I had to revert back to an older version of Command-T. The new behavior messed up my workflow after years of muscle memory. I'm often hacking on multiple sections of the same file in a vertical split. Simply choosing an already open file will jump that file instead of opening it (in all cases). If there was an option to disable |
By me is the use case similar as by artnez, I'm often using vertical splits on the same files. So generally in order to have this functionality we must change code snippet, which you have shown us. |
Thank you very much for creating and maintaining this great plugin, @wincent . I understand what I am doing. When I am opening a file with Command-T in a split, I do NOT want to move to another split, but want to open the file in that split. |
Not really "new" behavior (the commit I linked to above is from four years ago, and merely brought things closer to the intended behavior). I'm happy to add some option for this, carefully (like I said above, there are many subtleties and nuances to take into account), and in the meantime you can revert back to an older version or hack the code yourself. Technically you should be able to have it without any code changes by resourceful manipulation of the |
Thank you very much for the quick reply and kind comments and suggestions, @wincent . |
So I just cut v5.0.3 from the |
I've temporary hacked my .vimrc file in following commit: a-d-v-e-n-t-u-r-o-u-s/.dotfiles@18e9bda I'm going to test it for a few days to see if this is working for me. @wincent thank you very much for hints. |
Hello,
here is the scenario with which I got problem, maybe someone can help me with that:
Generally I'm using default settings of CommandT and current master from the SHA-1 sum:
7147ba9
The text was updated successfully, but these errors were encountered: