<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cli on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cli/</link>
    <description>Recent content in Cli on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cli/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted CLI Fuzzy Finders: fzf vs skim vs peco Compared (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-16-self-hosted-cli-fuzzy-finders-fzf-skim-peco/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-16-self-hosted-cli-fuzzy-finders-fzf-skim-peco/</guid>
      <description>&lt;h2 id=&#34;why-fuzzy-finders-transform-terminal-workflows&#34;&gt;Why Fuzzy Finders Transform Terminal Workflows&lt;/h2&gt;&#xA;&lt;p&gt;The command line is fundamentally a text interface, and working with text efficiently requires the right filtering tools. Without a fuzzy finder, common tasks like searching command history, navigating directories, or selecting Git branches require memorizing exact names or typing out long paths character by character. A fuzzy finder lets you type approximate substrings — &amp;ldquo;brch&amp;rdquo; matches &amp;ldquo;feature/add-branch-name&amp;rdquo; — dramatically reducing keystrokes and cognitive load.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Development Environment Managers: mise vs asdf vs direnv (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-16-self-hosted-development-environment-managers-mise-asdf-direnv/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-16-self-hosted-development-environment-managers-mise-asdf-direnv/</guid>
      <description>&lt;h2 id=&#34;why-use-environment-managers&#34;&gt;Why Use Environment Managers?&lt;/h2&gt;&#xA;&lt;p&gt;Modern software development involves juggling multiple language runtimes, tool versions, and environment variables. A project might require Node.js 20, Python 3.11, and a specific PostgreSQL client version — while another project on the same machine needs Node.js 18, Python 3.12, and MySQL. Without environment management, developers rely on manual &lt;code&gt;export&lt;/code&gt; commands, fragile shell scripts, or Docker containers for every task.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Dotfile Management: chezmoi vs yadm vs homeshick Compared (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-16-self-hosted-dotfile-management-chezmoi-yadm-homeshick/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-16-self-hosted-dotfile-management-chezmoi-yadm-homeshick/</guid>
      <description>&lt;h2 id=&#34;why-manage-dotfiles&#34;&gt;Why Manage Dotfiles?&lt;/h2&gt;&#xA;&lt;p&gt;Every serious developer quickly accumulates a sprawling collection of configuration files across multiple machines — shell aliases, editor settings, git configs, tmux layouts, and dozens of environment-specific tweaks that define their workflow. When you work across multiple machines (work laptop, home desktop, remote servers, CI environments), keeping these files synchronized becomes a maintenance headache. Copying files manually with &lt;code&gt;scp&lt;/code&gt; or USB drives is error-prone, and forgetting to sync a critical alias or keybinding disrupts your workflow.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
