<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alexander Greim on Medium]]></title>
        <description><![CDATA[Stories by Alexander Greim on Medium]]></description>
        <link>https://medium.com/@iltempo?source=rss-5e5f1480500c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DgyUSddrARB0_-aq.jpeg</url>
            <title>Stories by Alexander Greim on Medium</title>
            <link>https://medium.com/@iltempo?source=rss-5e5f1480500c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:01:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iltempo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A journey into fish]]></title>
            <link>https://medium.com/@iltempo/a-journey-into-fish-9acf8c505796?source=rss-5e5f1480500c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9acf8c505796</guid>
            <dc:creator><![CDATA[Alexander Greim]]></dc:creator>
            <pubDate>Sun, 06 Oct 2013 22:52:52 GMT</pubDate>
            <atom:updated>2013-10-07T19:56:52.121Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*mcUAnfMhk9p4NbKv.png" /></figure><h4>Getting fish shell ready for Ruby coding</h4><p>Terminal shells are essential. They let you communicate with your operating system underneath the user interface. Also it’s “the tool” for developers that value flexibility and speed over user interfaces. But shells don’t have to be as clunky as bash or heavily extended like <a href="https://github.com/robbyrussell/oh-my-zsh">oh-my-zsh</a> on top of z-shell.</p><p><a href="http://fishshell.com/">Fish shell</a> is thin and user-friendly. Out of the box you get features that make your live easier and more fun. Even though it is not fully posix compatible it’s getting an increasing level of support by the community. And it’s refreshingly different.</p><h4>Installation</h4><p>Installing <a href="http://fishshell.com/">fish shell</a> is as easy as installing any other <a href="http://brew.sh/">Homebrew</a> package.</p><pre>$ brew install fish</pre><p>Starting fish shell from your running shell is as easy as well.</p><pre>$ fish</pre><h4>Customization</h4><p>Fish can be customized by editing it’s user-specific configuration file.</p><pre><strong>$ vim ~/.config/fish/config.fish</strong></pre><p>It’s a bright idea using that path. It makes versioning and portable profiles much easier than picking up config files placed directly in the home directory.</p><h4>Supporting Homebrew</h4><p>Integrating Homebrew means ensuring it’s binaries are found before the system ones in the search path. Fish uses the “set” syntax other than “export” in zsh or bash. Also $PATH is not a string of semicolon separated path entries. It’s an array where entries are delimited by white-spaces.</p><p>Knowing that, prepending the Homebrew binary path translates to</p><pre>set -x PATH /usr/local/bin $PATH</pre><p>Add this line to your config.fish file. It’s all you have to do.</p><h4>Getting rbenv running</h4><p><a href="http://rbenv.org/">Rbenv</a> is my favorite version manager for Ruby installations. It initializes by defining itself as a function via shell scripting in every shell session. So far it needs <a href="https://coderwall.com/p/6hja1w">quite some hacking</a> to get it working with fish. Fortunately @mislav recently added <a href="https://github.com/sstephenson/rbenv/issues/459">fish shell support</a>. As it didn’t went into a release yet, you need to install the HEAD revision of rbenv.</p><pre>$ brew unlink rbenv</pre><pre>$ brew install --HEAD rbenv</pre><p>After that add the following line to your config.fish file.</p><pre>set PATH $HOME/.rbenv/bin $PATH<br>. (rbenv init -|psub)</pre><p>Now your are able to switch Ruby versions as usual.</p><h4>Enabling the git prompt</h4><p>Fish shell has a baked-in git prompt support. It’s a handy feature to see the status of the repository you are working on. Version 2.0 released by date needs quite some <a href="https://github.com/fish-shell/fish-shell/blob/2.0.0/share/functions/__fish_git_prompt.fish">configuration settings</a> if you want to use the full status including stashes, upstreams and untracked files.</p><p>Good news it that the master version already contains one provides on single and well composed configuration default putting it all together. Again this version is not released yet. So you need to install the HEAD of the fish.</p><pre>$ brew unlink fish</pre><pre>$ brew install --HEAD fish</pre><p>Then enable the git prompt in your config.fish file.</p><pre>set __fish_git_prompt_show_informative_status ‘yes’</pre><p>Use some color for the branch if you like.</p><pre>set __fish_git_prompt_color_branch yellow</pre><p>Finally set the fish prompt including the git part.</p><pre>function fish_prompt<br> set last_status $status</pre><pre> set_color $fish_color_cwd<br> printf &#39;%s&#39; (prompt_pwd)<br> set_color normal</pre><pre> printf &#39;%s &#39; (__fish_git_prompt)</pre><pre> set_color normal<br>end</pre><h4>Conclusion</h4><p>It took me some time to put that all together. Especially finding out about what’s possible and still unreleased. My goal was to keep the configuration as simple as possible. You can find it in my <a href="https://github.com/iltempo/fish_config">repository</a>.</p><p>The most interesting part is still pending — using fish on a daily basis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9acf8c505796" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>