[BUG ST2/3] set_syntax_file() clear 'is_widget' setting

[bizoo]

view.set_syntax_file() remove the ‘is_widget’ setting of the view.

If you type this code (line after line) in the console:

v = window.show_input_panel('test', '', None, None,None) print(v.settings().get('is_widget')) v.set_syntax_file('Python.tmLanguage') print(v.settings().get('is_widget'))
you’ll notice that the first print statement write True, and the second None.
So keybindings that use a context on setting.is_widget does not work correctly.

[facelessuser]

Nice catch. I have always wondered why “is_widget” seemed so flaky.

[bizoo]

Nice catch. I have always wondered why “is_widget” seemed so flaky.

There’s a simple workaround in this issue: github.com/randy3k/AlignTab/issues/16

Now maybe this is not the only thing (API or command) that change this setting, only Jon can tell…

[bizoo]

Bump!
Please look at it.

[kingkeith]

I suggest logging it here:

SublimeTextIssues/Core

[FichteFoll]

Also take a look here (and reference the threads)

API Suggestions

More consistent output panels Output panels have really odd behaviors currently. In exec.py, there is this code: if not hasattr(self, 'output_view'): # Try not to call get_output_panel until the regexes are assigned self.output_view = self.window.create_output_panel("exec") # [...] self.output_view.settings().set("result_file_regex", file_regex) self.output_view.settings().set("result_line_regex", line_regex) self.output_view.settings().set("result_base_dir", working_dir) self.outp…

Interface Suggestions Discussion: Style console output

Continuing the discussion from Interface Suggestions: Iirc there was a theme that added syntax coloring to the console a while back. I'm not sure how they did it though? Probably some widget settings stuff. This is also used to highlight regular expressions in the find panel, but I don't know how ST knows to only color the find panel and not any of the other widgets. Hint's welcome. If this was eventually added as a default feature (which I'm strongly in favor of), I'd like to work on a REPL…

[kingkeith]

Just as an experiment, I tried a few things and discovered that it re-attains it’s is_widget setting if you show the input panel again (it re-uses the same view object). Although, it loses the syntax that was set, so it’s not a valid workaround.

>>> v = window.show_input_panel('test', '', None, None, None)
>>> print(v.settings().get('is_widget'), v.settings().get('syntax'), v.id(), v.settings().get('gutter'))
True Packages/Text/Plain text.tmLanguage 3 False
>>> v.assign_syntax('Packages/Python/Python.sublime-syntax')
>>> print(v.settings().get('is_widget'), v.settings().get('syntax'), v.id(), v.settings().get('gutter'))
None Packages/Python/Python.sublime-syntax 3 True
>>> v2 = window.show_input_panel('test', '', None, None, None)
>>> print(v2.settings().get('is_widget'), v2.settings().get('syntax'), v2.id(), v2.settings().get('gutter'), v == v2)
True Packages/Text/Plain text.tmLanguage 3 False True

So it looks like there is some internal logic that shows the gutter and removes the is_widget setting when a syntax definition is applied to the view