Shell, editor and terminal configuration, and the tools that go with them https://git.soarez.net/sz/dot.git/atom?h=master 2026-10-29T21:40:43+00:00 2026-10-29T21:40:43+00:00 Igor Soarez igor@soarez.org 2026-10-29T21:40:43+00:00 urn:sha1:b3448031088447d76d80ac6b2bfa08320973a2d9 pi reads user-level MCP servers from one file, and a private layer linked that file to the same copy on every host -- so every host got a server only one machine could run. Build it the way models.json is built, from fragments another layer or one machine drops in mcp.d; this repo ships none, and with none the file is left absent. pi-models.py becomes pi-merge.py, which takes the key to merge and an optional base file, and serves both. 2026-09-25T09:20:13+00:00 Igor Soarez igor@soarez.org 2026-09-25T09:20:13+00:00 urn:sha1:ed21d1270007a8f9cbaa2ca7da0fee1eefeb405f 57e49dd made link/pi.sh unparseable on macOS. bash 3.2 does not skip heredoc content when it scans for the end of a command substitution, so the three apostrophes in a comment inside the new heredoc read as an unterminated quote and the script stopped parsing at end of file. ./link.sh on a Mac aborted partway: settings still generated, models.json stayed the symlink the commit meant to replace, and everything after that point never ran. Linux was fine, and so was every check I ran -- `bash` on a Mac with Homebrew is 5.x, which parses it happily. Reported from the machine it broke. Rewording the comment would fix it and leave the trap armed for the next edit, so the two python programs move into link/pi-settings.py and link/pi-models.py instead, called by path. The text is unchanged; there is no longer a heredoc inside $( ) to trip over, and both files now compile-check on their own. Verified under /bin/bash 3.2: first apply replaces both symlinks, a package removed by hand still survives a relink, fragments merge for settings and for models, and repeat runs report unchanged.