Mail Archives: cygwin/2005/06/29/20:26:40
At 08:15 PM 6/29/2005, you wrote:
>Larry Hall wrote:
>
>>At 05:44 PM 6/29/2005, you wrote:
>>>Okay. Setting CYGWIN=tty did not work as expected.
>>
>>
>>So you started a command prompt without any Cygwin shell running in it,
>>set CYGWIN="tty" and then started bash?
>
>No - I set it in my .bash_profile and exported it, then started Cygwin using the shortcut created by the install.
OK, that's the problem then.
>>Maybe I missed it but I don't recall Igor pointing you to a readme. You
>>can certainly look at the User's Guide:
>>
>><http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>
>
>Thanks. Igor mentioned the emacs readme in this posting:
>http://www.cygwin.com/ml/cygwin/2005-06/msg01106.html
OK yes, I just missed that then. I was looking for an actual pointer/path/
filename so my skim missed it.
>>>... I've included the output from cygcheck -svr below.
>>
>>Actually, we prefer (and ask for it) *attached*, not included/inlined.
>>
>
>Apologies - I got the "not" on the wrong part.
Yeah, you have lots of company. ;-)
>Result: setting CYGWIN=tty in a Win Cmd32 shell and running bash/Cygwin
>works properly. Is the indication, then, that I should set this as a Win
>environment variable instead of it being in my .bash_profile?
Right. That's the easiest thing to do to make sure it's set properly for
all shells you might launch from anywhere.
--
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/
- Raw text -