Skip to content
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

<C-t> opens a horizontal split instead of a new tab #311

Closed
Bladtman242 opened this issue Oct 20, 2017 · 9 comments
Closed

<C-t> opens a horizontal split instead of a new tab #311

Bladtman242 opened this issue Oct 20, 2017 · 9 comments

Comments

@Bladtman242
Copy link

Bladtman242 commented Oct 20, 2017

<C-t> opens a horizontal split instead of a new tab.
It doesn't happen every time, but I haven't been able to discern a pattern.

@adrianhelvik
Copy link

adrianhelvik commented Oct 29, 2017

2nd this. To clarify. It opens a new split pane instead of utilising the current buffer. The current buffer does not have unsaved content. It is seemingly random.

(On a positive note it made me memorize ‹c-w›j)

@wincent
Copy link
Owner

wincent commented Oct 29, 2017

What's the value of :set switchbuf??

@adrianhelvik
Copy link

usetab

@adrianhelvik
Copy link

I'm able to reproduce this easily. After pressing ‹leader›-t and selecting a random file a few times (I tested it now and it first took 9 times, then 6 times), the tab splits. Subsequent ‹leader›-t create new splits. For me the split is however vertical and not horizontal.

@adrianhelvik
Copy link

The same thing happens on my colleagues computer.

@Bladtman242
Copy link
Author

The value of switchbuf is usetab.

@wincent
Copy link
Owner

wincent commented Nov 17, 2017

I'm not able to reproduce this, but I'm looking at #315 and will see if that can be merged without introducing any regressions.

@wincent
Copy link
Owner

wincent commented Nov 17, 2017

#315 is merged into master now, so let's close this. If it isn't resolved for you, please comment and I can re-open it.

@wincent wincent closed this as completed Nov 17, 2017
@a-d-v-e-n-t-u-r-o-u-s
Copy link

Hi,
I had the same problem with version from 5.0.2 tag with following SHA-1 sum:
1c797d0

After rebasing on current master, problem seems to dissapear
7147ba9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants