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 990
  • Linux 749
Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10
Windows 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 1 1 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 1 0 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 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 1 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.