OhmNomNom / thyme

A fork of mintty, for the modern world
GNU General Public License v3.0
0 stars 0 forks source link

mintty fails to start up maximized on windows 7 #181

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. create a shortcut to mintty.exe
2. in the shortcut's properties window, set "Run" to "Maximized"
3. use this shortcut to start mintty

What is the expected output? What do you see instead?
Expected to have a maximized mintty window; instead, mintty starts up with 
regular size.

What version of the product are you using? On what operating system?
mintty 0.6.1, Windows 7 [Version 6.1.7600]

Please provide any additional information below.

Setting the compatibility mode in the shortcut's properties window to 
'Windows Vista' (any version) results in an interesting behavior: mintty 
does start up maximized, but a cmd.exe window is also created and stays 
open as long as mintty is open.  Also note that this funny behavior only 
happens if there's no other instance of mintty running.

Original issue reported on code.google.com by andr...@gmail.com on 15 Apr 2010 at 7:34

GoogleCodeExporter commented 9 years ago
This is fine on XP and Vista, no idea yet what's going wrong on 7. Thanks for 
the report.

I can explain the effect with the console though, but it's a long story. Mintty 
is a
GUI subsystem program, whereas most Cygwin programs, including bash, are console
subsystem programs. Normally, when invoking a console program from a GUI 
program,
Windows automatically creates a console window for that program. In cases like 
mintty
invoking bash, however, that's unnecessary and annoying, because bash's input 
and
output is connected to mintty. Therefore the Cygwin DLL contains a hack that 
creates
an invisible console window for bash to attach to.

Trouble is, Windows 7 has a bug that means that that hack doesn't work, which 
is why
the Cygwin DLL also contains a Windows 7-specific hack for creating an invisible
console. Therefore, if you enable Vista compatibility, the pre-7 version of the 
hack
that doesn't work on Windows 7 is used, hence you end up with the console window
being visible. Phew.

Original comment by andy.koppe on 15 Apr 2010 at 12:05

GoogleCodeExporter commented 9 years ago
Fixed in r849 on 0.6 branch.

Original comment by andy.koppe on 18 Apr 2010 at 9:44

GoogleCodeExporter commented 9 years ago

Original comment by andy.koppe on 20 Apr 2010 at 6:36

GoogleCodeExporter commented 9 years ago
Wow, that was a quick fix. Thanks!

Original comment by andr...@gmail.com on 21 Apr 2010 at 6:10