quick feedback, write something at search start

[simohe]

When called from the shell hook, it would be handy when the user would get some feedback immediately. Then searching can be aborted with ^C.

I propose:
in command-not-found, run `print('command not found ...', end="\r")` before starting the search. This line will be overwritten when the result is printed.
Not sure if this message shlould always be printed, or only when called from the hook.

[Dominique Ramaekers (dominique-ramaekers)]

Hi Simohe,

Thanks for your input.

One quick question, how long do you have to wait on a search, and what command did you enter? c-n-f is build to be fast. On my systems, I have immediately results...

[simohe (simohe)]

Normally the output is there after 0.2 seconds latest. This is fine of course.

It has happened that it took maybe three seconds. During this time, I tought the real command was running successfully. With early feedback, I could have hit Ctrl-C and fixed my command line.
I currently have no idea what conditions are required to hit a long search. Will try to remember next time it happens.

Of course the "print()" call should have "\r" at the end, not "\n". Trying to fix in description...