<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nix on ʕ•ᴥ•ʔ</title><link>https://staging.sua.dev/blog/nix/</link><description>Recent content in Nix on ʕ•ᴥ•ʔ</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Justin Hoang.</copyright><lastBuildDate>Thu, 23 Apr 2026 22:16:44 -0600</lastBuildDate><atom:link href="https://staging.sua.dev/blog/nix/index.xml" rel="self" type="application/rss+xml"/><item><title>Neovim</title><link>https://staging.sua.dev/neovim/</link><pubDate>Fri, 05 Sep 2025 00:00:00 -0600</pubDate><guid>https://staging.sua.dev/neovim/</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="#repositories"&gt;Repositories&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#plugins"&gt;Plugins&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#quirks"&gt;Quirks&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="repositories"&gt;Repositories&lt;/h2&gt;
&lt;p&gt;My &lt;code&gt;Neovim&lt;/code&gt; configuration is currently in two places:
&lt;a href="https://gitea.sua.dev/sua/nvim"&gt;nvim&lt;/a&gt; and
&lt;a href="https://gitea.sua.dev/sua/nixvim"&gt;nixvim&lt;/a&gt;. Both of these
configurations were heavily inspired by
&lt;a href="https://github.com/nvim-lua/kickstart.nvim"&gt;kickstart.nvim&lt;/a&gt;, a minimal starting
point for Neovim with sensible out-of-the-box configurations and detailed
documentation. The idea is that kickstart will give you the tools to build your
own configuration, rather than providing everything like a distribution would
(see &lt;a href="https://www.lazyvim.org/"&gt;LazyVim&lt;/a&gt; for example).&lt;/p&gt;
&lt;p&gt;I have mainly been using the nixvim configuration since last year. It is powered
by the &lt;a href="https://github.com/nix-community/nixvim"&gt;nixvim&lt;/a&gt; project, a Neovim
distribution powered by &lt;code&gt;nix&lt;/code&gt;. It allows you to define your Neovim
configurations using &lt;code&gt;nix&lt;/code&gt; modules rather than typical &lt;code&gt;lua&lt;/code&gt; files. This has the
added advantage of build reproducibility and seamless integration into the rest
of my &lt;code&gt;nix&lt;/code&gt; system configuration.&lt;/p&gt;</description></item><item><title>My Linux Journey</title><link>https://staging.sua.dev/my-linux-journey/</link><pubDate>Fri, 15 Aug 2025 00:00:00 -0600</pubDate><guid>https://staging.sua.dev/my-linux-journey/</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="#humble-beginnings"&gt;Humble Beginnings&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#linux-but-not-really"&gt;Linux but not really&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#macos-era"&gt;macOS Era&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#today"&gt;Today&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="humble-beginnings"&gt;Humble Beginnings&lt;/h2&gt;
&lt;p&gt;I don&amp;rsquo;t think I touched Linux before I got to college to study Computer Science.
The only experience I had with the computer is when I was playing video games
with my brother and cousins. My dad tried to teach &lt;code&gt;python&lt;/code&gt; to my brother and I
when we were in elementary school on a Raspberry Pi, but that never stuck. I
think that&amp;rsquo;s surprising because Bryan and I have always been pretty nerdy, but I
guess it wasn&amp;rsquo;t &lt;em&gt;that&lt;/em&gt; kind.&lt;/p&gt;</description></item></channel></rss>