GNOME Bugzilla – Bug 743020
Doesn't use VIM bindings for split-screen
Last modified: 2015-01-21 14:22:11 UTC
I regularly use Ctrl+W followed by "S" to get a horizontal split in VIM. In gnome-builder, this just closes the current file/window. Horizontal splits might not be possible with the current UI, so Ctrl+W "S" (as well as Ctrl+W "V"), should split vertically. Ctrl+W followed by Ctrl+W would switch views.
indeed. I think we need to improve keybindings in VIM mode.
*** Bug 743261 has been marked as a duplicate of this bug. ***
Created attachment 295052 [details] [review] vim: add basic support for vim splits via ctrl+w operations This supports creation of vertical and horizontal splits as well as closing the current split. Note that this only plumbs the signals, and the embedder is responsible for implementing what a split means. This does not currently implement support for navigation through the splits. That can be implemented separately from this.
Created attachment 295053 [details] [review] editor: wire vim split operations to editor splits
Please give this a try! However, it does not yet implement ^w^w ^wn ^wp or ^w<arrow> movements. The following should be supported: :split :vsplit :sp :vsp ^wc ^ws or ^wS ^wv Cheers!
Attachment 295052 [details] pushed as 6f45a1d - vim: add basic support for vim splits via ctrl+w operations Attachment 295053 [details] pushed as a0b3f51 - editor: wire vim split operations to editor splits
Created attachment 295055 [details] [review] vim: add simple support for cycling through visible buffers Supported movements are: ^w^w ^wn ^wp We do not currently support moving between the stacked splits, that will be done in a follow up commit.
Comment on attachment 295055 [details] [review] vim: add simple support for cycling through visible buffers Attachment 295055 [details] pushed as 0611988 - vim: add simple support for cycling through visible buffers
hey this is great, thanks for the fast turn around. one thing I noticed, is I use "^w w" not "^w^w" to switch between splits and so when trying this is out i ended up putting "w" in my buffer. I filed bug 743299 to cover that case.