<?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>Scheme on Xerxes II's Blog</title><link>/en/tags/scheme/</link><description>Recent content in Scheme on Xerxes II's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 03 May 2026 00:00:00 +1000</lastBuildDate><atom:link href="/en/tags/scheme/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing a Wakatime Plugin for Helix in Scheme</title><link>/en/posts/helix-wakatime-plugin-in-scheme/</link><pubDate>Sun, 03 May 2026 00:00:00 +1000</pubDate><guid>/en/posts/helix-wakatime-plugin-in-scheme/</guid><description>&lt;p&gt;My daily editor is &lt;a href="https://helix-editor.com/"&gt;Helix&lt;/a&gt;. I never got deep into Vim, so switching to Helix cost me nothing in terms of adjustment — it actually felt more natural. Helix works great out of the box, and the &amp;ldquo;select-then-act&amp;rdquo; editing model clicks with me more intuitively than Vim&amp;rsquo;s &amp;ldquo;verb-then-noun&amp;rdquo; approach.&lt;/p&gt;
&lt;p&gt;Helix mainline doesn&amp;rsquo;t have a plugin system, which has long been one of the biggest pain points in the community. However, &lt;a href="https://github.com/mattwparas"&gt;mattwparas&lt;/a&gt; maintains a fork (the &lt;a href="https://github.com/mattwparas/helix/tree/steel-event-system"&gt;&lt;code&gt;steel-event-system&lt;/code&gt; branch&lt;/a&gt;) that integrates &lt;a href="https://github.com/mattwparas/steel"&gt;Steel&lt;/a&gt; — an embedded Scheme implementation — as a plugin runtime. Scheme is a dialect of Lisp, and Steel is a dialect of Scheme, so you can probably guess what writing plugins looks like: lots of parentheses.&lt;/p&gt;</description></item></channel></rss>