Add Odin syntax highlighting

[santerijps]

Syntax highlighting support for Odin

This PR adds syntax highlighting for the Odin programming language.

• ADD Odin syntax definition odin.lsh and highlighting test odin.odin
• UPDATE markdown.lsh to handle Odin code blocks and markdown.md highlighting test

Test Screenshots

odin.odin

How to replicate:

cargo run -p lsh-bin -- render --input .\assets\highlighting-tests\odin.odin .\crates\lsh\definitions\

markdown.md

How to replicate:

cargo run -p lsh-bin -- render --input .\assets\highlighting-tests\markdown.md .\crates\lsh\definitions\

[santerijps]

@microsoft-github-policy-service agree

[Copilot]

Pull request overview

This PR adds Odin language syntax highlighting to the lsh highlighting system, including direct .odin file associations and Markdown fenced-code-block highlighting.

Changes:

• Added a new Odin language definition (odin.lsh) with file association for **/*.odin.
• Updated the Markdown highlighter to dispatch ```odin fenced blocks to the Odin highlighter.
• Added/updated highlighting test fixtures for Odin and Markdown.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
crates/lsh/definitions/odin.lsh	New Odin syntax definition and file association.
crates/lsh/definitions/markdown.lsh	Adds fenced-code-block dispatch for odin.
assets/highlighting-tests/odin.odin	New Odin highlighting fixture covering comments/strings/keywords/etc.
assets/highlighting-tests/markdown.md	Extends Markdown fixture with an odin fenced block.

Comments suppressed due to low confidence (1)

crates/lsh/definitions/odin.lsh:43

• The directive matcher /#\w+/ won’t match Odin’s #+... directives (e.g. the test file starts with #+feature ...), so those tokens won’t be highlighted as keywords. Consider broadening the pattern to include #+ (and any other directive prefixes you want to support) so #+feature is highlighted consistently with #assert, #partial, etc.

        } else if /(?:true|false|nil)\>/ {
            yield constant.language;
        } else if /#\w+/ {
            yield keyword.other;
        } else if /@/ {

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

[santerijps]

@copilot apply changes based on the comments in this thread

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

Comments suppressed due to low confidence (1)

crates/lsh/definitions/odin.lsh:50

• The numeric literal regex allows a trailing . with no following digits ([\d_]+\.?[\d_]*), which will likely mis-tokenize Odin range expressions like 0..<10 by consuming 0. as a number. Consider tightening the float alternatives so a decimal point is only matched when followed by at least one digit (and keep the leading-dot form like .5 if desired).

        } else if /(?i:-?(?:0x[\da-fA-F_]+|0b[01_]+|0o[0-7_]+|[\d_]+\.?[\d_]*|\.[\d_]+)(?:e[+-]?[\d_]+)?i?)/ {
            if /\w+/ {
                // Invalid numeric literal
            } else {
                yield constant.numeric;
            }

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

crates/lsh/definitions/odin.lsh:57

• The numeric literal regex will consume the first . in range expressions like 0..<10 (common in Odin), highlighting 0. as a float and leaving the remaining .< to be parsed separately. Consider adjusting the float alternative to require at least one digit after the decimal point (or otherwise avoid matching a trailing .) so range operators aren’t partially consumed by the number matcher.

        } else if /(?i:-?(?:0x[\da-fA-F_]+|0b[01_]+|0o[0-7_]+|[\d_]+\.?[\d_]*|\.[\d_]+)(?:e[+-]?[\d_]+)?i?)/ {
            if /\w+/ {
                // Invalid numeric literal
            } else {
                yield constant.numeric;
            }