Windows start command opens CMD but not a new instance of Hyper
Open
Nobody has claimed this yet.
🐛 Type: Bug
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
- OS version and name: Windows 10
- Hyper.app version: 2.1.1 (canary)
Issue
Simply I type start and hit ENTER. I get a new window of CMD, but I expect to get a new window of Hyper. May be it is not a big deal, but my scripts in npm open several windows, one for test the other one for webpack . But they are in native cmd window, I want them be in Hyper.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the start command behavior on Windows 10 with Hyper 2.1.1, including npm scripts that launch test and webpack windows. Trace how Hyper handles Windows command launches; done means those commands open new Hyper windows instead of native CMD windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100