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

HLSL Syntax

by MattSutherlin ST3

HLSL syntax highlighting for Sublime Text 3

Details

Installs

  • Total 1K
  • Win 1K
  • OS X 139
  • Linux 51
Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 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
Windows 0 1 2 4 1 0 0 2 5 1 6 3 2 4 3 1 3 1 7 3 0 1 6 3 1 0 2 1 1 6 2 2 1 1 0 5 2 4 2 5 1 2 4 0 1 5
OS X 1 0 0 1 0 0 2 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 2 0
Linux 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 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

HLSL_ST3

HLSL tools for Sublime Text 3

I'm just trying to provide a better, more fully featured editing environment for HLSL.

A large part of that is the syntax file, where the goal is to hook as much as possile into Sublime's symbol indexer in the most correct, most granular way possible. Functions (and function-esque macros) will link between defintions and call sites in both directions, via GoTo Defintion and GoTo Reference. Structs link from usage to definition, via GoTo Definition. Most everything else will at least get scoped for theme coloration, but more universal coverage towards scope-aware autocompletions is a (long-term) work in progress.

Additionally, right clicking include directives to open the referenced file is now supported. By default, it will attempt to open relative to the same directory as the incuding file, but user settings allow additional include paths to be provided.

Everything works best when your shader source is in an active sublime-project file. Otherwise, some features may only work across open files instead of all of your files.

Best with my HLSL-centric theme, Rocklobster: https://github.com/MattSutherlin/RockLobster_ST3Theme