Current version of suckless.vim does not respect the order of splitting like vim does #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…plits in vim The order of split commands in vim matters: `split | vsplit` will cause the following scheme: ``` +--+--+ | | | +--+--+ | | +-----+ ``` while `vsplit | split` will create the following splitting: ``` +--+--+ | | | +--+ + | | | +-----+ ``` When suckless.vim is used it creates the second type scheme regardless of the order. In this merge I've replaced 'wincmd n' with 'wincmd a:direction' which fixes the issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ok, no one have asked me, but here we go.
The order of split commands in vim matters:
split | vsplitwill cause the following scheme:while
vsplit | splitwill create the following splitting:When suckless.vim is used it creates the second type scheme regardless
of the order.
In this merge I've replaced 'wincmd n' with 'wincmd a:direction' which
fixes the issue.