24 Hours of AI Coding

ksqsf — Thu, 14 May 2026 00:00:00 +0000

Disclaimer: This post was translated into English by an AI model. It may contain mistakes or awkward wording. </blockquote>
Whether from news hype, friends in the AI industry, or online discussions, everyone keeps proclaiming the importance of the AI era. Yet I had never taken it very seriously. Claude Code has been out for more than a year, and I had occasionally used self-paid APIs to write small programs or analyze unfamiliar repositories, but I had never used an AI coding tool for a truly serious project. Yes, LLMs can write code, but did we not already know that? Only recently, after seeing friends use coding agents to build some quite interesting things, did I seriously try AI coding for the first time. The experience was perhaps too successful for me, even shocking. While the memory is still fresh, I want to record my first AI coding project.

Higher-order Data Types à la Carte

ksqsf — Sun, 12 Apr 2026 00:00:00 +0000

Disclaimer: This post was translated into English by an AI model. It may contain mistakes or awkward wording. </blockquote>
I recently needed to represent an AST for a small project, and I wanted the AST itself to be extensible: I could define fragments of a language and then combine them as needed. This sounds very suitable for DTALC. But one soon discovers that the classic DTALC formulation does not work. This post records the solution.

Living on WSL

ksqsf — Tue, 29 Apr 2025 00:00:00 +0000

Disclaimer: This post was translated into English by an AI model. It may contain mistakes or awkward wording. </blockquote>

I recently had to use Windows for work. After using WSL2 for a while, I found it quite usable. This post describes how I configure WSL and Emacs as my work environment.

Why Use WSL?</h1>

The first question is, of course: why not use a native Windows environment?

Indeed, today Windows can use tools such as Scoop to install command-line programs quickly, or one can use MSYS2 directly and build a command-line environment for Emacs to call.

I mainly use WSL for two reasons:

I am used to the Linux environment. Installing WSL feels like coming home: the same recipe, the same taste, and no learning cost.</li>
The projects I develop can only run on Linux, so in a sense it is a hard requirement. I say "in a sense" because Emacs can also use TRAMP for remote development.</li> </ol>
In short, I have spent very little time on native Windows, but I believe it can also be made usable with some effort.
TUI or GUI?</h1>
When I first installed WSL, I briefly tried WSLg and ran into some problems, so I only used the TUI. At first this was a compromise, but later I found the TUI completely sufficient. Of course, using the TUI means giving up some features:

The TUI can only use one font.</li>
TUI Emacs cannot display images.</li>
Before Emacs 30, there were no tty child frames.</li> </ol>
Aside from that, there do not seem to be many shortcomings.
Which Terminal?</h1>
As shown above, I use WezTerm. At first I started with Windows Terminal like everyone else, but I soon found that Emacs in Windows Terminal had screen tearing, while WezTerm did not.
My WezTerm configuration is simple, but one thing is worth mentioning: Emacs in a terminal cannot receive some key sequences, such as C-TAB</code>. We can bind this key in WezTerm to "send string to terminal program" as a workaround:
return { keys = { -- Press C-TAB to send C-x t o to the terminal program { key = 'Tab', mods = 'CTRL', action = act.SendString('\x18\x74\x6f') }, } } </code></pre> To find this string, call kbd</code> in IELM: ELISP> (kbd "C-x t o") "^Xto" ELISP> ?^X ELISP> ?^X 24 (#o30, #x18, ?\C-x) </code></pre> This tells you that Ctrl-x</code> corresponds to the character with ASCII code 0x18</code>, so you can construct the argument to SendString</code>. In Emacs, the ^X</code> here is colored differently from ordinary text, indicating that it is a complete special character. Do not try to copy ^X</code> directly from the web page; I split it into two characters, ^</code> and X</code>, so it can be displayed in a browser. </aside> WSL Configuration</h1> WSL has two layers of configuration: C:\Users\USERNAME\.wslconfig</code> on the Windows side, used to configure virtual-machine startup options.</li> /etc/wsl.conf</code> inside Linux, used to configure system startup and Linux services.</li> </ol> Below I omit full paths and only write filenames such as .wslconfig</code>. See the official documentation</a>. Which Distribution?</h2> Out of habit, I use Debian. But I encountered some WSL Debian problems, such as not being able to start .exe</code> files; the fix is mentioned below. These problems may not exist on Ubuntu, since Ubuntu is Microsoft's main target. If you need to choose, I suggest choosing a distribution you understand. If you do not want to tinker, Ubuntu is fine. Allocate More Hardware Resources</h2> In .wslconfig</code>: processors=12 memory=12GB </code></pre> Enable systemd</h2> Edit /etc/wsl.conf</code>: [boot] systemd = true </code></pre> Run .exe</code> Directly</h2> Debian's WSLInterop seems to have some compatibility problems with systemd and needs manual repair:

/home/ksqsf

24 Hours of AI Coding

Higher-order Data Types à la Carte

Living on WSL

Enable systemd</h2>
Edit `/etc/wsl.conf</code>:</p>`
`[boot] </span>systemd </span>= </span>true </span></code></pre> Run .exe</code> Directly</h2> Debian's WSLInterop seems to have some compatibility problems with systemd and needs manual repair:</p>`

Run `.exe</code> Directly</h2> Debian's WSLInterop seems to have some compatibility problems with systemd and needs manual repair:</p>`