For whatever reason I was thinking at the time, I had split the channels
to receive request to print to and clear the status message. This
basically means that, even if you meant to print X and then clear it
in 500 milliseconds, the clear request could actually arrive BEFORE
the print message.
This change basically puts all the status related request into one
channel, so that all requests can come sequentially
This basically makes it easier for the users to see what exactly they
are waiting for. Previously we ran the filter, then re-drew the screen.
But this could take a while if the buffer is really big or the matcher
is slow, and therefore you would be stuck with a really old version of
your query in the screen for a while.
This change basically forces a redraw of the prompt alone before running
the query, which was something I meant to do for a long time, and now
possible because I split up the drawing in the layout object to
Prompt/Status/Lines sections