ctrl+C does not kill trapped process(git bash config was used)
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
trap 'kill %1; kill %2' SIGINT
cd /server1;
node server1.js &
cd /server2;
node server2.js &
cd /server3;
node server3.js;
note that this is working correctly on conEmu
OS: Windows 10;
gitbash: 2.26.2;
hyper: 3.0.1
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
Reproduce the provided trap configuration from this-is-my-config.txt in Hyper 3.0.1 on Windows 10 with Git Bash 2.26.2, then compare Ctrl+C behavior with ConEmu. Done means Ctrl+C terminates the trapped foreground and background Node.js processes as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100