On 5/14/19 3:00 PM, Robert P. J. Day wrote:
i'm finally annoyed enough about this to just ask ... on a
regular
basis, i mistype a command and (predictably) get:
bash: xxx: command not found...
but, quite often, rather than getting a bash prompt back immediately,
there is a loooooooong pause, as i wait, and wait, and wait for a new
prompt, finally running out of patience and breaking with ^C to get a
new prompt.
what in the name of mutt is bash doing all that time? if there's no
such command, why the long pause in giving me a new prompt?
If you have "PackageKit-command-not-found" installed, then it's trying
to find you a package to install to give you that command. Try running
a command that could exist, but you don't have installed. For example,
"cowsay". :-) (Unless you do have that installed.)