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

LPC

by abathur ST3

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

Labels language syntax

Details

Installs

  • Total 87
  • Win 49
  • OS X 25
  • Linux 13
Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5 Sep 4
Windows 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 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 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

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.