Bash completes to files or directories that don't exist. This problem
occurs only because of non-escaping the equal sign. But since bash
allows this, it's still a bug.
Repeat-By:
Situation 1:
$ mkdir =
$ cd =[TAB] produces $ cd =\=/
Problem: Bash completes to '==', which doesn't exist. It should only
replace '=' by '\='.
Situation 2:
$ mkdir foo
$ touch foo/bar=
$ vi foo/bar=[TAB] completes to $ vi foo/bar=foo/bar\=
Problem: as above - bash completes to something that doens't exist,
should only replace '=' by '\='