I feel like ctrl + tab has to move to next tab & ctrl + shift + tab should move to previous tab (cycle if it reaches the end).
I feel like that's more predictable behaviour.
I feel like ctrl + tab has to move to next tab & ctrl + shift + tab should move to previous tab (cycle if it reaches the end).
I feel like that's more predictable behaviour.
And I love it :-p It is literally the reason (in combination with "open new tab next to current") I use the browser I do (Vivaldi; would consider Opera, but it doesn't/didn't do "open new tab next to current").
To each their own :-)
(It is literally the reason I will not be leaving Firefox after this Ctrl-Tab moves to most recently used tab abomination :))
I'm joking of course that I think to desire otherwise is insane. Except I'm not. Or am I? :)
Hence, alt was just hanging out being useless :-p (I'm like 95% terminal or browser, so it's a great use of alt to me :-) )
Amusingly, last time I used OSX or Windows properly, I got super grumpy about the fact "(alt|mac)-tab" seemed amazingly inconsistent - I think cause I'd try and switch consistently between two windows, and got surprising-seeming results... I somewhat think I had gremlins :-p
(As I wrote this I actually did a few ctrl-tabs and a few alt-tabs... I hadn't quite realise I used both as often/evenly...)
[1] https://github.com/bwinton/TabCenter/issues/498#issuecomment...
However, I am unable to use it through the keyboard. The undocumented C-S-l seems to trigger a search over there. But there is no way of navigating to a matching tab without the mouse. Any tips?
You can enter "% string" into the location bar, and it will suggest switches to open tabs which contain that string either in their title or URL.
I've been using this little-known location bar feature for a long long time.
If you only have a few tabs open, it can be useful in conjunction with Ctrl-[1-9], but I am also still strongly in the next/prev tab camp.
{ "keys": ["ctrl+tab"], "command": "next_view" }, { "keys": ["ctrl+shift+tab"], "command": "prev_view" }
Also Preferences -> Key Bindings works too but I'd encourage everyone to get used to the command palette for all sorts of commands like Set Syntax and Package Control
I don't use ST, but at least in Atom, I know you can easily override it in your keymap:
'body':
'ctrl-tab': 'pane:show-next-item'
'ctrl-tab ^ctrl': 'unset!'
'ctrl-shift-tab': 'pane:show-previous-item'
'ctrl-shift-tab ^ctrl': 'unset!'On Atom, I've set ctrl + tab to remap to pane:show-next-item, and ctrl + shift + tab to pane:show-previous-item.
(view your keymap, and see what ctrl + page-up/down is bound to, and then bind it to ctrl + tab /+ shift)
Edit: here are my settings:
'body':
'ctrl-tab': 'pane:show-next-item'
'ctrl-tab ^ctrl': 'unset!'
'ctrl-shift-tab': 'pane:show-previous-item'
'ctrl-shift-tab ^ctrl': 'unset!'Usually when programming, the most relevant are the last source files I viewed, e.g. a source file and its header file. I love ctrl+tab switching between most recent files this way.
Same in a webbrowser with related articles. Don't see a use of a next/prev in the list tab shortcut myself, it's not like tabs are ever in some particular order for me :)
If I want to switch between 2 tabs quickly - I set them side by side and it solves the problem for me.
(And then meta-tab is also hanging out there, being simple and ready for an alternative context switch (mostly browser <-> terminal).)
Not to mention you'd need to set the hand from one end of the keyboard to the middle, just to press something you'd otherwise move 1 key.
As I said, it's dumb.
If I want to go to specific file, I'd just Ctrl+P and type in the filename.
Using Ctrl+PageUp/Down to scroll through all open tabs is predictable but kinda useless since I have 20+ tabs opened after a while.