This question already has an answer here:
This evening, I accidentally typed in
at the bash command line (Fedora 27, bash 4.4.12). To my surprise, it did (apparently) nothing, but gave no error. How come?
I get the same effect with
.. on its own, with no argument.
I wondered whether it could have been treated as
. ., i.e. source the current directory, but when I try that, it gives an error to say that
. is a directory.
If I try three dots, it suggests trying two:
[james@melissa ~] $ ... bash: ...: command not found... Similar command is: '..' [james@melissa ~] $
so it certainly on some level thinks that the command exists. There's no
man page for it, though, and
.. --help doesn't give any output.
But perhaps most weirdly of all, it seems that if I execute
.., with or without an argument, then I get an exit code of 127, which is the exit code for trying to run a non-existent command. So on some level it also thinks the command doesn't exist.
It doesn't appear to be related to the existence of a directory called
..; or, at least, I do get an error if I type the name of any other directory on its own, and
.. doesn't throw an error even if I'm in the root directory, where there's no such directory as
All I can guess is that it's not really a command, but that the error message is being suppressed for some reason.
Any other ideas?
EDIT: this turns out to be the same underlying problem as in linked post, although with different symptoms: there, any command starting with a
. silently fails. That is not the case here, where only
.. has this effect. It seems that the bug has been partly fixed, but not completely.