Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.
Sign up to join this community
When I am running on the command line using iTerm, it is in a different mode than I'm used to, shown in the images below.
When I try to type a command it shows all the previous variations of that command. When I try to run a commandit often adds other options to the command line. How do I get out of this mode?
This looks like what happens when you start typing a command and then hit cmd+;. The options in that mode are :
iTerm2: Highlights for New Users: Autocomplete
Any text that exists in a tab or its scrollback buffer can be autocompleted in that tab. To use autocomplete, type the beginning of a word and then press cmd-;. An autocomplete window opens showing the top 20 choices for words beginning what you have entered. The list can be filtered by typing a subsequence. The filter can be reset by pressing backspace. If you make a selection and press return, it will be entered for you. If you make a selection and press tab, your autocomplete will be extended with the selection.
To just get "out of this mode" – not making a selection – hit esc.
This then could therefore be for this special case a setting found 'automated' in Preferences>Profiles>Advanced>Triggers:
If that's the case, then clicking edit should open a sheet-pop-up where you see some entries, one of them providing this now unwanted feature.
In the lower left here is a plus and minus sig box. Select the unwanted trigger and delete it.
Alternatively, you might just create an entirely new profile (first picture with "Default" + "TUSTEP"), click the plus sign in the lower left, and compare settings with your former "Default"-profile (in case you have some more sophisticated settings).
The files at
~/Library/Preferences/com.googlecode.iterm2.plist
~/Library/Application\ Support/iTerm2
might also be worth a look.
If there are external 'input manipulators' installed (text autocompleter, scripters, listeners to events) things get more complicated…
when running iTerm click on the View menu and under that menu is an option for "Auto Command Completion". That option was selected which caused the problem mentioned in the question. When that option was deselected the iTerm windows performed as normal.
