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

Option 6 (quitting) results in a different terminal window closing #248

Closed
legoadk opened this issue Oct 25, 2015 · 3 comments
Closed

Option 6 (quitting) results in a different terminal window closing #248

legoadk opened this issue Oct 25, 2015 · 3 comments

Comments

@legoadk
Copy link

legoadk commented Oct 25, 2015

When more than one Terminal window is open, and CAT is quit from within (by entering option 6 on the main screen), a different terminal window is actually closed. This may result in lost work if other terminals have active programs running within them.

OS X 10.10.5

sysfloat added a commit that referenced this issue Dec 7, 2015
@sysfloat sysfloat closed this as completed Dec 7, 2015
@legoadk
Copy link
Author

legoadk commented Dec 7, 2015

The patch for this bug, if it works like I think it does, actually issues Command Q to the entire terminal application. This will quit every open terminal, as well – actually more destructive than the original issue that closed a different random window. A suggestion would be to instead issue Command-W, which only closes the currently focused tab within the current window. The issue with this is that it still leaves the Terminal application open — good if you have other terminals open, bad if CAT was the only open program. Tough bug to work around!

@sysfloat
Copy link
Collaborator

sysfloat commented Dec 7, 2015

@legoadk Command-W will close the window but CAT will stay in the dock as "Not Responding".
CAT opens a new instance of Terminal running as root and you shouldn't use it to run anything else. The new solution would then quit that instance. Any instance of the normal Terminal not used by CAT remain unaffected.

@legoadk
Copy link
Author

legoadk commented Dec 8, 2015

Ah, that totally makes sense. In that case, ignore my previous comment :)

greenygh0st added a commit to greenygh0st/Continuity-Activation-Tool that referenced this issue Feb 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants