Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 9 Aug 2002 01:05:52 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Program Options vs. cygwin env problem
Message-ID: <20020809050552.GA10606@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3D52DD11 DOT 9527 DOT BFD2D AT localhost> <3D52E690 DOT 3498 DOT 3113C4 AT localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D52E690.3498.3113C4@localhost>
User-Agent: Mutt/1.3.23.1i

On Thu, Aug 08, 2002 at 09:45:52PM -0700, Stephen C. Biggs wrote:
>On 9 Aug 2002 at 0:27, Christopher Faylor wrote:
>>under this, you can create an string entry named "default" with data
>>containing CYGWIN environment variable options.  If you add an "export"
>>option to the end of the data values, a CYGWIN environment variable
>>will be regenerated from the registry and visible in the environment.
>>
>>You can also set options for individual programs by adding an entry like:
>>
>> Name			Type		Data
>> c:\usr\sbin\inetd.exe	REG_SZ		tty export
>> 
>> That will make cygwin always set the cygwin option to tty and export
>> a CYGWIN=tty for every program that inetd invokes.
>
>Note that you recommend this...  Again, I have no CYGWIN variable, and it 
>is being generated by reading the registry: note that it also adds 
>"export" to the environment -- is this a bug?

I recommended it for the above inetd example, not for "default".  If you
think about what default does, it obviously doesn't make a lot of sense
to go to the extra effort of exporting the data from the registry to the
environment since it will just be read by every cygwin program anyway.
The only use that it would have in the default case is to expose the
settings from the registry.  I suppose that could be useful in some
cases.

>> Oh, and it looks like you are actually setting cygwin values on the
>> (Default) part of a registry entry.  This is just an entry that Windows
>> corrects.  It is not what Cygwin reads.  You have to actually *create*
>> an entry called "default" (lowercase without the parentheses).  Maybe
>> this is your whole problem.
>> 
>
>No, I have done exactly what you said, above.

Sorry but, no you haven't.  You misinterpreted what I said.  I said that
you should *create* a string entry called "default".  You didn't create
one.  You apparently used an existing "(Default)" that is established
when you created the "Program Options" key.  That is incorrect.

cgf

>>The main reason this this is not documented is that there is no
>>programmatic way to manipulate it and I am not comfortable with telling
>>people how to edit the registry "by hand".
>>
>>However, if you are familiar with the registry, then setting this value
>>should not be a big deal.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/