Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: ericblake AT comcast DOT net (Eric Blake) To: "Maloney, Michael" , cygwin AT cygwin DOT com Subject: Re: echo $? Date: Thu, 28 Jul 2005 17:32:13 +0000 Message-Id: <072820051732.8857.42E9169D000769CB0000229922007358340A050E040D0C079D0A@comcast.net> X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0 > I am trying to get my current expect scripts to run with the latest > cygwin but am having problems with the cmd-prompt after issuing the > command above. After the "echo $?", the expected prompt is returned but > with white space before it. I've never seen this before on Windows or > Unix. > What is your $PS1? And what shell (and version) are you running? There is a known bug in bash-3.0-7 with certain prompts displaying incorrectly, so if expect is postprocessing a screen-capture, I could see the prompt display bug being the cause of your concern. Usually, when post-processing shell output, the shell was not run in interactive mode, so that prompts are not part of the shell output; maybe more information about how you are running expect and why you expect (pardon the pun) to see the prompt as part of the output would also be helpful in diagnosing the problem. Hint - following these directions will help us know more about your setup, to see if anything obvious jumps out with your installed versions. As it is, your uname output mentions cygwin-1.5.17, although 1.5.18 is the latest, so you probably have several out-of-date packages. > Problem reports: http://cygwin.com/problems.html -- Eric Blake volunteer cygwin bash maintainer -- 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/