<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>book/src/guides/injection.md - fork/helix @ master</title>
<meta name="description" content="book/src/guides/injection.md in fork/helix at master.">
<meta property="og:title" content="book/src/guides/injection.md - fork/helix @ master">
<meta property="og:description" content="book/src/guides/injection.md in fork/helix at master.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="master" data-tip="10f07d7eb089430930e6d3547a98b440b927d025">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/helix</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/helix</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">Niklas Gruhn</span><span class="commit-message" data-commit="8b952bb1d5560bda283bf81d2a95cec62e031e09">docs: another injection query example (#13312)</span><span class="snapshot-sha sha" data-commit="8b952bb1d5560bda283bf81d2a95cec62e031e09">8b952bb1</span><time datetime="2025-04-09T14:30:11+02:00" title="2025-04-09 14:30:11 +0200">2025-04-09</time></p>
<header class="topbar"><details class="switcher"><summary>master</summary><div class="menu"><strong>branches</strong><a class="current" href="/fork/helix/ref/master/">master</a><strong>tags</strong><a href="/fork/helix/ref/23.05/">23.05</a><a href="/fork/helix/ref/23.10/">23.10</a><a href="/fork/helix/ref/24.03/">24.03</a><a href="/fork/helix/ref/24.07/">24.07</a><a href="/fork/helix/ref/25.01/">25.01</a><a href="/fork/helix/ref/25.01.1/">25.01.1</a><a href="/fork/helix/ref/25.07/">25.07</a><a href="/fork/helix/ref/25.07.1/">25.07.1</a><a class="all" href="/fork/helix/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/helix/">helix</a> / <a href="/fork/helix/ref/master/tree/book/">book</a> / <a href="/fork/helix/ref/master/tree/book/src/">src</a> / <a href="/fork/helix/ref/master/tree/book/src/guides/">guides</a> / <span class="cur">injection.md</span></nav>
<span class="view-stats"><span>2.5 KiB</span><span>65 lines</span></span><span class="actions"><a class="raw" href="/fork/helix/raw/c94dadba1e9d523410aa26baa451e0c4701be953/book/src/guides/injection.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><h2>Adding Injection Queries</h2>
<p>Writing language injection queries allows one to highlight a specific node as a different language.
In addition to the <a href="https://tree-sitter.github.io/tree-sitter/3-syntax-highlighting.html#language-injection">standard</a> language injection options used by tree-sitter, there
are a few Helix specific extensions that allow for more control.</p>
<p>An example of a simple query that would highlight all strings as bash in Nix:</p>
<pre class="language-query"><a-p>((</a-p><a-v>string_expression</a-v> <a-p>(</a-p><a-v>string_fragment</a-v><a-p>)</a-p> <a-p>@</a-p><a-t>injection.content</a-t><a-p>)</a-p>
  <a-p>(#</a-p><a-f>set</a-f><a-p>!</a-p> <a-pr>injection.language</a-pr> <a-s>&quot;bash&quot;</a-s><a-p>))</a-p></pre>
<p>Another example is this query, which highlights links in comments and keywords like "TODO", by reusing the dedicated "comment" language:</p>
<pre>((comment) @injection.content
  (#set! injection.language &quot;comment&quot;))
</pre>
<h2>Capture Types</h2>
<ul>
<li>
<p><code>@injection.language</code> (standard):
The captured node may contain the language name used to highlight the node captured by
<code>@injection.content</code>.</p>
</li>
<li>
<p><code>@injection.content</code> (standard):
Marks the content to be highlighted as the language captured with <code>@injection.language</code> <em>et al</em>.</p>
</li>
<li>
<p><code>@injection.filename</code> (extension):
The captured node may contain a filename with a file-extension known to Helix,
highlighting <code>@injection.content</code> as that language. This uses the language extensions defined in
both the default languages.toml distributed with Helix, as well as user defined languages.</p>
</li>
<li>
<p><code>@injection.shebang</code> (extension):
The captured node may contain a shebang used to choose a language to highlight as. This also uses
the shebangs defined in the default and user <code>languages.toml</code>.</p>
</li>
</ul>
<h2>Settings</h2>
<ul>
<li>
<p><code>injection.combined</code> (standard):
Indicates that all the matching nodes in the tree should have their content parsed as one
nested document.</p>
</li>
<li>
<p><code>injection.language</code> (standard):
Forces the captured content to be highlighted as the given language</p>
</li>
<li>
<p><code>injection.include-children</code> (standard):
Indicates that the content node’s entire text should be re-parsed, including the text of its child
nodes. By default, child nodes’ text will be excluded from the injected document.</p>
</li>
<li>
<p><code>injection.include-unnamed-children</code> (extension):
Same as <code>injection.include-children</code> but only for unnamed child nodes.</p>
</li>
</ul>
<h2>Predicates</h2>
<ul>
<li>
<p><code>#eq?</code> (standard):
The first argument (a capture) must be equal to the second argument
(a capture or a string).</p>
</li>
<li>
<p><code>#match?</code> (standard):
The first argument (a capture) must match the regex given in the
second argument (a string).</p>
</li>
<li>
<p><code>#any-of?</code> (standard):
The first argument (a capture) must be one of the other arguments (strings).</p>
</li>
</ul>
</section><div class="code-panel"><pre class="code src language-markdown"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text"><a-p>##</a-p> <a-tt>Adding Injection Queries</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">Writing language injection queries allows one to highlight a specific node as a different language.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text">In addition to the [standard][upstream-docs] language injection options used by tree-sitter, there</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">are a few Helix specific extensions that allow for more control.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text">An example of a simple query that would highlight all strings as bash in Nix:</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text"><a-p>```</a-p><a-tl>scm</a-tl></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text"><a-p>((string_expression (string_fragment) @injection.content)</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text"><a-p>  (#set! injection.language &quot;bash&quot;))</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text"><a-p>Another example is this query, which highlights links in comments and keywords like &quot;TODO&quot;, by reusing the dedicated &quot;comment&quot; language:</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text"><a-p>((comment) @injection.content</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L15" href="#L15">15</a><span class="code-text"><a-p>  (#set! injection.language &quot;comment&quot;))</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L16" href="#L16">16</a><span class="code-text"><a-p>```</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L17" href="#L17">17</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L18" href="#L18">18</a><span class="code-text"><a-p>## </a-p><a-tt>Capture Types</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L19" href="#L19">19</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L20" href="#L20">20</a><span class="code-text"><a-p>- `@injection.language` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text"><a-p>The captured node may contain the language name used to highlight the node captured by</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text"><a-p>`@injection.content`.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"><a-p>- `@injection.content` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text"><a-p>Marks the content to be highlighted as the language captured with `@injection.language` _et al_.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text"><a-p>- `@injection.filename` (extension):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L28" href="#L28">28</a><span class="code-text"><a-p>The captured node may contain a filename with a file-extension known to Helix,</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L29" href="#L29">29</a><span class="code-text"><a-p>highlighting `@injection.content` as that language. This uses the language extensions defined in</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L30" href="#L30">30</a><span class="code-text"><a-p>both the default languages.toml distributed with Helix, as well as user defined languages.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L31" href="#L31">31</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L32" href="#L32">32</a><span class="code-text"><a-p>- `@injection.shebang` (extension):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L33" href="#L33">33</a><span class="code-text"><a-p>The captured node may contain a shebang used to choose a language to highlight as. This also uses</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L34" href="#L34">34</a><span class="code-text"><a-p>the shebangs defined in the default and user `languages.toml`.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L35" href="#L35">35</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L36" href="#L36">36</a><span class="code-text"><a-p>## </a-p><a-tt>Settings</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L37" href="#L37">37</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L38" href="#L38">38</a><span class="code-text"><a-p>- `injection.combined` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L39" href="#L39">39</a><span class="code-text"><a-p>Indicates that all the matching nodes in the tree should have their content parsed as one</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L40" href="#L40">40</a><span class="code-text"><a-p>nested document.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L41" href="#L41">41</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L42" href="#L42">42</a><span class="code-text"><a-p>- `injection.language` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L43" href="#L43">43</a><span class="code-text"><a-p>Forces the captured content to be highlighted as the given language</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L44" href="#L44">44</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L45" href="#L45">45</a><span class="code-text"><a-p>- `injection.include-children` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L46" href="#L46">46</a><span class="code-text"><a-p>Indicates that the content node’s entire text should be re-parsed, including the text of its child</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L47" href="#L47">47</a><span class="code-text"><a-p>nodes. By default, child nodes’ text will be excluded from the injected document.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L48" href="#L48">48</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L49" href="#L49">49</a><span class="code-text"><a-p>- `injection.include-unnamed-children` (extension):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L50" href="#L50">50</a><span class="code-text"><a-p>Same as `injection.include-children` but only for unnamed child nodes.</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L51" href="#L51">51</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L52" href="#L52">52</a><span class="code-text"><a-p>## </a-p><a-tt>Predicates</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L53" href="#L53">53</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L54" href="#L54">54</a><span class="code-text"><a-p>- `#eq?` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L55" href="#L55">55</a><span class="code-text"><a-p>The first argument (a capture) must be equal to the second argument</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L56" href="#L56">56</a><span class="code-text"><a-p>(a capture or a string).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L57" href="#L57">57</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L58" href="#L58">58</a><span class="code-text"><a-p>- `#match?` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L59" href="#L59">59</a><span class="code-text"><a-p>The first argument (a capture) must match the regex given in the</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L60" href="#L60">60</a><span class="code-text"><a-p>second argument (a string).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L61" href="#L61">61</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L62" href="#L62">62</a><span class="code-text"><a-p>- `#any-of?` (standard):</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L63" href="#L63">63</a><span class="code-text"><a-p>The first argument (a capture) must be one of the other arguments (strings).</a-p></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L64" href="#L64">64</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L65" href="#L65">65</a><span class="code-text"><a-tu>[upstream-docs]</a-tu><a-p>: </a-p><a-tu>https://tree-sitter.github.io/tree-sitter/3-syntax-highlighting.html#language-injection</a-tu></span></span></pre></div></div>
</main>
</body>
</html>
