<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>docs/help.md - fork/wezterm @ termiz-0.23.1</title>
<meta name="description" content="docs/help.md in fork/wezterm at termiz-0.23.1.">
<meta property="og:title" content="docs/help.md - fork/wezterm @ termiz-0.23.1">
<meta property="og:description" content="docs/help.md in fork/wezterm at termiz-0.23.1.">
<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="termiz-0.23.1" data-tip="7053748e4d899e7fc5e202d6f903b052fc78e759">
<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/wezterm</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/wezterm</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">Wez Furlong</span><span class="commit-message" data-commit="11c4b11669d9ce23d51afaf286b5383fbdc9794f">s,wez/wezterm,wezterm/wezterm,</span><span class="snapshot-sha sha" data-commit="11c4b11669d9ce23d51afaf286b5383fbdc9794f">11c4b1166</span><time datetime="2025-02-07T13:08:01-07:00" title="2025-02-07 13:08:01 -0700">2025-02-07</time></p>
<header class="topbar"><details class="switcher"><summary>termiz-0.23.1</summary><div class="menu"><strong>branches</strong><a href="/fork/wezterm/ref/main/">main</a><strong>tags</strong><a class="current" href="/fork/wezterm/ref/termiz-0.23.1/">termiz-0.23.1</a><a href="/fork/wezterm/ref/termiz-0.23.2/">termiz-0.23.2</a><a href="/fork/wezterm/ref/termiz-0.23.3/">termiz-0.23.3</a><a href="/fork/wezterm/ref/termwiz-0.23.0/">termwiz-0.23.0</a><a href="/fork/wezterm/ref/termwiz-0.23.1/">termwiz-0.23.1</a><a href="/fork/wezterm/ref/termwiz-0.23.2/">termwiz-0.23.2</a><a href="/fork/wezterm/ref/termwiz-0.23.3/">termwiz-0.23.3</a><a href="/fork/wezterm/ref/vtparse-0.7.0/">vtparse-0.7.0</a><a class="all" href="/fork/wezterm/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/wezterm/">wezterm</a> / <a href="/fork/wezterm/ref/termiz-0.23.1/tree/docs/">docs</a> / <span class="cur">help.md</span></nav>
<span class="view-stats"><span>798 B</span><span>13 lines</span></span><span class="actions"><a class="raw" href="/fork/wezterm/raw/1ee255d18b4beaf365ed605282536118a1db7141/docs/help.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>Getting Help</h2>
<p>This is a spare time project, so please bear with me.  There are a couple of channels for support:</p>
<ul>
<li>You can use the GitHub issue tracker to see if someone else has a similar issue, or to file a new one: <a href="https://github.com/wezterm/wezterm/issues">https://github.com/wezterm/wezterm/issues</a></li>
<li>Start or join a thread in our <a href="https://github.com/wezterm/wezterm/discussions">GitHub Discussions</a>; if you have general
questions or want to chat with other wezterm users, you're welcome here!</li>
<li>There is a <a href="https://app.element.io/#/room/#wezterm:matrix.org">Matrix room via Element.io</a>
for (potentially!) real time discussions.</li>
</ul>
<p>The GitHub Discussions and Element/Gitter rooms are better suited to questions
than it is to bug reports, but don't be afraid to use whichever you are most
comfortable using and we'll work it out.</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"><a-p>##</a-p> <a-tt>Getting Help</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">This is a spare time project, so please bear with me.  There are a couple of channels for support:</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text"><a-p>* </a-p>You can use the GitHub issue tracker to see if someone else has a similar issue, or to file a new one: &lt;https://github.com/wezterm/wezterm/issues&gt;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text"><a-p>* </a-p>Start or join a thread in our [GitHub Discussions](https://github.com/wezterm/wezterm/discussions); if you have general</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text"><a-p>  </a-p>questions or want to chat with other wezterm users, you&#39;re welcome here!</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>There is a [Matrix room via Element.io](https://app.element.io/#/room/#wezterm:matrix.org)</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>  </a-p>for (potentially!) real time discussions.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text">The GitHub Discussions and Element/Gitter rooms are better suited to questions</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text">than it is to bug reports, but don&#39;t be afraid to use whichever you are most</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text">comfortable using and we&#39;ll work it out.</span></span></pre></div></div>
</main>
</body>
</html>
