<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Unix on ZachFi</title>
    <link>https://zach.fi/tags/unix/</link>
    <description>Recent content in Unix on ZachFi</description>
    <image>
      <title>ZachFi</title>
      <url>https://zach.fi/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://zach.fi/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.148.2</generator>
    <language>en</language>
    <lastBuildDate>Sat, 22 Jun 2019 22:08:36 -0700</lastBuildDate>
    <atom:link href="https://zach.fi/tags/unix/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>New Terminal</title>
      <link>https://zach.fi/posts/new-terminal/</link>
      <pubDate>Sat, 22 Jun 2019 22:08:36 -0700</pubDate>
      <guid>https://zach.fi/posts/new-terminal/</guid>
      <description>&lt;p&gt;For years I had it in my head that &lt;code&gt;urxvt&lt;/code&gt; was the best terminal emulator one
could find. I ignored all those little areas of Unix management where I&amp;rsquo;d have
to set my &lt;code&gt;TERM&lt;/code&gt; variable to something like &lt;code&gt;xterm-256color&lt;/code&gt; before some remote
shell would recognize my terminal correctly, or where F keys had to be
configured before they would be passed to the running application. Those little
moments when I&amp;rsquo;d load a new color scheme for mutt, or vim, and I could tell
that I wasn&amp;rsquo;t quite getting the same experience that everyone else who
installed the plug-in had. Its been a good number of years this way, and I&amp;rsquo;d
just gotten used to it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
