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 210
  • Win 128
  • Mac 51
  • Linux 31
Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6 Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12
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 1 0
Mac 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 1 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.