This bug was fixed in the package command-not-found - 0.2.40ubuntu1
---
command-not-found (0.2.40ubuntu1) lucid; urgency=low
* scan.data:
- updated to current lucid
* command-not-found:
- catch KeyboardInterrupt during initial import as
well (LP: #479716)
- show
Thanks Wouter, only showing it in this case makes sense, I commited a
fix to bzr.
** Changed in: command-not-found (Ubuntu)
Status: New => Confirmed
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Low
** Changed in: command-not-found (Ubuntu)
Status: Confirmed
I don't see how people will be confused by "The program 'latex' is
currently not installed.", that seems pretty clear to me. To add another
line saying "command not found" is totally unnecessary.
It would be good to do that when a command is typed that is not
recognized at all (like it does now),
In karmic it will print:
...
latex: command not found
This is a reaction to bug #420161 when bash stopped outputing that line. I
think the command not found string
is useful to not confuse people who are used to this as a standard shell output.
** Changed in: command-not-found (Ubuntu)
S
I agree with you. Why don't you consider posting the 'bug' here -> bug-
b...@gnu.org
--
Don't display "bash: command: command not found"
https://bugs.launchpad.net/bugs/408020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Cesar, I mean the output you get when you try to run a program that you
don't have installed (hence it is filed against the command-not-found
package). What you pasted is the output of installing a program and then
running it.
--
Don't display "bash: command: command not found"
https://bugs.launc
What version of Ubuntu are you using?
In my case, I'm using Jaunty Jackalope and I throw the following:
c3...@sonya:~$ sudo aptitude install wipe
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Leyendo la información de estado exten
