Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Ctrl+G fails to open a quoted VS Code path containing spaces

Open Beginner friendly
#179 1 comment 0 reactions 0 assignees View on GitHub

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
Active
Tech stack
shell, typescript

Research direction

Look at the external editor handling code, likely in a file like src/editor.ts or src/cli.ts. The issue is with parsing the VISUAL environment variable when it contains quoted paths with spaces. The fix should ensure the shell command is split correctly. Test by setting VISUAL as described and running the Ctrl+G command in the Step prompt.

Written by the indexing model from the issue text.

Description

bug
What happened?

On macOS, Ctrl+G briefly shows the external-editor launch message, then returns to Step without opening VS Code. I reproduced this with Step 0.1.0 and extensions disabled (step -ne --no-session). No error is shown. This makes Ctrl+G unusable when VISUAL points to a quoted app-bundle path with spaces. I have a fix and regression test ready in my fork and would like to submit a PR when external PRs are accepted.

Steps to reproduce
  1. Confirm that /Applications/Visual Studio Code.app/Contents/Resources/app/bin/code exists.
  2. Run VISUAL='"/Applications/Visual Studio Code.app/Contents/Resources/app/bin/code" --wait' step -ne --no-session.
  3. Press Ctrl+G in the Step prompt.
Expected behavior

VS Code opens the temporary prompt.md file and Step waits until I close the editor.

Version

0.1.0

Dominant language
TypeScript
Stars
54
Forks
20
Avg merge
4h 1m
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stepfun-ai/Step-Code

All issues in stepfun-ai/Step-Code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.