<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dotemacs/docs/design/music-config-without-emms.org, branch load-graph-classify-end</title>
<subtitle>My Emacs configuration
</subtitle>
<id>https://git.cjennings.net/dotemacs/atom?h=load-graph-classify-end</id>
<link rel='self' href='https://git.cjennings.net/dotemacs/atom?h=load-graph-classify-end'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/'/>
<updated>2026-05-15T07:09:23+00:00</updated>
<entry>
<title>docs(design): commit music-config-without-emms spec + readiness review</title>
<updated>2026-05-15T07:09:23+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-15T07:09:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/commit/?id=d9fa8f4db2b9e6d7f610094950b460cdee146e47'/>
<id>urn:sha1:d9fa8f4db2b9e6d7f610094950b460cdee146e47</id>
<content type='text'>
The spec lays out the EMMS-removal design: package-owned track and
playlist structs, a narrow backend protocol with mpv as the v1 backend,
state-change hooks replacing EMMS player hooks, an overlay-based
selected-track marker, a fake-backend test architecture, a quantified
performance budget, a 22-step parity walk, and the migration plan.

The review tracks implementation readiness: which migration-plan step
is safe to start, which decisions still block the rest, and the exact
spec edits required.

Two decisions landed this session and are now baked into the spec:

- Platform support: Linux and macOS get full features; Windows runs in
  degraded mode (play/stop/next/previous only) because Emacs cannot
  natively connect to mpv's Windows named-pipe IPC.  Anyone who wants
  full Windows parity can wire mpvc.exe shellout or a w32-* named-pipe
  client as a follow-up.

- File-extension scope: cj/music-file-extensions stays as-is.  webm and
  ape files in ~/music are intentionally skipped.

Socket path now references temporary-file-directory instead of a
hardcoded /tmp/ prefix so the spec stays consistent with the Windows
section.
</content>
</entry>
</feed>
