public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Re: Bug Report: bash-2.05b-4 - xit: command not found
@ 2002-09-09 13:32 Jerry D. Hedden
  0 siblings, 0 replies; 3+ messages in thread
From: Jerry D. Hedden @ 2002-09-09 13:32 UTC (permalink / raw)
  To: cygwin

I'm using bash 2.05b-4 and cygwin 1.3.12-4 (i.e., the lastest
versions).  (I had put the version in the subject line but not in the
body of the message.  Sorry.)

The scripts in my original message (below) consistently reproduce
this bug.  I even triple-checked it after getting your message.

-- Original Message --
From: "Joey Bernard" <bernard@caris.com>
Subject: Re: Bug Report: bash-2.05b-4 - xit: command not found

What version of bash are you using?  This works fine on my box using 
2.05b.  This is on cygwin 1.3.12-4.

-- Original Message --
From: "Jerry D. Hedden" <jdhedden@yahoo.com>
Subject: Bug Report: bash-2.05b-4 - xit: command not found

The bug is reproducible using the following two scripts:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit
--- End file 1 ---

--- Begin file 2: bug2.sh ---
#!/usr/bin/bash
exit
--- End file 2 ---

Running the first script gives the following:

prompt>  ./bug1.sh
./bug1.sh: line 3: xit: command not found

The 'e' is missing from 'exit'.
If you add an extra blank line to the end of bug1.sh as follows:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit

--- End file 1 ---

You now get the following:

prompt>  ./bug1.sh
./bug1.sh: line 3: it: command not found

Now the 'e' and 'x' are missing.
Another blank line as follows:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit


--- End file 1 ---

You get:

prompt>  ./bug1.sh
./bug1.sh: line 3: t: command not found

Only the 't' is left.  If you add a third black line, you get no
error most likely because all the letters in 'exit' have been 
'eaten'.

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Bug Report: bash-2.05b-4 - xit: command not found
@ 2002-09-09  7:22 Joey Bernard
  0 siblings, 0 replies; 3+ messages in thread
From: Joey Bernard @ 2002-09-09  7:22 UTC (permalink / raw)
  To: cygwin

What version of bash are you using?  This works fine on my box using 2.05b.  This is on cygwin 1.3.12-4.



-- Original Message --
From: "Jerry D. Hedden" <jdhedden@yahoo.com>
To: cygwin@cygwin.com
Send: 10:57 AM
Subject: Bug Report: bash-2.05b-4 - xit: command not found

The bug is reproducible using the following two scripts:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit
--- End file 1 ---

--- Begin file 2: bug2.sh ---
#!/usr/bin/bash
exit
--- End file 2 ---

Running the first script gives the following:

prompt>  ./bug1.sh
./bug1.sh: line 3: xit: command not found

The 'e' is missing from 'exit'.
If you add an extra blank line to the end of bug1.sh as follows:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit

--- End file 1 ---

You now get the following:

prompt>  ./bug1.sh
./bug1.sh: line 3: it: command not found

Now the 'e' and 'x' are missing.
Another blank line as follows:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit


--- End file 1 ---

You get:

prompt>  ./bug1.sh
./bug1.sh: line 3: t: command not found

Only the 't' is left.  If you add a third black line, you get no
error most likely because all the letters in 'exit' have been 'eaten'.






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Bug Report: bash-2.05b-4 - xit: command not found
@ 2002-09-09  7:05 Jerry D. Hedden
  0 siblings, 0 replies; 3+ messages in thread
From: Jerry D. Hedden @ 2002-09-09  7:05 UTC (permalink / raw)
  To: cygwin

The bug is reproducible using the following two scripts:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit
--- End file 1 ---

--- Begin file 2: bug2.sh ---
#!/usr/bin/bash
exit
--- End file 2 ---

Running the first script gives the following:

prompt>  ./bug1.sh
./bug1.sh: line 3: xit: command not found

The 'e' is missing from 'exit'.
If you add an extra blank line to the end of bug1.sh as follows:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit

--- End file 1 ---

You now get the following:

prompt>  ./bug1.sh
./bug1.sh: line 3: it: command not found

Now the 'e' and 'x' are missing.
Another blank line as follows:

--- Begin file 1: bug1.sh ---
#!/usr/bin/bash
./bug2.sh
exit


--- End file 1 ---

You get:

prompt>  ./bug1.sh
./bug1.sh: line 3: t: command not found

Only the 't' is left.  If you add a third black line, you get no
error most likely because all the letters in 'exit' have been 'eaten'.

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-09-09 20:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-09 13:32 Bug Report: bash-2.05b-4 - xit: command not found Jerry D. Hedden
  -- strict thread matches above, loose matches on Subject: below --
2002-09-09  7:22 Joey Bernard
2002-09-09  7:05 Jerry D. Hedden

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).