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

Ctrl+C signal kills the terminal

Open
#425 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell
Domain
cli

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

  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 flathub/com.visualstudio.code

All issues in flathub/com.visualstudio.code

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.