X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: http://www.cygwin.com/ml/cygwin/2001-03/msg01023.html reply Date: Fri, 8 Dec 2006 17:59:02 -0000 Message-ID: <013f01c71af2$8b8203f0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <25014BD780E09C4C9CAA23E7E47B317D067E1A@MAIL2.csw.l-3com.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 08 December 2006 17:36, Voss, Douglas C @ CSW-SLC wrote: > I'm not sure how this works to put up a reply, People don't usually bother replying to 5-year old problem reports! > but having the same problem, You probably don't have the same problem. The OP's problem was having the backslash escaping the space between {} and ; meaning that the whole sequence was treated as one word "{} ;" rather than two words "{}" and ";". Unless you made the same mistake in your command line, your problem is a different one. > I found a solution not included in the followups: Essentially the same solution! > Try it without the \ before the ; Actually, the cause of your problem is that you're running all the commands from a DOS shell, not a bash shell, so the ; does not need to be escaped as it is only a command terminator in bash, not cmd.exe; your solution *will* fail in a bash shell. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/