[GH-ISSUE #57] Exiting SSH connection should close its window/tab #1004

New issue

Closed

opened 2026-02-28 12:00:45 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 12:00:45 +03:00

Owner

Originally created by @majkinetor on GitHub (Jan 13, 2021).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/57

Originally assigned to: @VShawn on GitHub.

When I exit the shell, I am left with the dummy black window that I need to explicitly close as no other action could be done on it. This is not a big problem per se, but certainly UX fail.

If it is possible to detect this, you should close the hosting window automatically.

Originally created by @majkinetor on GitHub (Jan 13, 2021). Original GitHub issue: https://github.com/1Remote/1Remote/issues/57 Originally assigned to: @VShawn on GitHub. When I exit the shell, I am left with the dummy black window that I need to explicitly close as no other action could be done on it. This is not a big problem per se, but certainly UX fail. If it is possible to detect this, you should close the hosting window automatically.

kerem

2026-02-28 12:00:45 +03:00

closed this issue
added the
meta-enhancement

area-ct-ssh
labels

kerem commented

2026-02-28 12:00:45 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 13, 2021):

I am left with the dummy black window

sorry? I dont get how you left dummy black window? Did you mean left with 'exit' command instead of click 'X' button on windows top right?

If it is possible to detect this

And actually yes, we can do that. Since we cannot get Shell close event without pipe\FIFO\signal(I am not intend to implemt any communication between processes). We can still create a background watcher to check if KiTTY process is alive periodically. Onec KiTTY was killed we can close the tab.

@VShawn commented on GitHub (Jan 13, 2021): > I am left with the dummy black window sorry? I dont get how you left dummy black window? Did you mean left with 'exit' command instead of click 'X' button on windows top right? > If it is possible to detect this And actually yes, we can do that. Since we cannot get Shell close event without pipe\FIFO\signal(I am not intend to implemt any communication between processes). We can still create a background watcher to check if KiTTY process is alive periodically. Onec KiTTY was killed we can close the tab.

kerem commented

2026-02-28 12:00:45 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 13, 2021):

found something useful

@VShawn commented on GitHub (Jan 13, 2021): found something useful ![image](https://user-images.githubusercontent.com/10143738/104448158-c2d4fd00-55d7-11eb-8b5f-51a63b5583b5.png)

kerem commented

2026-02-28 12:00:45 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 13, 2021):

works

PRemoteM 0.5.8.2101132000.zip

@VShawn commented on GitHub (Jan 13, 2021): works ![1](https://user-images.githubusercontent.com/10143738/104449536-b5b90d80-55d9-11eb-953f-b70ee1d2389e.gif) [PRemoteM 0.5.8.2101132000.zip](https://github.com/VShawn/PRemoteM/files/5808454/PRemoteM.0.5.8.2101132000.zip)

kerem referenced this issue

2026-02-28 12:07:11 +03:00

[PR #1004] [MERGED] Analysis of issue #864: Clipboard clearing is an environment issue, not a code issue #1891

kerem referenced this issue

2026-03-01 17:23:31 +03:00

[PR #1004] [MERGED] Analysis of issue #864: Clipboard clearing is an environment issue, not a code issue #2853

kerem referenced this issue

2026-03-13 13:01:45 +03:00

[PR #1004] [MERGED] Analysis of issue #864: Clipboard clearing is an environment issue, not a code issue #3852