Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly close spawned kitty window #2471

Merged
merged 3 commits into from
Sep 27, 2024
Merged

Conversation

k4lizen
Copy link
Contributor

@k4lizen k4lizen commented Sep 26, 2024

The PID of the process run inside a spawned kitty window (always gdb in the current code) isn't properly detected. We can instead use the internal window id kitty returns to close it.

Fixes #2428

@k4lizen
Copy link
Contributor Author

k4lizen commented Sep 26, 2024

One thing though, when I Ctrl+C the process, while it does properly close the debugging window, some characters/bytes get printed:
image
@peace-maker Do you know where this could be coming from?
It seems to happen even if I do

subprocess.Popen(["kitten", "@", "close-window", "--match", f"id:{kittyid}"], stdout=open(os.devnull, "r+b"), stderr=open(os.devnull, "r+b"))

It is a bit annoying that that happens.

@k4lizen k4lizen changed the title properly close spawned kitty window Properly close spawned kitty window Sep 26, 2024
@peace-maker
Copy link
Member

Not sure, maybe @Arusekk knows

@peace-maker peace-maker merged commit 785ed9f into Gallopsled:dev Sep 27, 2024
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bug] kitty debugging window doesn't close when exiting process
2 participants