lark-parser/lark_syntax

Lark-flavoured EBNF grammar syntax definition for Sublime Text or TextMate

lark_syntax's Issues

TextMate 2 .tmbundle support?

Unless I'm mistaken, these files need to be bundled into a .tmbundle in order to be used in TextMate 2. Are there any plans to make this available?

Thanks.

Syntax break when line ends with repeat-exactly-n-times

Was goofing around a little and noticed that syntax highlighting breaks when a line ends with the exact repetition form. It seems to get back on track if I add any other literal, rule, the range form, etc.

In case it ends up mattering, plugin version 1.2.1, ST3 build 3180, on macos 10.14.

syntax highlighting for vim

Just writing a note to let you know I threw together a very basic syntax highlighting script for vim, since that is the editor I use

https://github.com/jisaacstone/lark.vim

Doesn't have the fancy regex highlighting, but better'n nothing. Hopefully someone else can find it useful

Syntax break after escaped double quotes "\""

BACKTICK     : "`"
PERCENTAGE   : "%"
EXCLAMATION  : "!"
DOUBLE_QUOTE : "\""

?parens       : OPEN_PAREN | CLOSE_PAREN | OPEN_BRACKET | CLOSE_BRACKET
OPEN_BRACKET  : "["
CLOSE_BRACKET : "]"
OPEN_BRACE    : "{"
CLOSE_BRACE   : "}"
OPEN_PAREN    : "("
CLOSE_PAREN   : ")"

installation

how do you install it in Sublime ?

Syntax breaks after regular expression: /\/\*([\s\S]*?)\*\//

// General non terminal constructs
free_input_string: /(\\{|\\}|[^\n{}])+/

SINGLE_LINE_COMMENT: /(\#|\/\/)[^\n]*/
// MULTI_LINE_COMMENT: /\/\*([\s\S]*?)\*\//

NEWLINE: (CR? LF)+
_NEWLINE: ( /\r?\n[\t ]*/ | SINGLE_LINE_COMMENT )+
INTEGER: "0".."9"

Commenting out the line fixes it:

interactive feedback on currently open grammar file ?

Would it be feasible to add a feature for the user to check his grammar in the editor ?

I am thinking something along the lines of https://omrelli.ug/nearley-playground/
that provides an interactive feedback to the user creating a grammar, via examples.
Or maybe being able to use the lark for syntax highlighting in other open files...

Of course, many kind of visualisations are possible (showing parse trees, etc.).
The point here is to get some bare minimum of interactive feedback directly in the editor, without having to code anything.