0
Not a bug
Bug in View.syntax_name()
Traceback I got when trying this from the command line.
>>> window.active_view().syntax_name()
Traceback (most recent call last):
File "<string>", line 1, in <module>
Boost.Python.ArgumentError: Python argument types in
View.syntax_name(View)
did not match C++ signature:
syntax_name(SP<TextBufferView>, long long)
>>> window.active_view().syntax_name()
Traceback (most recent call last):
File "<string>", line 1, in <module>
Boost.Python.ArgumentError: Python argument types in
View.syntax_name(View)
did not match C++ signature:
syntax_name(SP<TextBufferView>, long long)
Answer
Answer
Not a bug
This is working as expected: syntax_name() takes a point, and will return the scope name at that point. The name isn't ideal.
If you want the name of the syntax file currently in use, you can use view.settings().get('syntax')
If you want the name of the syntax file currently in use, you can use view.settings().get('syntax')
Customer support service by UserEcho
If you want the name of the syntax file currently in use, you can use view.settings().get('syntax')