Support multi-language documents
See original GitHub issueNow that Cursorless supports HTML (great job!) it would be amazing if it could also support nested languages inside of HTML. For example JS/TS inside of <script>
tags, and CSS/SCSS inside of <style>
tags.
This would be super helpful for web developers. Because plenty of popular frameworks (such as Vue) use single file components, where HTML, JS and CSS are all located in the same file.
I assume that this documentation is relevant to this issue: https://tree-sitter.github.io/tree-sitter/using-parsers#multi-language-documents
- JS and CSS support inside of HTML
- Code blocks within markdown
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:20 (12 by maintainers)
Top Results From Across the Web
Creating Multi-Language Documents with HotDocs
HotDocs technology helps to improve the end-user experience by enabling the simple creation of documents in a variety of languages, producing error-free, ...
Read more >Creating Multi-Language Documents (Brief Guide)
Automating multi-language documents can be a cinch with the best document automation software. You can get the measurements, currencies, dates, ...
Read more >Multilingual Support - LogicalDOC
LogicalDOC is an international Document Management System that supports a wide variety of languages. Language support means more than a simple translation ...
Read more >Multiple Language Support and Localization - infoRouter
infoRouter offers Multiple Language Support and Localization in Document Management software for a global economy.
Read more >Serving Multilingual Online Documentation
We at SCO have implemented our help, online documentation and manual pages using WWW architecture, and because we control both the client and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome! Solid research. We should think about how this connects to rewriting our language defs using this query language. Cc/ @wenkokke
One minor thing I’ll add: helix also maintains its own injection regexes in case for whatever reason we need to steal those. They’re all in one file, see eg rust
Just to be clear, by “incremental parsing”, I mean updating the parse tree as the document changes, which tree-sitter is able to do efficiently without reparsing the entire document. Here’s where we do it in the parse-tree extension: https://github.com/cursorless-dev/vscode-parse-tree/blob/4af875b7cbd72d68c1e1eafe43ddabc3403264ce/src/extension.ts#L109-L134