deathaxe
deathaxe
Find Results tab is not linked to a file and thus CTags can't determine the folder to search .tags files in. A solution would require to parse "Find Results" content...
Some general advices: `main` and `prototype` are primary entry points and thus shouldn't be located somewhere in the middle of anywhere. They should be the first contexts. I'd recommend to...
FWIW, context order and structure of existing C syntaxes may not be ideal nor a good template to rely on. Better look at something more recent, such as Java, PHP...
C++ is expected to fail at this point. That's step 2. Maybe even disable its tests to be able to focus on C in the meanwhile.
Not sure how useful #1831 still is. It came with some interesting parts, but scoping variable definitions `entity.name` is not that great. Maybe some things can even be solved with...
I'd vote to remove [C++.sublime-settings](https://github.com/sublimehq/Packages/blob/master/C%2B%2B/C%2B%2B.sublime-settings) and properly decide whether to scope it as C or C++ via `file_extensions` in syntax definitions.
A specific type would reveal accidental comparisons between view ids and buffer ids for instance, both of which are not related with each other.
What syntax is displayed for ps1 files in status bar? Is PowerShell package disabled (in `ignored_packages` list)? Maybe ps1 extension was assigned another syntax before?
Closing due to inactivity.
JSON schemas have been created at https://github.com/wbond/package_control/blob/four-point-oh/sublime-package.json for use in ST. I also have them explicitly, locally.