ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

IDL-Syntax

by andik ALL

simple IDL (Microsoft midl, Mozilla WebIDL) syntax highlighting for Sublime Text

Details

Installs

  • Total 3K
  • Win 1K
  • Mac 998
  • Linux 752
Aug 31 Aug 30 Aug 29 Aug 28 Aug 27 Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18
Windows 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

IDL syntax highlighting

This package provides a simple IDL (Microsoft midl, Mozilla WebIDL) syntax highlighting, derived from Sublime's standard C++ highlighting. It provides you with correct symbol detection, which was the main reason to create this.

No fancy stuff here, no additional functionality, no snippets

If you want highlighting for WebIDL in the new Sublime Text Format, look at the package from vinyldarkscratch.

Note about Scopes

(This is only due to the use of Textmate Syntax highlighting which seems to have a worldwide global namespace. It has little effect to the end user.)

This file was primarily intended for highlighting MS IDL files (used by Windows COM Interfaces). But people seem to be more interested in highlighting webIDL Files, where this file seems to work too. Because of a namespace glitch in I was asked to rename the scope of this syntax highlighting and did so. Scope is now source.webidl.

Because I'm not willing to maintain two files this new scopename does also apply to MS IDL files in future. This is not completely correct, but does not have any influence on the functionality in regard of MS IDL files. Except you wrote your own extensions for this scope. In this case, you need to modify them to match the new scope. Or just let me know, maybe we can have a solution for both sides.