install on win7 enterprise, can't modify bash start up shortcut

[LMH]

Thank you for all the clarification on shells and terminals, I have 
always used the terms interchangeably, which I guess was not correct.

A few replies,

 > Is there any religious taboo that would prevent you from opening the
 > batch script in an editor and see that you're wrong?

No, I did this on my XP cygwin install, and there is clearly nothing 
there to indicate the windows size, nor was there anything in the bashrc 
files, so I didn't know where to look next. I suppose I need to look at 
ini files for the terminal that gets started.

 > That window belongs to cmd.exe; bash runs inside it. The settings are
 > in the registry; for the Cygwin shortcut it's

This would imply that I'm trying to change a registry setting related to 
cmd.exe and the OS isn't letting me. The confusing thing is that I have 
done this before on the exact same OS and not had this issue.

Just for giggles, I tried to change the terminal settings for my windows 
command line shortcut. I did not get the same error, but I did notice 
that there was a menu entry called "Defaults" as well as "Properties". 
This gives the same options, but this time when I save them there is no 
error. Changing the defaults changes the window options for both the 
bash shortcut and the windows cmd shortcut (I have both on my desktop).

So I guess this is resolved, but I suppose I should look in to running 
the mintty terminal. What are the basic advantages of this compared to 
running in cmd?

LMH



Corinna Vinschen wrote:
> On Aug 19 21:19, Csaba Raduly wrote:
>> On Fri, Aug 19, 2011 at 8:31 PM, LMH  wrote:
>>
>> (Please don't top-post)
>>> I've had no issue with re-sizing the bash window in the past and having
>>> those changes saved to the shortcut, even on win7 ent, so I am concerned
>>> about the health of the install.
>>
>> The health of the Cygwin install should be unrelated. I gues  this is
>> some Windows-y permission issue.
>> The shortcut points to cygwin.bat; Windows runs cmd.exe to interpret
>> the batch file, which eventually starts bash.
>>
>>> The desktop icon points to Cygwin.bat, but
>>> that doesn't have anything in it about the bash shell. Can someone point me
>>> to the ini file where the specs of the bash window would be recorded?
>>
>> That window belongs to cmd.exe;
>
> No, not really.  Cmd is a shell, like bash.  Up to Windows Vista and
> Server 2008, the console itself was implemented as just a bunch of
> library functions and a shared core in the csrss process.  Start bash
> from Explorer, and in Task Manager you will see that no cmd is running.
>
> Starting with Windows 7 and Server 2008 R2, the console window is
> implemented as a standalone application called conhost.exe.  So, if you
> start bash from explorer in W7, you will not only see bash, but also an
> additional conhost process.  So, in a way conhost is the same as mintty,
> a terminal emulator, even if not a good one.
>
> Either way, that's a common misunderstanding of the way the Windows
> console works.  It was never cmd.  Cmd is and always was only a shell,
> just another console application like bash.
>
> I hope it goes without saying why you see a cmd process in task manager
> when you started bash via the Cygwin.bat batch file...
>
>
> Corinna
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple