X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,SPF_HELO_NEUTRAL X-Spam-Check-By: sourceware.org Message-Id: <201104142306.p3EN6XSx013784@tigris.pounder.sol.net> From: Tom Rodman X-From: cygwin@cygwin.com X-Reply-to: cygwin@cygwin.com To: cygwin@cygwin.com From: Tom Rodman Reply-to: cygwin@cygwin.com Subject: Re: interactive shell mis-parsing 1st two words on line In-reply-to: <201103030203.p23230Gg015878@tigris.pounder.sol.net> References: <201102252157.p1PLvCN0009250@tigris.pounder.sol.net> <201103030203.p23230Gg015878@tigris.pounder.sol.net> Date: Thu, 14 Apr 2011 18:06:32 -0500 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Greetings: I have updated cygwin since I last posted, and I'm still having this problem several times a day. It's as though the first space on the commandline is being seen as a semicolon. I wrote an expect script to attempt to force the problem - unfortunately after 100+ commandlines there were no problems; it only happens when I interactively type commands. It would be nice to hear that I'm not the only one seeing this. -- thanks/regards, Tom -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple