X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <5195c8760901052113i531a01eeucd7e7aa0f36c8dc3@mail.gmail.com>
Date: Tue, 6 Jan 2009 10:43:40 +0530
From: "Jeenu V" <jeenuv AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cmd.exe from Cygwin
In-Reply-To: <4962DE56.6040007@cygwin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5195c8760901020359y51dbe19cw2803e36afe028c1d AT mail DOT gmail DOT com> 	 <5195c8760901051014h201d425cp927f31c1cb941233 AT mail DOT gmail DOT com> 	 <4962569C DOT 9070607 AT cygwin DOT com> <4962856F DOT 4090206 AT equate DOT dyndns DOT org> 	 <5195c8760901051704w4a68c10ehcde6cd5610fa9f3 AT mail DOT gmail DOT com> 	 <4962CAA1 DOT 9080104 AT cygwin DOT com> 	 <5195c8760901051957l64bc2a20gfd246ca684f689a4 AT mail DOT gmail DOT com> 	 <4962D8ED DOT 1000109 AT cygwin DOT com> 	 <5195c8760901052020l6dd3669bif4ffe5525846f03d AT mail DOT gmail DOT com> 	 <4962DE56 DOT 6040007 AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Tue, Jan 6, 2009 at 10:00 AM, Larry Hall (Cygwin)
<reply-to-list-only-lh AT cygwin DOT com> wrote:
> And I assume that you don't have this problem if you just invoke
> 'cmd.exe' from Windows and try the same thing and further that it
> does reproduce if you then invoke 'bash' from that command prompt
> and then 'cmd.exe' again.

cmd.exe from Windows: no; it behaves normally
cmd.exe -> bash -> cmd.exe: same problem

> I watched the screencast.  That's how I came to understand the
> problem you were seeing.  I wouldn't say I couldn't reproduce it
> otherwise.  I try really hard not to lie about this kind of thing. ;-)

Just making sure, you know :)

I checked with one of my colleagues who has Cygwin installed, but he
doesn't seem to have this problem. I feel like going with a fresh
installation.

-- 
:J

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