<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Linux on SIGKILL</title><link>https://sigkill.no/tags/linux/</link><description>An independent corner of the internet. Notes on Unix, networks, and things figured out along the way.</description><language>en-US</language><copyright>cr4sh0v3rrid3 (CC BY 4.0)</copyright><managingEditor>cr4sh@sigkill.no (cr4sh0v3rrid3)</managingEditor><atom:link href="https://sigkill.no/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Alacritty terminfo</title><link>https://sigkill.no/blog/alacritty_terminfo/</link><guid>https://sigkill.no/blog/alacritty_terminfo/</guid><pubDate>Fri, 05 Apr 2024 00:00:00 +0000</pubDate><author>cr4sh@sigkill.no (cr4sh0v3rrid3)</author><description>&lt;p&gt;To get alacritty to work with remote hosts:&lt;/p&gt;&#10;&lt;div class="code-block"&gt;&#10; &lt;div class="code-label" aria-hidden="true"&gt;TEXT&lt;/div&gt;&#10; &#10; &lt;pre tabindex="0"&gt;&lt;code&gt;$ infocmp &amp;gt; al.txt&#10;$ scp al.txt &amp;lt;user&amp;gt;@&amp;lt;host&amp;gt;:~/&#10;&#10;# On the remote host:&#10;$ tic -x al.txt&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;&#10;&lt;h3 id="what-does-tic--x-do"&gt;What does &amp;ldquo;tic -x&amp;rdquo; do?&lt;/h3&gt;&#10;&lt;div class="code-block"&gt;&#10; &lt;div class="code-label" aria-hidden="true"&gt;TEXT&lt;/div&gt;&#10; &#10; &lt;pre tabindex="0"&gt;&lt;code&gt;$ man tic&#10;...&#10; -x Treat unknown capabilities as user-defined (see user_caps(5)). That is, if you supply a capability name which tic does not recognize, it will infer its type&#10; (Boolean, number or string) from the syntax and make an extended table entry for that. User-defined capability strings whose name begins with “k” are treated as&#10; function keys.&#10;...&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="one-liner"&gt;One liner&lt;/h2&gt;&#10;&lt;p&gt;Note: this is stolen from the &lt;a href="https://wiki.archlinux.org/title/Alacritty#Terminal_functionality_unavailable_in_remote_shells"&gt;archwiki&lt;/a&gt;&lt;/p&gt;</description><content:encoded>&lt;p&gt;To get alacritty to work with remote hosts:&lt;/p&gt;&#10;&lt;div class="code-block"&gt;&#10; &lt;div class="code-label" aria-hidden="true"&gt;TEXT&lt;/div&gt;&#10; &#10; &lt;pre tabindex="0"&gt;&lt;code&gt;$ infocmp &amp;gt; al.txt&#10;$ scp al.txt &amp;lt;user&amp;gt;@&amp;lt;host&amp;gt;:~/&#10;&#10;# On the remote host:&#10;$ tic -x al.txt&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;&#10;&lt;h3 id="what-does-tic--x-do"&gt;What does &amp;ldquo;tic -x&amp;rdquo; do?&lt;/h3&gt;&#10;&lt;div class="code-block"&gt;&#10; &lt;div class="code-label" aria-hidden="true"&gt;TEXT&lt;/div&gt;&#10; &#10; &lt;pre tabindex="0"&gt;&lt;code&gt;$ man tic&#10;...&#10; -x Treat unknown capabilities as user-defined (see user_caps(5)). That is, if you supply a capability name which tic does not recognize, it will infer its type&#10; (Boolean, number or string) from the syntax and make an extended table entry for that. User-defined capability strings whose name begins with “k” are treated as&#10; function keys.&#10;...&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="one-liner"&gt;One liner&lt;/h2&gt;&#10;&lt;p&gt;Note: this is stolen from the &lt;a href="https://wiki.archlinux.org/title/Alacritty#Terminal_functionality_unavailable_in_remote_shells"&gt;archwiki&lt;/a&gt;&lt;/p&gt;&#10;&lt;div class="code-block"&gt;&#10; &lt;div class="code-label" aria-hidden="true"&gt;TEXT&lt;/div&gt;&#10; &#10; &lt;pre tabindex="0"&gt;&lt;code&gt;$ infocmp | ssh &amp;#34;$user@$host&amp;#34; &amp;#39;tic -x /dev/stdin&amp;#39;&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;&#10;</content:encoded></item></channel></rss>