Skip to content

Fix install-from-content failing when root-directory doesn't exist#12

Merged
cuttlefisch merged 2 commits into
mainfrom
fix/install-from-content-root-directory
Apr 14, 2026
Merged

Fix install-from-content failing when root-directory doesn't exist#12
cuttlefisch merged 2 commits into
mainfrom
fix/install-from-content-root-directory

Conversation

@cuttlefisch
Copy link
Copy Markdown
Owner

@cuttlefisch cuttlefisch commented Apr 14, 2026

Summary

  • --install-from-content crashes with "No such file or directory" when the spec's root-directory points to a path that hasn't been created yet (e.g. a not-yet-cloned repo directory)
  • Add (make-directory default-directory t) before the install pipeline runs, so the CWD is guaranteed to exist
  • Add test: non-existent root-directory is created before pipeline stages execute

Test plan

  • make test — all 105 specs pass
  • In Emacs, eval updated code, then C-c C-c on a src block whose root-directory doesn't exist yet — should clone successfully

🤖 Generated with Claude Code

cuttlefisch and others added 2 commits April 14, 2026 23:30
When root-directory points to a not-yet-cloned path, call-process fails
with "No such file or directory" because default-directory must exist.
Add make-directory before the pipeline runs so the CWD is created first.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@cuttlefisch cuttlefisch merged commit a694b53 into main Apr 14, 2026
4 checks passed
@cuttlefisch cuttlefisch deleted the fix/install-from-content-root-directory branch April 14, 2026 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant