Skip to content

[Feature]: Syntax highlighting for MATLAB (.m) and LaTeX (.tex) #10363

Closed
innocarpe/orca
#50

Description

@Jhnnn001

Problem or use case

.m and .tex files have no syntax highlighting — everything renders in one
flat color (see screenshot). Other languages highlight fine.

Syntax highlighting for MATLAB (.m) and LaTeX (.tex)

Image

Environment

  • Orca 1.4.153-rc.3, macOS

Proposed solution

Standard syntax highlighting: comments, keywords, strings, and commands
each get their own color, as they do for supported languages.

Alternatives or additional context

No response

Activity

  1. added theissue type on Jul 24, 2026
  2. innocarpe commented on Jul 24, 2026

    @innocarpe
    Contributor

    I'd like to take this.

    Plan: Wire .m → MATLAB (vendored MathWorks TextMate grammar, same registration path as Nim) and .tex/.ltx/.sty/.cls → LaTeX (presentation-only Monarch for comments, commands, environments, and math — full VS Code LaTeX TextMate pulls many embedded language scopes). Update detectLanguage so the editor opens them with the new language ids.

    PR shortly.

  3. nicolaschapados commented on Sep 7, 2026

    @nicolaschapados

    This would really be a nice addition (especially .tex files).

  4. evaristocosta commented on Sep 24, 2026

    @evaristocosta

    I agree, having .tex files would be a great and important addition.

  5. nwparker commented on Oct 30, 2026

    @nwparker
    Contributor

    Thanks for the request! Both halves are now available as official plugins: LaTeX Syntax for .tex/.ltx/.sty, and the new MATLAB Syntax for .m.

    To install: Settings → Plugins → turn on plugins → search for it and install. It needs Orca 1.4.246 or newer (older versions show "Needs Orca 1.4.246"), because that's the first release where an enabled plugin syntax takes precedence over Orca's own mapping for these files. Note that while MATLAB Syntax is on, every .m file is highlighted as MATLAB, including Objective-C sources.

    Credit to @innocarpe, whose PR #10371 this replaces; they're a co-author of the plugin commit. If it falls short for you, please reopen and tell us what is missing.

  6. added a commit that references this issue on Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions