On 6 Mar 2014, at 3:43, Rob McBroom wrote:
Like I said, I was using “:true” before. I wonder if “1” and “:true” were equivalent before, but something in the last update causes “1” not to be parsed the same way. If so, the Python bundle probably needs to be changed.
Indeed: I now check for a string, and check if it’s ‘emptyLines’ and only if not a string, check if it’s a boolean.
I’ve fixed the code so that ‘1’ is still treated as a boolean value. But we’ll push a new bundle where it’s changed to :true, so people won’t have to wait for a new build.
That said, I think ‘emptyLines’ (now) make more sense for Python, as it will for example de-indent current line when typing the ending colon in ‘else:’. Though we can’t push that change, as it would cause people not on latest build, to get indent re-enabled for Python.
But I would encourage Python users (on nightly builds) to make that change and report if it’s causing issues.