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

Command windows remain open on Windows 10 Build 9926 #439

Closed
GoogleCodeExporter opened this issue Jun 4, 2015 · 4 comments
Closed

Command windows remain open on Windows 10 Build 9926 #439

GoogleCodeExporter opened this issue Jun 4, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Jun 4, 2015

Windows 10 Pro Technical Preview build 9926

cygwin               1.7.33-1
mintty               1.2-beta1-1

When launching mintty, 2 additional console windows appear visible as shown in 
screenshot attached.

Appears to be another instance of this old issue: 
https://code.google.com/p/mintty/issues/detail?id=39

Running in compatibility mode for Windows 8 fixes the issue, so I'm guessing 
the check for which OS the "Windows 7 hack" needs to be applied to simply needs 
to be updated.

Original issue reported on code.google.com by cl...@clintarmstrong.net on 24 Jan 2015 at 11:03

Attachments:

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Jun 4, 2015

I'm not sure it's related to mintty, but  perhaps to windows conhost.exe 
instead?

If you run screen, a new console windows also appear when you create a new 
screen window (^a c).

Here setting the compatibility mode for windows vista/vista sp1/vista sp2/win7 
or 8 doesn't change anything. 

Windows 10 Pro Tech Preview Build 9926
cygwin  1.7.33-1
mintty  1.2-beta1-1
screen  4.2.1-2

Original comment by yunga.pa...@gmail.com on 17 Feb 2015 at 3:03

@mintty
Copy link
Owner

@mintty mintty commented Jun 30, 2015

Hopefully fixed for next release by adding respective resource magic values.

@mintty
Copy link
Owner

@mintty mintty commented Aug 7, 2015

Any such incidents with recent versions? Otherwise I'll close the issue soon.

@mintty
Copy link
Owner

@mintty mintty commented Sep 4, 2015

I had previously overlooked the detail that the issue occurs also on ^C a in 'screen' - which is clear evidence that at least this instance of the issue is not related to mintty.

@mintty mintty closed this Sep 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants