Open jubr opened 1 year ago
Cycling through MRU tabs are super critical to my workflow. IMO the only thing stopping me from switching to Zed right now.
Big plus one to this: everything else about zed is great, but I just can't shake my muscle memory from other editors of ctrl+tab'ing in MRU order.
I am able to switch between most recently used tabs by adding this to my keymap.json:
{
"context": "Pane",
"bindings": {
"ctrl-shift-tab": "pane::GoBack",
"ctrl-tab": "pane::GoForward",
}
}
Thanks for the suggestion, @phwes, this is close, but not exactly the de-facto MRU behavior I am looking for.
Looks like interest is rising for this feature: #4772 + (semi-related) #5620
Yes, you are right @jubr. On both accounts!
Too me this is most likely one of the most used binding at all. I got so used to it, that I really do not understand why very common browsers and even editors that target especially the fans of bindings do not have this...
Anyway, I would love to see it implement 👍
Related #8757
sorry if this is not relevant here, but how can I set the keybinding to switch to the next tab in zed vim mode.
Hey @phwes 👋
I was very happy to, indeed, bind the ctrl--
and ctrl-_
on the ctrl-tab
and ctrl-shift-tab
binding like you propose because it is exactly what I want. However, it doesn't work and keeps the tab_switcher::Toggle
😢
Do you have an idea why?
Check for existing issues
Describe the feature
Since https://github.com/zed-industries/zed/issues/5244 (which can be closed) cycling tabs L+R has been implemented with
pane::ActivateNextItem
andpane::ActivatePrevItem
.But I'd like to request MRU-cycling through tabs, so I can quickly switch between non-adjacent tabs with
cmd-tab
andcmd-shift-tab
. I often have a lot of files open, having to use the mouse to switch or performing 10 consecutive L or R operations is not efficient.Basically how VSCode does it. Here's some pre-work describing the behavior hoping it can jump-start implementation:
Generic wishlist
pane::ActivateMruPrevItem
andpane::ActivateMruNextItem
pane::ActivateItem
mThese commands can then be bound to for instance:
Some UI thoughts
If applicable, add mockups / screenshots to help present your vision of the feature