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.1.0.6.0.20040414111729.030a1978@127.0.0.1>
X-Sender: 
Date: Wed, 14 Apr 2004 11:23:31 -0400
To: Daniel Clausen <sargon AT mac DOT com>, Cygwin List <cygwin AT cygwin DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: zsh and cygwin
In-Reply-To: <12631888.1081955720500.JavaMail.sargon@mac.com>
References: <12631888 DOT 1081955720500 DOT JavaMail DOT sargon AT mac DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:15 AM 4/14/2004, you wrote:
>On Wednesday, April 14, 2004, at 04:25PM, Larry Hall <xxx AT xxx DOT xxx> wrote:


<http://cygwin.com/acronyms/#PCYMTNQREAIYR>



>[snip]
>
>>>Most of my co-workers already switched to using bash, since there never
>>>was an issue with it. Now I could do that too but I love zsh. ;)
>>>
>>>Anyone else experiencing this? Comments? Ideas? Shrieking epitaphs?
>>
>>
>>Sure.   There have been some problems over time.  Check the email archives 
>>if you're interested in details.
>
>Actually I did check the archives whenever I had issues with zsh/cygwin
>in the past.
>


Good.  Thanks.



>>I have a sneaking suspicion that you began this thread for a reason but 
>>I'm not going to jump to any conclusions (or 'take the bait' ;-) )
>
>It's definitely not meant as a flame or anything like that. If it
>sounded that way, I'm sorry.
>
>I realize the initial post was vague, but that was intentional.
>I don't want to discuss the _current_ issue with zsh/cygwin, (if it
>still exists like about 1month ago) but was more wondering how fellow
>zsh/cygwin users feel about the situation and how they usually
>handle the problems. (like maybe they use zsh for 'regular work' but
>have a lil wrapper for 'make' which starts it in a bash or something
>like that)


The best way to handle problems is to report them in as much detail as 
possible and/or work to resolve them (patch/test/debug).  The ways 
that you mention above to handle the problems are "work-arounds".  If
possible, it's best to avoid this situation and just fix the problems
instead.  Hopefully, that makes everyone feel happy. ;-)



--
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/