Bash bug ?

Bash bug ?

[Pasa Guglielmo]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

It seems that there is a little bug in bash.
When you begin to type a command while bash prompt
is still not ready it prints the typed text in the reverse
order once ready.

And you cannot safely use the arrow keys without having
some kind of escape sequence apearing on the screen.
-- 
Sincerely yours,
				Pasa Guglielmo
------------------------------------------------------------------
¦ homepage: http://www.omedia.ch/pages/gpasa/			 ¦
¦----------------------------------------------------------------¦
¦ e-mail  : gpasa@omedia.ch       ¦  tel. :  +41 (0)24 485 50 40 ¦
¦ mailing : Pasa Guglielmo        ¦  fax  :  +41 (0)24 485 50 44 ¦
¦ 	    Rte des Cases 17A     ¦ 	  	  		 ¦	
¦ 	 CH-1890 St-Maurice       ¦  prof.: physicist		 ¦	
¦	    (Switzerland)         ¦				 ¦	
------------------------------------------------------------------
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Bash bug ?

[Chris Faylor]

In article < 345E7FB9.89577E0E@omedia.ch >,
Pasa Guglielmo  <gpasa@omedia.ch> wrote:
>It seems that there is a little bug in bash.
>When you begin to type a command while bash prompt
>is still not ready it prints the typed text in the reverse
>order once ready.
>
>And you cannot safely use the arrow keys without having
>some kind of escape sequence apearing on the screen.

Try Sergey's coolview release.  It should solve these problems:

	http://www.lexa.ru/sos

This is a recording...
-- 
http://www.bbc.com/	cgf@bbc.com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: Bash bug ?

[Earnie Boyd]

You must be on Win95.  I experience it only on Win95.  I reported the 
problem but don't remember any response.

It appears to me that the stdio buffer is being LIFOed instead of 
FIFOed.  I also think that this is the cause for the escape sequences 
not behaving properly.  ie: The left arrow displaying [d[d[d.

-        \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------

>Date: Tue, 04 Nov 1997 01:26:53 -0025
>From: Pasa Guglielmo <gpasa@omedia.ch>
>To: gnu-win32@cygnus.com
>Subject: Bash bug ?
>
>It seems that there is a little bug in bash.
>When you begin to type a command while bash prompt
>is still not ready it prints the typed text in the reverse
>order once ready.
>
>And you cannot safely use the arrow keys without having
>some kind of escape sequence apearing on the screen.
>--=20
>Sincerely yours,
>				Pasa Guglielmo
>------------------------------------------------------------------
>=A6 homepage: http://www.omedia.ch/pages/gpasa/			 =A6
>=A6----------------------------------------------------------------=A6
>=A6 e-mail  : gpasa@omedia.ch       =A6  tel. :  +41 (0)24 485 50 40 
=A6
>=A6 mailing : Pasa Guglielmo        =A6  fax  :  +41 (0)24 485 50 44 
=A6
>=A6 	    Rte des Cases 17A     =A6 	  	  		 =A6=09
>=A6 	 CH-1890 St-Maurice       =A6  prof.: physicist		 =A6=09
>=A6	    (Switzerland)         =A6				 =A6=09
>------------------------------------------------------------------
>-
>For help on using this list (especially unsubscribing), send a message 
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

RE: Bash bug?

[Brian Beuning, com]

I had some problems building on my d: drive for a while.
It seems by default the d: drive is not transparently accessible.
I think you can access it with something like //d/src or you
can use mount(1) to put it anywhere you want.  I did this
	c:
	md dos
	cd dos
	md d
	mount d: /dos/d

Then you can access d:\src as /dos/d/src.

Brian Beuning

----------
From: 	Steve Shepard
Sent: 	Tuesday, April 29, 1997 7:07 PM
To: 	gnu-win32@cygnus.com
Cc: 	sjs@navio.com
Subject: 	Bash bug?


Earlier, I sent mail to this list regarding a "cat" problem. In
digging into the problem further, I've found that it instead appears
to be a problem with bash redirection.

When redirecting input like in the following fragment from
gdb/configure)

echo $ac_n "checking for AIX""... $ac_c" 1>&6
cat > conftest.$ac_ext <<EOF
#line 717 "configure"
#include "confdefs.h"
#ifdef _AIX
  yes
#endif

I get "No such file or directory" error. This is the result of
redirecting the input. Nothing is written to the conftest file.

I'm trying to build gdb from the cdk and can't get past the configure
stage. Is this a known bash bug? I'm using b17.1 (all.tar.gz from
ftp://ftp.cygnus.com/pub/gnu-win32/gnu-win32-b17.1/ )

How have those out there who have build the tools successfully worked
around this? I've tried the mks tools and tcsh. The first has problems
with sed and the second with the script synax.

Regards,
Steve Shepard

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Bash bug?

[Steve Shepard]

Earlier, I sent mail to this list regarding a "cat" problem. In
digging into the problem further, I've found that it instead appears
to be a problem with bash redirection.

When redirecting input like in the following fragment from
gdb/configure)

echo $ac_n "checking for AIX""... $ac_c" 1>&6
cat > conftest.$ac_ext <<EOF
#line 717 "configure"
#include "confdefs.h"
#ifdef _AIX
  yes
#endif

I get "No such file or directory" error. This is the result of
redirecting the input. Nothing is written to the conftest file.

I'm trying to build gdb from the cdk and can't get past the configure
stage. Is this a known bash bug? I'm using b17.1 (all.tar.gz from
ftp://ftp.cygnus.com/pub/gnu-win32/gnu-win32-b17.1/ )

How have those out there who have build the tools successfully worked
around this? I've tried the mks tools and tcsh. The first has problems
with sed and the second with the script synax.

Regards,
Steve Shepard

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BASH bug?

[John A. Lewis]

Ray,

You should be able to fix this problem by creating a /tmp direcotry for
the shell to use.  You can do this by creating a directory called 'tmp'
wherever you have your root set up, or by mounting your windows temp
directory ('C:\Windows\Temp' perhaps?) as '/tmp'.

-- John Lewis


Ray Kelm wrote:
> 
> This doesn't work in a bash script:
> 
> #!/bin/sh
> 
> cat > test.txt <<EOF
> this is a test
> EOF
> 
> I get:
> 
> ./script: 73165732: No such file or directory
> 
> Is this a bug someone has fixed? or even seen?
> 
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: BASH bug?

[Geoffrey Noer]

> cat > test.txt <<EOF
> this is a test
> EOF
> 
> I get:
> ./script: 73165732: No such file or directory
> 
> Is this a bug someone has fixed? or even seen?

This is fixed in upcoming beta 18...

-- 
Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

BASH bug?

[Ray Kelm]

This doesn't work in a bash script:

#!/bin/sh

cat > test.txt <<EOF
this is a test
EOF

I get:

./script: 73165732: No such file or directory

Is this a bug someone has fixed? or even seen?

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".