Kronuz/SublimeCodeIntel — pull request #232 by vanrijn (2013-03-16 23:48:11+00:00)
Title: Fixed bug in saving status_msg. This was causing status_msg to never be ...

...erased. Also setting an explicit 5 second timeout to really long Invalid language status message.

This is to address https://github.com/Kronuz/SublimeCodeIntel/issues/104

The logger/calltip functions already has a timeout. There was a bug that was preventing the status message from ever being erased properly. Also, I think this message is "info" if not "debug" level, but I think 10 seconds is too long since this messages is extremely verbose and takes over the entire status line. The options were to either change the message type to "warning" or "error", or to provide an explicit timeout amount for less than 10 seconds.

I don't think changing the message type to warning or error is the right thing because it's not a warning or an error situation, it's just the plugin saying "I couldn't do anything with this file".

So I chose to provide an explicit timeout for 5 seconds for this one message.

Hope this helps!