mrjones2014 / smart-splits.nvim

🧠 Smart, seamless, directional navigation and resizing of Neovim + terminal multiplexer splits. Supports tmux, Wezterm, and Kitty. Think about splits in terms of "up/down/left/right".
MIT License
906 stars 38 forks source link

The resize direction is unexpectedly reversed with neo-tree open in a vertical split #16

Closed krishnakumarg1984 closed 2 years ago

krishnakumarg1984 commented 2 years ago

When a tree explorer window such as neo-tree is open to the left in a vertical split to the current buffer, smart-splits does not work as expected. In fact, it has the opposite behavior. When resizing the main buffer with "Ctrl+left", it resizes to the right, making the current buffer smaller and filetree buffer larger. Similarly, the opposite behavior is noted with "<Ctrl + right>".

mrjones2014 commented 2 years ago

Did you try setting neo-tree as an ignored file/buffer type?

https://github.com/mrjones2014/smart-splits.nvim#configuration

krishnakumarg1984 commented 2 years ago

Yes. I have tried it. It still exhibits the same behavior.

mrjones2014 commented 2 years ago

what is ""? it doesn't do anything for me

krishnakumarg1984 commented 2 years ago

what is ""? it doesn't do anything for me

Apologies. I didn't quite understand what you meant.

Edit: Ah. It was a github rendering issue. I updated the text with explicit wording so that the Github renderer doesn't swallow it up.

mrjones2014 commented 2 years ago

Ah, okay.

I can reproduce using nvim-tree (which is what I have installed) now. I typically have my tree on the right which is why I haven't noticed it.

krishnakumarg1984 commented 2 years ago

Ah. I have my symbols outline to the right and file explorer to the left. This is probably why I noticed this issue.

mrjones2014 commented 2 years ago

@krishnakumarg1984 can you verify if it's fixed for you by 620e38da2d3afc562523765b46e759e0141a6d69? I just pushed this commit to master and it fixes it for me.

krishnakumarg1984 commented 2 years ago

@mrjones2014 Yay! That fixed it. Thank you so much. I haven't added neo-tree to ignored file types. This now works for me even without it.

krishnakumarg1984 commented 2 years ago

@mrjones2014 This is now regressing unfortunately.