While in a term3 tab, switching to another tab using Ctrl-Tab should leave the terminal in the same state.
Actual behavior
While in a term3 tab, if you press Ctrl-Tab to switch to another tab and then come back to the terminal tab, the shell autocomplete is triggered. I’m guessing this is because the terminal tab somehow “swallows” the Tab from the Ctrl-Tab shortcut.
This is quite hard to notice in Bash as autocomplete is only triggered if you start typing text and hit Tab twice. However, other shells such as Fish trigger it even when nothing is typed and upon the first press on Tab, so this bug can be annoying.
Here is a short illustration for the problem:
Steps to reproduce
Using Bash:
Open a term3 tab and at least one other tab in Atom.
Start typing a command (for example, ex).
Hit Tab once; notice that autocomplete is not yet triggered.
Switch to another tab using Ctrl-Tab.
Come back to the term3 tab (either by clicking the tab or via a keyboard shortcut).
Autocomplete was triggered while you switched to the other tab.
Expected behavior
While in a term3 tab, switching to another tab using
Ctrl-Tabshould leave the terminal in the same state.Actual behavior
While in a term3 tab, if you press
Ctrl-Tabto switch to another tab and then come back to the terminal tab, the shell autocomplete is triggered. I’m guessing this is because the terminal tab somehow “swallows” theTabfrom theCtrl-Tabshortcut.This is quite hard to notice in Bash as autocomplete is only triggered if you start typing text and hit
Tabtwice. However, other shells such as Fish trigger it even when nothing is typed and upon the first press onTab, so this bug can be annoying.Here is a short illustration for the problem:
Steps to reproduce
Using Bash:
ex).Tabonce; notice that autocomplete is not yet triggered.Ctrl-Tab.