We actually do try to make the canvas as keyboard navigable as possible. There are a list of keyboard bindings in the "Keybindings and Help" button on the bottom right.
In terms of manually resizing, we actually do try to tile in the viewport. May I know what's causing you to resize it so I can fix it?
In this vein, do you know what the experience has been like for users that use the vim vscode plugin? I see that it's trivial to carry over extensions and whatnot, but is the experience still "good" trying to use both?
I use the Vim VS Code plugin! It mostly works, but I'm not going to lie: there are a couple of bugs e.g. when you go to definition the Vim selection gets confused because in most cases you get placed into a symbol editor.
I am happy to fix any bugs here. I am the only person I know who uses the Vim plugin in Haystack, so I haven't prioritized fixing the bugs I encounter.
Sorry, I was just going off the demo. Maybe demo the keybinds briefly.
If you get a demo of someone editing stuff super quickly using only keybinds I think it would look pretty cool.
Right now I don’t know if the value prop is strong enough for me to switch editors and remodel/relearn all my keybinds. This is like a 10-15% improvement not a 1.5x or 2x improvement.
In terms of manually resizing, we actually do try to tile in the viewport. May I know what's causing you to resize it so I can fix it?