You will learn
that rewrite to C would be of no use, because Python code
immediately calls wrapped satsolver library which IS written in C. And
most of time (if not all of it) is spent there ...
Too bad. Look: This is a tool for a bash users and we have a good reason to
believe that people using bash are people who are not willing to loose their
time with fancy GUI tools. We want to help them with their work and help them
when they do a mistake, fine.
You are probably aware of it, but just to make it clear for other list
readers: command-not-found is not GUI. It just prints some text to console.
But exchange of help that probably will not be needed
for a apparent delay in
many cases when a typo is typed is no real help. command-not-found message
with all the information in 0.3 seconds is a cool thing to have. Message
appearing in 1.3 seconds makes this package just another kludge that needs to
be uninstalled from the default installation, when you want to have your work
When it provides useful information which missing package to install
just in 1.3 seconds, it is a great enhancement, don't you think? I agree
that 1 second could be bothersome when you do a typo, though.
Unfortunately there is no easy way to figure out if the command written
is a typo or not. More easier approach is to do less typos :)
(Especially in shell they can be dangerous).
I got used to uninstalling mono, apparmor and similar
highly useful tools for
my daily work. I am very unhappy that we have yet another thing like that.
Just add command-not-found to your list then. It seems wide already.
(Or change you shell profile, you wouldn't need to bother with this
If this tool has to be that slow by design, I think
that it should not
in default installation (again: bash users are IMHO
mostly people who want to
have their work done, no need to help them). Otherwise it should be fixed.
Shell users are the ONLY people which will use this tool, so argument
'no need to help them' is far off. Command-not-found could not be used
from anything else than shell.
I sure hope that advanced bash users (the ones you are probably
referring to, not all bash users) are able to add 'unset
command_not_found_handle' to their profiles.
For my part, I really don't care if c-n-f is a part of default install
or not. I know how that the tool exists and how to install it. The
question is: Do we want our users to know about it? Do we care about
their experience? Do we want a head start on the competition? If there
is more negative response, c-n-f will not be installed by default. If
there is more positive acceptance, it will stay. If we hadn't enabled it
by default now, we would have never known.
Best Regards / S pozdravom,
Pavol RUSNAK SUSE LINUX, s.r.o
Package Maintainer Lihovarska 1060/12
PGP 0xA6917144 19000 Praha 9, CR
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org