today iain learned: How to replace nvim-treesitter and Mason with NVPM, and protect against supply chain attacks in tools that depend on git repositories.
Running Claude Code on a spare NUC sounds simple, but the devil is in the details.
I've written about this setup twice: Building my Terminal Setup covered the shell, fonts, and Ghostty, and A tmux Workspace Built Around the Claude Code Autopilot covered the project launcher, worktrees, and per-project tmux servers. Since then the right side of every workspace grew a three-pane column, the editor changed to neovim, and a shared notepad appeared. This is what a working session looks like now. What's on screen Every project session has the same shape. Claude Code runs in
I built much of my now-playing project with a Claude Code autopilot. I describe a feature, and it gets planned, implemented, reviewed, and shipped without me typing the intermediate steps. To do the implementation and the git work, the autopilot spawns subagents that write to the working tree. When two lines of work touch a single checked-out git tree, there can be collisions. This post goes over the terminal setup I use to prevent them — on the autopilot's side and on mine. The shared-tree
マルチシェル・マルチOS対応のdotfilesエコシステムDorothyの紹介です。
today iain learned: Some neat features that come with an upgrade to Neovim version 0.12, such as the built-in Undotree plugin and native Treesitter-based incremental selection.
today iain learned: How to remap the CapsLock key with a tap-hold keybind in Linux
today iain learned: How to use terminal commands for displaying a custom Neovim dashboard logo on startup
today iain learned: How to use the wev CLI tool to help add keybinds or shortcuts for special keys in Hyprland
today iain learned: How to fix a macOS WezTerm configuration to work in Hyprland
today iain learned: How to set up and use sessions in the kitty terminal emulator
How to use WezTerm's hyperlink rules to open files in VS Code from Zellij
A quick guide on how to set up mackup for dotfiles.
Obsidian: dooooooooope open source writing app tailored to programmers' thought processes.
VSCode
I recently decided to start using my own home server to store my dotfiles. The main reasons are simplicity, privacy, and security. I previously stored them in a repository on my GitHub account and installed them with Ansible, but I have increasingly found it cumbersome when trying to keep them updated and in sync. On GitHub, the changes (and mistakes!) I make to my dotfiles are publicly viewable; sometimes I'll make changes several times a day, sometimes scrapping a change entirely when I later realize it was not such a good idea or breaks something in my activity flow. I also would love the convenience of keeping SSH keys and GPG keychains in sync and updated, and storing them on a public server is obviously not an option, nor even in a private repository hosted on GitHub or GitLab.
Mac を新しく購入したり OS をクリーンインストールしたときのためにセットアップ手順を残しておきます。 ...
いろいろと PC を乗り換えたり、不具合対応のために PC を初期化したりしたとき、イチから環境を作り直すのはめんどくさいものです。 dotfiles を GitHub で管理すれば環境構築のコストが一気に少なくなります。 また、これにより環境を作り直すこと自体の心理的ハードルが下がるメリットもあります。 ...
Silicon Valley Season 2 ruined it for me. Richard had worked so hard on Pied Piper, but Gavin is alm
I made a Dracula colour theme for tmux and I love it! Here's a bit about how to customize tmux
I made a Dracula colour theme for tmux and I love it! Here's a bit about how to customize tmux
History My dotfiles repo started out as a fork from some dude . The main reason for making the repo