Ability to specify mintty windows should be maximized other than command-line option

[GoogleCodeExporter]

I know this may seem like a strange request, but I'd like to be able to specify 
that mintty windows should be maximized using something other than the 
command-line args that were added in 0.7.1.  This is because I use a Windows 
7-like launcher on XP (ViGlance) that doesn't allow you to specify the 
command-line for pinned applications.  I'm also asking the ViGlance author to 
add that feature, but given that many of mintty's options are specified in 
.minttyrc (and the config UI) already including window geometry, I thought that 
perhaps it wouldn't be too difficult to specify an alternative window geometry 
of maximized or full screen through that config file.

Thanks for mintty!  It's absolutely fantastic!!!

Original issue reported on code.google.com by scottwe...@gmail.com on 25 Jun 2010 at 9:42

[GoogleCodeExporter]

You can also specify the initial window state in the properties of the shortcut 
you're launching mintty from, using the 'Run:' setting. Does ViGlance support 
that?

Original comment by andy.koppe on 26 Jun 2010 at 8:15

[GoogleCodeExporter]

Unfortunately, no.  Basically when you pin an app in ViGlance it just grabs the 
path to the binary and stores that in an opaque configuration.  When you click 
a pinned app it launches it directly.  You don't have any control over 
command-line options.  Kind of a strange decision for a launcher, but otherwise 
it's actually a really cool launcher for someone who is stuck on XP (at least 
on my work machine).

Original comment by scottwe...@gmail.com on 26 Jun 2010 at 12:29

[GoogleCodeExporter]

Hmm, that's not very good, is it? Another thing you'll be missing is the '-' 
argument that tells mintty to start bash as a login shell.

Sorry, but a flaw in a proprietary eyecandy app for an OS that's heading 
towards the knackers' yard is not a good reason for making changes to mintty.

If I added this one as a config file option, the obvious question would be, why 
not everything else? Answer: because the config file is for options dialog 
stuff, whereas command line options are for additional settings that only make 
sense at startup.

Now there is an argument to be made that everything should go into the config 
file anyway, and if I'd had any foresight the config file would use the same 
options format as the command line, but that's a different (enhancement) issue.

Original comment by andy.koppe on 26 Jun 2010 at 7:42

• Changed state: Rejected

[GoogleCodeExporter]

I've implemented config file versions of the command line options, including 
the one for the initial window state, for 0.9.7.

Original comment by andy.koppe on 17 Apr 2011 at 10:46

• Changed state: Verified
• Added labels: Difficulty-Medium, Milestone-0.9.7