Ctrl+C signal kills the terminal
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by reproducing the issue while a working process runs in the terminal, then trace how Ctrl+C signals are handled by the terminal and its child process. Done means Ctrl+C stops the working process without terminating the terminal itself; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Description
everything is working fine, but if you try to kill a working process in the terminal, Hitting Ctrl+C will kill the terminal.
- Dominant language
- Shell
- Stars
- 217
- Forks
- 81
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 flathub/com.visualstudio.code
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
flathub/com.visualstudio.code#679 · 4 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
flathub/com.visualstudio.code#563 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flathub/com.visualstudio.code#388 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
flathub/com.visualstudio.code#715 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
flathub/com.visualstudio.code#710 ·
All issues in flathub/com.visualstudio.code
Similar issues
-
Feature Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
project-chip/certification-tool#1154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
beehive-lab/TornadoVM#1151 ·
Maintainers usually reply within 1 day
-
component/tests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/nodewright#735 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
obra/superpowers#2433 ·
Maintainers usually reply within 5 days