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 231
  • Win 139
  • Mac 57
  • Linux 35
Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28
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
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 1 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 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

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.