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

LPC

by abathur ST3

Sublime syntax highlighting support for LDMud / LPC (Lars Pensjö C)

Details

Installs

  • Total 80
  • Win 44
  • OS X 24
  • Linux 12
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 Mar 11 Mar 10 Mar 9
Windows 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 0 0 0 0 0 0 0 0
OS X 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 1 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

SublimeLPC

Sublime syntax highlighting support for LDMud / LPC (Lars Pensjö C)

Note: only for ST3 Builds >= 3084

This is a working draft of Sublime Text 3 syntax highlighting for the LPC language, used to develop within LDMud. I could use your help pushing development forward. While the issue tracker (https://github.com/abathur/SublimeLPC/issues) will give you some idea of where to jump in, the most important tasks at the moment are:

  1. identifying missing language features, edge cases in current matching, scopes that should be matched but aren't, scopes that need renaming, etc. (via pull request or issue tracker)
  2. gathering feedback on the “Open” questions in the issue tracker
  3. finishing out a robust, compiling syntax_test of the LPC language (see /test).

If you'd like to help develop SublimeLPC directly, you can:

  1. remove any local copy of SublimeLPC (either through package control, or removing the directory if you cloned it)
  2. fork this repo
  3. git clone your fork into your ST3/Packages/ directory
  4. create a new branch, improve SublimeLPC, and submit a pull request

Any matching/scope changes should be accompanied by updates to the test cases (either to just keep scopes in sync, or add tests that will pass when the bug or edge case is fixed.)

See http://www.sublimetext.com/docs/3/syntax.html for details on the syntax format.