why the long pause after bash "command not found"?

[Robert P. J. Day]

  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?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                         http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

This is PackageKit looking for RPM binary packages that might have the command you need.

(Please CC this message yourself if it doesn't reach the list.)

  -----Original Message-----
  From: <users(a)lists.fedoraproject.org&gt;
  Sent: Tue, 14 May 2019 18:00:29 -0400 (EDT)
  To: 3603060030(a)txt.att.net
 Subject: why the long pause after bash "command not found"?

>   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 
==================================================================
This mobile text message is brought to you by AT&T

[DJ Delorie]

"Robert P. J. Day" <rpjday(a)crashcourse.ca&gt; writes:
>    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? 
It's probably trying to give you a clue on how to install the right
package to get that command.

Try removing PackageKit-command-not-found if you don't want that
"feature".

[Tom Horsley]

On Tue, 14 May 2019 18:11:45 -0400
DJ Delorie wrote:

>  Try removing PackageKit-command-not-found if you don't want that
>  "feature". 
On my list to remove even before I first boot a newly
installed fedora (from a chroot into the fedora partition).
bash-completion and environment-modules are two other
highly irritating ones I get rid of.

[Patrick O'Callaghan]

On Tue, 2019-05-14 at 18:33 -0400, Tom Horsley wrote:
>  On Tue, 14 May 2019 18:11:45 -0400
>  DJ Delorie wrote:
>  
>  > Try removing PackageKit-command-not-found if you don't want that
>  > "feature".
>  
>  On my list to remove even before I first boot a newly
>  installed fedora (from a chroot into the fedora partition).
>  bash-completion and environment-modules are two other
>  highly irritating ones I get rid of. 
I find bash-completion useful (within limits).

poc

Hi

On Wed, 15 May 2019 11:45:51 +0100 Patrick O'Callaghan wrote:
>  On Tue, 2019-05-14 at 18:33 -0400, Tom Horsley wrote:
> > On my list to remove even before I first boot a newly
> > installed fedora (from a chroot into the fedora partition).
> > bash-completion and environment-modules are two other
> > highly irritating ones I get rid of. 
>  I find bash-completion useful (within limits). 
Me too, and particularly since I discovered the M-/ (or Alt-/,
complete-filename) key to force a simple filename completion when the
full (too fancy) completion with TAB is not what you want.

The bash-completion is really useful with a bunch of commands
nowadays.

-- 
francis

[Samuel Sieb]

On 5/15/19 10:02 AM, Francis.Montagnac(a)inria.fr wrote:
>  Me too, and particularly since I discovered the M-/ (or Alt-/,
>  complete-filename) key to force a simple filename completion when the
>  full (too fancy) completion with TAB is not what you want. 
Thank you very much for this tip!  I used this yesterday.  That has been 
my only annoyance with bash-completion.

[Ian Chapman]

On 15/05/2019 06:33, Tom Horsley wrote:

> > Try removing PackageKit-command-not-found if you don't want
> that
> > "feature".
>  
>  On my list to remove even before I first boot a newly
>  installed fedora (from a chroot into the fedora partition).
>  bash-completion and environment-modules are two other
>  highly irritating ones I get rid of. 
+1 to that. The bash-completion is in theory useful but in many cases it 
doesn't fallback to the default properly which is just annoying.

-- 
Regards,
Ian Chapman

[Samuel Sieb]

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.)

[Robert P. J. Day]

On Tue, 14 May 2019, Samuel Sieb wrote:

>  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.) 
  ah, got it, thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                         http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================