<?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>Terminal on D. Sébastien Taggart</title>
    <link>https://www.sebastientaggart.com/tags/terminal/</link>
    <description>Recent content in Terminal on D. Sébastien Taggart</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 23:02:59 -0400</lastBuildDate>
    <atom:link href="https://www.sebastientaggart.com/tags/terminal/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Per-repo SSH keys for Git with core.sshCommand</title>
      <link>https://www.sebastientaggart.com/writing/git-per-repo-ssh-key-with-core-ssh-command/</link>
      <pubDate>Wed, 02 Aug 2023 20:18:43 -0400</pubDate>
      <guid>https://www.sebastientaggart.com/writing/git-per-repo-ssh-key-with-core-ssh-command/</guid>
      <description>Store the right SSH identity in each clone’s .git/config so you stop prefixing every Git command or maintaining a giant ~/.ssh/config.</description>
      <content:encoded><![CDATA[<p>If you keep more than one GitHub (or GitLab, or whatever) identity, you usually end up with more than one private key. The usual fixes are <code>Host</code> aliases in <code>~/.ssh/config</code>, or typing <code>GIT_SSH_COMMAND='ssh -i ~/.ssh/some_key -o IdentitiesOnly=yes' git …</code> before every command. Both work. Neither is what I want when I just opened a random repo in a deep path and want my fingers to do the right thing.</p>
<p><strong>Reminder:</strong> you can pin the SSH command on a single clone:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">git config core.sshCommand <span class="s2">&#34;ssh -i ~/.ssh/your_private_key -F /dev/null&#34;</span>
</span></span></code></pre></div><p>That lands in <code>.git/config</code> for that repository only. Every <code>git fetch</code>, <code>git pull</code>, <code>git push</code> from that directory uses that key. No wrapper script, no repeated env var.</p>
<p><code>-F /dev/null</code> tells <code>ssh</code> not to read your normal config file for that invocation. That matters when your global config would otherwise offer several keys and confuse <code>github.com</code> about which one you meant. Pair with <code>-o IdentitiesOnly=yes</code> if your agent still tries to hand out the wrong identity first.</p>
<p>This does not travel with the remote (<code>.git/config</code> stays local), so a fresh clone needs the line again, or you automate it once in a bootstrap script. For “this laptop folder always means my work GitHub,” that tradeoff is usually fine.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Improving Terminal in OSX</title>
      <link>https://www.sebastientaggart.com/writing/improving-terminal-in-osx/</link>
      <pubDate>Fri, 07 Aug 2020 20:58:11 -0500</pubDate>
      <guid>https://www.sebastientaggart.com/writing/improving-terminal-in-osx/</guid>
      <description>&lt;p&gt;Out of the box, using the Terminal in macOS leaves much to be desired. The built-in application can feel inflexible and quite plain, while the default shell, Bash, lacks several handy tools that become indispensable once you’ve experienced them.&lt;/p&gt;
&lt;p&gt;Let’s explore how to transform your terminal experience into something that’s not just functional but enjoyable.&lt;/p&gt;
&lt;h2 id=&#34;homebrew-the-missing-package-manager&#34;&gt;Homebrew: The Missing Package Manager&lt;/h2&gt;
&lt;p&gt;Homebrew is the essential package manager for macOS. It fills a significant gap for developers, allowing you to easily install and manage software packages.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>Out of the box, using the Terminal in macOS leaves much to be desired. The built-in application can feel inflexible and quite plain, while the default shell, Bash, lacks several handy tools that become indispensable once you’ve experienced them.</p>
<p>Let’s explore how to transform your terminal experience into something that’s not just functional but enjoyable.</p>
<h2 id="homebrew-the-missing-package-manager">Homebrew: The Missing Package Manager</h2>
<p>Homebrew is the essential package manager for macOS. It fills a significant gap for developers, allowing you to easily install and manage software packages.</p>
<p>To get started, run this command in your terminal:</p>
<pre tabindex="0"><code>/bin/bash -c &#34;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)&#34;
</code></pre><p><em>Note:</em> This command should automatically install Xcode if it&rsquo;s not already present. If it doesn’t, you can manually install it with:</p>
<pre tabindex="0"><code>sudo xcode-select --install
</code></pre><h3 id="handy-brew-commands">Handy Brew Commands</h3>
<p>Once you have Homebrew installed, here are some commands that will serve you well:</p>
<ul>
<li><code>brew doctor</code> - A self-check tool; run it if you encounter issues.</li>
<li><code>brew search SOMETHING</code> - Searches for a package named <code>SOMETHING</code>. However, checking <a href="http://searchbrew.com/">online</a> might yield quicker results.</li>
<li><code>brew list --versions</code> - Lists all installed packages and their versions.</li>
<li><code>brew install git</code> / <code>brew uninstall git</code> / <code>brew upgrade git</code> - Manage Git easily.</li>
<li><code>brew update</code> / <code>brew upgrade</code> - Updates apps or all packages, respectively.</li>
<li><code>brew outdated</code> - Displays available upgrades.</li>
</ul>
<h3 id="installing-non-open-source-software">Installing Non-Open Source Software</h3>
<p>Forget about dragging icons around to install applications. With Homebrew, you can use <code>brew cask</code> to install macOS apps seamlessly:</p>
<pre tabindex="0"><code>brew install --cask firefox
</code></pre><p>You can browse a comprehensive <a href="https://formulae.brew.sh/cask/">list of available casks</a>. Notable applications available this way include:</p>
<ul>
<li><a href="https://formulae.brew.sh/cask/atom">Atom</a></li>
<li><a href="https://formulae.brew.sh/cask/firefox">Firefox</a></li>
<li><a href="https://formulae.brew.sh/cask/google-chrome">Chrome</a></li>
<li><a href="https://formulae.brew.sh/cask/iterm2">iTerm2</a></li>
</ul>
<h2 id="iterm2-a-more-powerful-terminal">iTerm2: A More Powerful Terminal</h2>
<p>For a more robust and customizable terminal experience, consider using iTerm2. It’s lightweight, efficient, and offers features that can significantly enhance your workflow. You can install it with:</p>
<pre tabindex="0"><code>brew install --cask iterm2
</code></pre><h2 id="the-z-shell-a-step-up-from-bash">The Z Shell: A Step Up from Bash</h2>
<p>The Z shell (or Zsh) is built on top of Bash and brings additional features to the table. To make the most of it, you’ll want to use a plugin framework. One of the most popular is <code>Oh My Zsh</code>.</p>
<p>To get started, run:</p>
<pre tabindex="0"><code>brew install zsh
brew install wget
sh -c &#34;$(wget -O- https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)&#34;
</code></pre><p>To ensure you&rsquo;re using Zsh, check your shell with:</p>
<pre tabindex="0"><code>echo $0
</code></pre><p>If it doesn’t return <code>-zsh</code>, you can set Zsh as your default shell with:</p>
<pre tabindex="0"><code>chsh -s $(which zsh)
</code></pre><p>All your Zsh configuration lives in <code>~/.zshrc</code>. After you make changes, don’t forget to load them with:</p>
<pre tabindex="0"><code>source ~/.zshrc
</code></pre><h3 id="auto-suggestions-a-game-changer">Auto Suggestions: A Game Changer</h3>
<p>One of the standout features for frequent terminal users is the Zsh Auto Suggestions plugin. It provides context-aware auto-completion based on your command history, making your workflow far more efficient.</p>
<p>To install this plugin, run:</p>
<pre tabindex="0"><code>git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions
</code></pre><p>Then add <code>zsh-autosuggestions</code> to your plugins list in <code>~/.zshrc</code>.</p>
<h3 id="spaceship-theme-enhance-your-prompt">Spaceship Theme: Enhance Your Prompt</h3>
<p>For those looking to refine the aesthetic and functionality of their terminal, the Spaceship Prompt is an excellent addition. It offers a visually appealing layout that displays your current git branch, command status, and more.</p>
<p>To install Spaceship, run:</p>
<pre tabindex="0"><code>git clone https://github.com/denysdovhan/spaceship-prompt.git &#34;$ZSH_CUSTOM/themes/spaceship-prompt&#34;
ln -s &#34;$ZSH_CUSTOM/themes/spaceship-prompt/spaceship.zsh-theme&#34; &#34;$ZSH_CUSTOM/themes/spaceship.zsh-theme&#34;
</code></pre><p>Finally, set the theme in your <code>.zshrc</code>:</p>
<pre tabindex="0"><code>ZSH_THEME=&#34;spaceship&#34;
</code></pre><h3 id="recommended-zshrc-configuration">Recommended .zshrc Configuration</h3>
<p>Here’s a suggested configuration to help you get started with the Spaceship theme and other useful settings:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nv">ZSH_THEME</span><span class="o">=</span><span class="s2">&#34;spaceship&#34;</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="nv">SPACESHIP_USER_SHOW</span><span class="o">=</span><span class="s2">&#34;false&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nv">SPACESHIP_HOST_SHOW</span><span class="o">=</span><span class="s2">&#34;false&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nv">SPACESHIP_PHP_SHOW</span><span class="o">=</span><span class="s2">&#34;false&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nv">SPACESHIP_PROMPT_ADD_NEWLINE</span><span class="o">=</span><span class="s2">&#34;true&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nv">SPACESHIP_DIR_TRUNC_PREFIX</span><span class="o">=</span><span class="s2">&#34;.../&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nv">SPACESHIP_DIR_TRUNC_REPO</span><span class="o">=</span><span class="s2">&#34;false&#34;</span>
</span></span></code></pre></div><p>For plugins, consider:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nv">plugins</span><span class="o">=(</span>git colorize pip python brew zsh-autosuggestions<span class="o">)</span>
</span></span></code></pre></div><p>You might also want to add some convenient aliases to your <code>.zshrc</code>:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">alias</span> <span class="nv">ls</span><span class="o">=</span><span class="s1">&#39;ls --color=auto -lhapG&#39;</span> <span class="c1"># Prettier output of ls, includes directory slashes</span>
</span></span><span class="line"><span class="cl"><span class="nb">alias</span> <span class="nv">gs</span><span class="o">=</span><span class="s1">&#39;git status&#39;</span>
</span></span><span class="line"><span class="cl"><span class="nb">alias</span> <span class="nv">gaa</span><span class="o">=</span><span class="s1">&#39;git add --all&#39;</span>
</span></span><span class="line"><span class="cl"><span class="nb">alias</span> <span class="nv">gcm</span><span class="o">=</span><span class="s1">&#39;git commit -m &#39;</span>
</span></span></code></pre></div><p>From here, feel free to add any other aliases that suit your workflow!</p>
<h3 id="conclusion">Conclusion</h3>
<p>By adopting these tools and configurations, you’ll not only enhance your terminal experience but also streamline your workflow. Embrace the power of Homebrew, iTerm2, and Zsh, and watch your productivity soar. After all, a well-optimized environment is a crucial step towards effective development and efficient problem-solving. Happy coding!</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
