Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.9k
runtime(leex): add leex filetype support#18832
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Conversation
leex is the lexical analyzer generator for Erlang. Its input file formatfollows a section-based structure and uses the `.xrl` file extension.https://www.erlang.org/doc/apps/parsetools/leex.htmlThis initial work includes file detection, an ftplugin (which inheritsthe Erlang configuration), and a syntax definition.
jparise commentedNov 29, 2025
| runtime/syntax/kotlin.vim@udalov | ||
| runtime/syntax/kdl.vim@imsnif@jiangyinzuo | ||
| runtime/syntax/krl.vim@KnoP-01 | ||
| runtime/syntax/leex.vim@jparise |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
@hcs42 I wasn't sure if you wanted to maintain these files, as well. I'm happy to reassign them to you or co-maintain them, any way you prefer.
runtime/syntax/leex.vim Outdated
| " Maintainer: Jon Parise <jon@indelible.org> | ||
| " Last Change: 2025 Nov 28 | ||
| " Filenames: *.xrl | ||
| " URL: https://www.erlang.org/doc/apps/parsetools/leex.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This header field is used for the upstream repo or download. I'd just add this as a comment below the header block or in a "References: " field likecs.vim etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
That sounds good. I've also seenRepository: used for upstream repos.
runtime/syntax/leex.vim Outdated
| finish | ||
| endif | ||
| syninclude@Erlangsyntax/erlang.vim |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
There's probably exceptions in the repo but this cluster should also use theleex prefix - so,@leexErlang.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Good idea. I'll fix up some of my other projects to do this, too. 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
@dkearns I also see that many syntax files use<sfile>:p:h/... to explicitly reference the runtime-included file. Because I'm not referencing any specific Erlang syntax elements, I think this could go either way here (because it's presumably fine if a higher-precedence runtimepatherlang syntax is used). Any preference?
leex is the lexical analyzer generator for Erlang. Its input file format follows a section-based structure and uses the
.xrlfile extension.https://www.erlang.org/doc/apps/parsetools/leex.html
This initial work includes file detection, an ftplugin (which inherits the Erlang configuration), and a syntax definition.