deathaxe

Downloading Godot, adding the reference and restarting Omnisharp was the only steps I needed to do to fix it on my end.

Yes, settings actually don't work. See #28 for given code lense setting in particular or #44 for the reason why. You can however control omnisharp settings by placing an omnisharp.json...

sublime-project file is not important. Some language servers just require the main project folder to be the first folder in ST's sidebar. It may not be the case for Omnisharp,...

The only idea left is checking _LSP Log Panel_ for some useful hints printed by OmniSharp language server. Maybe it tells us, what's missing. Loading your project on my end...

I assumed you got that update already. It may indeed make a difference as previous release shipped Omnisharp based on net471, which may not be fully compatible with .NET6+ and...

IIRC, it was already announced that extending drop targets to e.g. buffer is not a priority due to various technical difficulties.

Please avoid that. It will have potential netative side effects with A File Icons, which already creates such stubs for all sorts of files. Maybe rather just have a look...

Things may become wonky as soon as scope names and/or associated `file_type_...` names differ between packages. This may cause no icons to be displayed for such types. Yes, custom icons...

This wouldn't probably change anything if multiple packages define concurrent resources. It would just avoid those syntax stubs. But maybe raise other issues. Assigning an extension to a new syntax...

It doesn't neccesarily list existing packages as "to enable".