jps wrote:It sounds like you should just use setStatus(), and not worry too much about the position of the 'Line X, Column Y' message.
You can clear the status message by calling sublime.statusMessage(''), but you'll want to be careful, and only clear it when going from a line with a status message to one without, otherwise you'll end up always overwriting what should be getting displayed with the status message, such as what the find panel prints.
That is in fact what I settled on, for now. It would be nice to have just a little more control over the order that default message gets placed in the statusbar (also be nice to be able to change the separator),
(maybe by making it subject to the regular status key ordering and allowing that key to be changed)
It's not so much that I personally can't stand that the message is no longer where it usually is, but that I think as much of the default behavior should be unaffected by a plugin I write. If that's where people usually look to see where they are in a file, they'll have to search to the arbitrary end of whatever message my plugin sticks in there. (I look there somewhat often to check my line lengths)
But, I can see it's obviously not something that people are clamoring for.
Also, in regard to the suggestion of sublime.statusMessage(''), clearing the status bar is just a matter of removing my part of the message: calling view.eraseStatus(mykey), sublime worries about the rest.
Thanks for considering