Commit 2336ee5
committed
Another weird Sublime view settings case
Another situation where Sublime returns None from the settings
dictionary via "get" when it should return the default or the actual
value. This seems to be some kind of race condition as we never set the
object in the settings file None, and this isn't the first time I've
seen this.
In this case, I am not certain if the object is already in the view or
not, but if it isn't, we should have used the default value of "{}", and
if it was, we should have pulled the dictionary object, but isntead we
got None which we never set.1 parent 7e983cd commit 2336ee5
1 file changed
+2
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
157 | 157 | | |
158 | 158 | | |
159 | 159 | | |
160 | | - | |
| 160 | + | |
161 | 161 | | |
162 | | - | |
| 162 | + | |
163 | 163 | | |
164 | 164 | | |
165 | 165 | | |
| |||
0 commit comments