But if you don't do this, you can still use <tab> - and if there are more than one option it'll list the possibilities. With this you just have to tab through all the options to see what is there.
So basically it switches the behaviour to what CMD does on Windows. IMO this is extremely annoying and I wish I could disable it on Windows.
If you have 3 options starting with the same prefix, it's fine, but if there's hundreds (e.g. a directory with a lot of libraries starting with lib<something>), it becomes highly annoying and it's better to just give the list so I can type the next letter
For PowerShell, there is PSReadLine, and that has an option to make completion more bash-like in that it completes common prefixes, then lists all options afterwards.
(Say you have a directory with two subdirectories "fooabc" and "foo123". You are in the directory and you type "cd f" and then hit tab. This will complete to "cd foo", and if you hit tab again, then it will show the two options, and then you have to enter "a" or "1" to disambiguate.)
Yes, I'm very confused -- I don't have to do anything to "turn on" autocomplete, it's already turned on! The things they talk about change the behavior.
If you have 3 options starting with the same prefix, it's fine, but if there's hundreds (e.g. a directory with a lot of libraries starting with lib<something>), it becomes highly annoying and it's better to just give the list so I can type the next letter