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 960
  • Linux 736
Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 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
Windows 0 0 0 1 1 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Mac 0 0 0 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 0 0 0 0 0 0 0 0 0 0 0 1
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 1 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.