<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>docs/architecture.md - fork/helix @ 23.05</title>
<meta name="description" content="docs/architecture.md in fork/helix at 23.05.">
<meta property="og:title" content="docs/architecture.md - fork/helix @ 23.05">
<meta property="og:description" content="docs/architecture.md in fork/helix at 23.05.">
<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="23.05" data-tip="7f5940be80eaa3aec7903903072b7108f41dd97b">
<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">A-Walrus</span><span class="commit-message" data-commit="1378b911b63f4fdab7beba77de6d54f1dd070553">Fix some typos (#2978)</span><span class="snapshot-sha sha" data-commit="1378b911b63f4fdab7beba77de6d54f1dd070553">1378b911</span><time datetime="2022-07-06T05:49:54+03:00" title="2022-07-06 05:49:54 +0300">2022-07-06</time></p>
<header class="topbar"><details class="switcher"><summary>23.05</summary><div class="menu"><strong>branches</strong><a href="/fork/helix/ref/master/">master</a><strong>tags</strong><a class="current" 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/23.05/tree/docs/">docs</a> / <span class="cur">architecture.md</span></nav>
<span class="view-stats"><span>4.7 KiB</span><span>111 lines</span></span><span class="actions"><a class="raw" href="/fork/helix/raw/5d33cbac06b7bf015156d3e5c8e699c374fc2fa8/docs/architecture.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"><table><thead><tr><th>Crate</th><th>Description</th></tr></thead><tbody>
<tr><td>helix-core</td><td>Core editing primitives, functional.</td></tr>
<tr><td>helix-lsp</td><td>Language server client</td></tr>
<tr><td>helix-dap</td><td>Debug Adapter Protocol (DAP) client</td></tr>
<tr><td>helix-loader</td><td>Functions for building, fetching, and loading external resources</td></tr>
<tr><td>helix-view</td><td>UI abstractions for use in backends, imperative shell.</td></tr>
<tr><td>helix-term</td><td>Terminal UI</td></tr>
<tr><td>helix-tui</td><td>TUI primitives, forked from tui-rs, inspired by Cursive</td></tr>
</tbody></table>
<p>This document contains a high-level overview of Helix internals.</p>
<blockquote>
<p>NOTE: Use <code>cargo doc --open</code> for API documentation as well as dependency
documentation.</p>
</blockquote>
<h2>Core</h2>
<p>The core contains basic building blocks used to construct the editor. It is
heavily based on <a href="https://codemirror.net/6/docs/">CodeMirror 6</a>. The primitives
are functional: most operations won't modify data in place but instead return
a new copy.</p>
<p>The main data structure used for representing buffers is a <code>Rope</code>. We re-export
the excellent <a href="https://github.com/cessen/ropey">ropey</a> library. Ropes are cheap
to clone, and allow us to easily make snapshots of a text state.</p>
<p>Multiple selections are a core editing primitive. Document selections are
represented by a <code>Selection</code>. Each <code>Range</code> in the selection consists of a moving
<code>head</code> and an immovable <code>anchor</code>. A single cursor in the editor is simply
a selection with a single range, with the head and the anchor in the same
position.</p>
<p>Ropes are modified by constructing an OT-like <code>Transaction</code>. It represents
a single coherent change to the document and can be applied to the rope.
A transaction can be inverted to produce an undo. Selections and marks can be
mapped over a transaction to translate to a position in the new text state after
applying the transaction.</p>
<blockquote>
<p>NOTE: <code>Transaction::change</code>/<code>Transaction::change_by_selection</code> is the main
interface used to generate text edits.</p>
</blockquote>
<p><code>Syntax</code> is the interface used to interact with tree-sitter ASTs for syntax
highlighting and other features.</p>
<h2>View</h2>
<p>The <code>view</code> layer was supposed to be a frontend-agnostic imperative library that
would build on top of <code>core</code> to provide the common editor logic. Currently it's
tied to the terminal UI.</p>
<p>A <code>Document</code> ties together the <code>Rope</code>, <code>Selection</code>(s), <code>Syntax</code>, document
<code>History</code>, language server (etc.) into a comprehensive representation of an open
file.</p>
<p>A <code>View</code> represents an open split in the UI. It holds the currently open
document ID and other related state. Views encapsulate the gutter, status line,
diagnostics, and the inner area where the code is displayed.</p>
<blockquote>
<p>NOTE: Multiple views are able to display the same document, so the document
contains selections for each view. To retrieve, <code>document.selection()</code> takes
a <code>ViewId</code>.</p>
</blockquote>
<p><code>Info</code> is the autoinfo box that shows hints when awaiting another key with bindings
like <code>g</code> and <code>m</code>. It is attached to the viewport as a whole.</p>
<p><code>Surface</code> is like a buffer to which widgets draw themselves to, and the
surface is then rendered on the screen on each cycle.</p>
<p><code>Rect</code>s are areas (simply an x and y coordinate with the origin at the
screen top left and then a height and width) which are part of a
<code>Surface</code>. They can be used to limit the area to which a <code>Component</code> can
render. For example if we wrap a <code>Markdown</code> component in a <code>Popup</code>
(think the documentation popup with space+k), Markdown's render method
will get a Rect that is the exact size of the popup.</p>
<p>Widgets are called <code>Component</code>s internally, and you can see most of them
in <code>helix-term/src/ui</code>. Some components like <code>Popup</code> and <code>Overlay</code> can take
other components as children.</p>
<p><code>Layer</code>s are how multiple components are displayed, and is simply a
<code>Vec&lt;Component&gt;</code>. Layers are managed by the <code>Compositor</code>. On each top
level render call, the compositor renders each component in the order
they were pushed into the stack. This makes multiple components "layer"
on top of one another. Hence we get a file picker displayed over the
editor, etc.</p>
<p>The <code>Editor</code> holds the global state: all the open documents, a tree
representation of all the view splits, the configuration, and a registry of
language servers. To open or close files, interact with the editor.</p>
<h2>LSP</h2>
<p>A language server protocol client.</p>
<h2>Term</h2>
<p>The terminal frontend.</p>
<p>The <code>main</code> function sets up a new <code>Application</code> that runs the event loop.</p>
<p><code>commands.rs</code> is probably the most interesting file. It contains all commands
(actions tied to keybindings).</p>
<p><code>keymap.rs</code> links commands to key combinations.</p>
<h2>TUI / Term</h2>
<p>TODO: document Component and rendering related stuff</p>
</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"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text">| Crate        | Description                                                      |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">| -----------  | -----------                                                      |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text">| helix-core   | Core editing primitives, functional.                             |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">| helix-lsp    | Language server client                                           |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">| helix-dap    | Debug Adapter Protocol (DAP) client                              |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text">| helix-loader | Functions for building, fetching, and loading external resources |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text">| helix-view   | UI abstractions for use in backends, imperative shell.           |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text">| helix-term   | Terminal UI                                                      |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text">| helix-tui    | TUI primitives, forked from tui-rs, inspired by Cursive          |</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text">This document contains a high-level overview of Helix internals.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text"></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>&gt; </a-p>NOTE: Use `cargo doc --open` for API documentation as well as dependency</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>&gt; </a-p>documentation.</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>Core</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">The core contains basic building blocks used to construct the editor. It is</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text">heavily based on [CodeMirror 6](https://codemirror.net/6/docs/). The primitives</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text">are functional: most operations won&#39;t modify data in place but instead return</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text">a new copy.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text">The main data structure used for representing buffers is a `Rope`. We re-export</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text">the excellent [ropey](https://github.com/cessen/ropey) library. Ropes are cheap</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text">to clone, and allow us to easily make snapshots of a text state.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L28" href="#L28">28</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L29" href="#L29">29</a><span class="code-text">Multiple selections are a core editing primitive. Document selections are</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L30" href="#L30">30</a><span class="code-text">represented by a `Selection`. Each `Range` in the selection consists of a moving</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L31" href="#L31">31</a><span class="code-text">`head` and an immovable `anchor`. A single cursor in the editor is simply</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 selection with a single range, with the head and the anchor in the same</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L33" href="#L33">33</a><span class="code-text">position.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L34" href="#L34">34</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L35" href="#L35">35</a><span class="code-text">Ropes are modified by constructing an OT-like `Transaction`. It represents</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 single coherent change to the document and can be applied to the rope.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L37" href="#L37">37</a><span class="code-text">A transaction can be inverted to produce an undo. Selections and marks can be</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L38" href="#L38">38</a><span class="code-text">mapped over a transaction to translate to a position in the new text state after</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L39" href="#L39">39</a><span class="code-text">applying the transaction.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L40" href="#L40">40</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L41" href="#L41">41</a><span class="code-text"><a-p>&gt; </a-p>NOTE: `Transaction::change`/`Transaction::change_by_selection` is the main</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>&gt; </a-p>interface used to generate text edits.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L43" href="#L43">43</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L44" href="#L44">44</a><span class="code-text">`Syntax` is the interface used to interact with tree-sitter ASTs for syntax</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L45" href="#L45">45</a><span class="code-text">highlighting and other features.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L46" href="#L46">46</a><span class="code-text"></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>##</a-p> <a-tt>View</a-tt></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">The `view` layer was supposed to be a frontend-agnostic imperative library that</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L50" href="#L50">50</a><span class="code-text">would build on top of `core` to provide the common editor logic. Currently it&#39;s</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L51" href="#L51">51</a><span class="code-text">tied to the terminal UI.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L52" href="#L52">52</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L53" href="#L53">53</a><span class="code-text">A `Document` ties together the `Rope`, `Selection`(s), `Syntax`, document</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L54" href="#L54">54</a><span class="code-text">`History`, language server (etc.) into a comprehensive representation of an open</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L55" href="#L55">55</a><span class="code-text">file.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L56" href="#L56">56</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L57" href="#L57">57</a><span class="code-text">A `View` represents an open split in the UI. It holds the currently open</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L58" href="#L58">58</a><span class="code-text">document ID and other related state. Views encapsulate the gutter, status line,</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L59" href="#L59">59</a><span class="code-text">diagnostics, and the inner area where the code is displayed.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L60" href="#L60">60</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L61" href="#L61">61</a><span class="code-text"><a-p>&gt; </a-p>NOTE: Multiple views are able to display the same document, so the document</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>&gt; </a-p>contains selections for each view. To retrieve, `document.selection()` takes</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>&gt; </a-p>a `ViewId`.</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">`Info` is the autoinfo box that shows hints when awaiting another key with bindings</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L66" href="#L66">66</a><span class="code-text">like `g` and `m`. It is attached to the viewport as a whole.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L67" href="#L67">67</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L68" href="#L68">68</a><span class="code-text">`Surface` is like a buffer to which widgets draw themselves to, and the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L69" href="#L69">69</a><span class="code-text">surface is then rendered on the screen on each cycle.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L70" href="#L70">70</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L71" href="#L71">71</a><span class="code-text">`Rect`s are areas (simply an x and y coordinate with the origin at the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L72" href="#L72">72</a><span class="code-text">screen top left and then a height and width) which are part of a</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L73" href="#L73">73</a><span class="code-text">`Surface`. They can be used to limit the area to which a `Component` can</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L74" href="#L74">74</a><span class="code-text">render. For example if we wrap a `Markdown` component in a `Popup`</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L75" href="#L75">75</a><span class="code-text">(think the documentation popup with space+k), Markdown&#39;s render method</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L76" href="#L76">76</a><span class="code-text">will get a Rect that is the exact size of the popup.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L77" href="#L77">77</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L78" href="#L78">78</a><span class="code-text">Widgets are called `Component`s internally, and you can see most of them</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L79" href="#L79">79</a><span class="code-text">in `helix-term/src/ui`. Some components like `Popup` and `Overlay` can take</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L80" href="#L80">80</a><span class="code-text">other components as children.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L81" href="#L81">81</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L82" href="#L82">82</a><span class="code-text">`Layer`s are how multiple components are displayed, and is simply a</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L83" href="#L83">83</a><span class="code-text">`Vec&lt;Component&gt;`. Layers are managed by the `Compositor`. On each top</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L84" href="#L84">84</a><span class="code-text">level render call, the compositor renders each component in the order</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L85" href="#L85">85</a><span class="code-text">they were pushed into the stack. This makes multiple components &quot;layer&quot;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L86" href="#L86">86</a><span class="code-text">on top of one another. Hence we get a file picker displayed over the</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L87" href="#L87">87</a><span class="code-text">editor, etc.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L88" href="#L88">88</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L89" href="#L89">89</a><span class="code-text">The `Editor` holds the global state: all the open documents, a tree</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L90" href="#L90">90</a><span class="code-text">representation of all the view splits, the configuration, and a registry of </span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L91" href="#L91">91</a><span class="code-text">language servers. To open or close files, interact with the editor.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L92" href="#L92">92</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L93" href="#L93">93</a><span class="code-text"><a-p>##</a-p> <a-tt>LSP</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L94" href="#L94">94</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L95" href="#L95">95</a><span class="code-text">A language server protocol client.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L96" href="#L96">96</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L97" href="#L97">97</a><span class="code-text"><a-p>##</a-p> <a-tt>Term</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L98" href="#L98">98</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L99" href="#L99">99</a><span class="code-text">The terminal frontend.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L100" href="#L100">100</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L101" href="#L101">101</a><span class="code-text">The `main` function sets up a new `Application` that runs the event loop.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L102" href="#L102">102</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L103" href="#L103">103</a><span class="code-text">`commands.rs` is probably the most interesting file. It contains all commands</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L104" href="#L104">104</a><span class="code-text">(actions tied to keybindings). </span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L105" href="#L105">105</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L106" href="#L106">106</a><span class="code-text">`keymap.rs` links commands to key combinations.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L107" href="#L107">107</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L108" href="#L108">108</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L109" href="#L109">109</a><span class="code-text"><a-p>##</a-p> <a-tt>TUI / Term</a-tt></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L110" href="#L110">110</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L111" href="#L111">111</a><span class="code-text">TODO: document Component and rendering related stuff</span></span></pre></div></div>
</main>
</body>
</html>
