(no title)
johnthedebs | 11 days ago
Some feedback (since you were asking for it elsewhere in the thread!). Happy to go into more detail about any of these if it's helpful:
- It's not obvious/easy to open browser dev tools (cmd-alt-i didn't work), and when I did find it (right click page -> inspect element) none of the controls were visible but I could see stuff happening when I moved my mouse over the panel
- Would be cool to borrow more of ghostty's behavior:
- hotkey overrides - I have some things explicitly unmapped / remapped in my ghostty config that conflict with some cmux keybindings and weren't respected
- command palette (cmd-shift-p) for less-often-used actions + discoverability
- cmd-z to "zoom in" to a pane is enormously useful imo
lawrencechen|11 days ago
> hotkey overrides - I have some things explicitly unmapped / remapped in my ghostty config that conflict with some cmux keybindings and weren't respected
We need to be better about this; right now you can modify keyboard shorcuts with cmd+, in the GUI. Planning on making it a config file in the spirit of ghostty though, not sure if we want to reuse ghostty's config file though since it might become a maintenance burden for them...
> command palette (cmd-shift-p) for less-often-used actions + discoverability
yes
> cmd-z to "zoom in" to a pane is enormously useful imo
Thinking of the right way to design this. Like hypothetically we can expand it, but what happens if you make a vertical/horizontal split, or cmd+t to make a new tab? I guess we could just "merge" it back into the original space which would be pretty cool.
johnthedebs|11 days ago
if you make a new split (or navigate splits), it would zoom you back out (contract the panel) and just split/navigate the way it normally would