just argument-comment-lint fails when the repo path contains spaces
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- shell
- Domain
- build-system
Research direction
Start with the argument-comment-lint recipe and its justfile_directory() command substitution, using AGENTS.md and just --dry-run argument-comment-lint to reproduce the unquoted path expansion. Verify the helper path is handled as one path when the checkout contains spaces, then rerun the recipe to confirm the target-list helper executes successfully.
Written by the indexing model from the issue text.
Description
What happened?
AGENTS.md recommends running just argument-comment-lint locally. In a checkout whose path contains a space, the recipe fails before it can run the target-list helper because the justfile_directory() expansion is unquoted inside command substitution.
In this checkout, running just argument-comment-lint expands to:
bazel build --config=argument-comment-lint -- $(/Users/gimdong-yong/Documents/Quick Question/openai-codex-upstream/tools/argument-comment-lint/list-bazel-targets.sh)
The shell splits that path at Quick Question, producing:
argument-comment-lint: /Users/gimdong-yong/Documents/Quick: No such file or directory
just --dry-run argument-comment-lint shows the same unquoted path expansion.
Expected behavior
The argument-comment-lint recipe should quote the helper path so the command works from checkouts whose absolute path contains spaces.
Additional context
I searched open issues and PRs for terms including argument-comment-lint, path spaces, and justfile_directory, and did not find an existing open item that appears to cover this shell quoting issue.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·