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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.0.1.1.0.20040204141551.039b4a60@127.0.0.1>
X-Sender: 
Date: Wed, 04 Feb 2004 14:20:27 -0500
To: "Buchbinder, Barry (NIH/NIAID)" <BBuchbinder AT niaid DOT nih DOT gov>,
   "'Cygwin List'" <cygwin AT cygwin DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: RE: Text entry to command line program
In-Reply-To: <F76C9B2DA2FC4C4CA0A18E288BBCBCF70361F18E@nihexchange24.nih .gov>
References: <F76C9B2DA2FC4C4CA0A18E288BBCBCF70361F18E AT nihexchange24 DOT nih DOT gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:41 AM 2/4/2004, Buchbinder, Barry (NIH/NIAID) you wrote:
>To be more specific, while tty must be set beforehand, 


Right, that's what the doc says and it's right! ;-)


>the web page is
>silent about other CYGWIN options.


Sounds sinister.  We must all combat this conspiracy of silence.


>Here's an example:  I set codepage:oem in CYGWIN.  When I run ascii, I see
>the correct OEM characters.  Then, in the same bash shell (no rxvt), if I
>change CYGWIN to have codepage:ansi, I get the ANSI characters.  Resetting
>in bash to codepage:oem gives OEM.  Then if I mark, block, and copy high
>order characters, and then paste the high order characters onto the command
>line, they look just like they were when ascii displayed them, no matter
>what codepage is set to.  if they were pasted behind echo, and then execute
>echo, again they look just like what they were when ascii displayed them.
>Doing echo x | tr x '\266' gives what character is appropriate for what
>codepage is set to at the time.
>
>So changing codepage in CYGWIN after a bash shell is launched can change
>cygwin behavior.


Yep.  Some options are only read at DLL start time.  Others are read 
"more frequently".  Feel free to offer a patch to the User's Guide to 
update it with this information for each option if you're interested.


>-----Original Message-----
>From: Larry Hall [mailto:cygwin-lh AT cygwin DOT com] 
>Sent: Wednesday, February 04, 2004 11:03 AM
>To: Ross Boulet; cygwin AT cygwin DOT com
>Subject: RE: Text entry to command line program
>
>At 09:26 AM 2/4/2004, Ross Boulet you wrote:
>>> [...]
>>> > > Try something like:
>>> > > 
>>> > > CYGWIN=notty sqlplus
>>> > > 
>>> > 
>>> > Is that saying notty for sqlplus and tty for everything else?
>>> [...]
>>> 
>>> No, that's an interactive command line, it's not a setting of 
>>> the CYGWIN
>>> variable (i.e. it's not CYGWIN="notty sqlplus"). The above 
>>> actually launches
>>> sqlplus, setting the CYGWIN variable to "notty" for its process.
>>> 
>>> SLao
>>> 
>>Unfortunately, this does not work.  I had previously tried setting CYGWIN
>>within a shell to no avail.  I found it must be set from dos before
>>launching bash or ksh.
>
>
>Correct.  Just as stated in the User's Guide:
>
><http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>
>
>
>--
>Larry Hall                              http://www.rfk.com
>RFK Partners, Inc.                      (508) 893-9779 - RFK Office
>838 Washington Street                   (508) 893-9889 - FAX
>Holliston, MA 01746                     
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Problem reports:       http://cygwin.com/problems.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Problem reports:       http://cygwin.com/problems.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/


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