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 997
  • Linux 752
Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18
Windows 0 0 0 0 0 0 1 0 0 1 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 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 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.