From:	elmet AT cc DOT ttu DOT ee (Elmet Orasson)
Subject:	Re: Extra newline with bash read?
2 Jun 1997 09:16:24 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<Pine.GSO.3.95.970602125017.24883C-100000.cygnus.gnu-win32@marvin>
Mime-Version:	1.0
Original-To:	Fabio Somenzi <Fabio AT Colorado DOT EDU>
Original-cc:	"Richardson,Anthony" <ARichard AT stark DOT cc DOT oh DOT us>,
	"'Gnu-Win32 List'" <gnu-win32 AT cygnus DOT com>
In-Reply-To:	<199705310346.VAA03898@boulder.Colorado.EDU>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

On Fri, 30 May 1997, Fabio Somenzi wrote:

> >>>>> "R" == Richardson,Anthony  <ARichard AT stark DOT cc DOT oh DOT us> writes:
> 
>  R> My shell scripts that use "read" to get user input aren't working.
>  R> Here's a simple example:
> 
>  R>  #!/bin/sh echo -n "input a1: " read a1 echo -n "input a2: " read
>  R> a2 echo "a1 = " $a1 echo "a2 = " $a2
> 
>  R> It doesn't wait for input at "read a2" and a2 doesn't get set.  Is
>  R> the "Enter" key being read as a <CR/NL> pair?  Is there a fix?
> 
> You may want to try "C-j" instead of "Enter." It's a workaround rather
> than a fix.

I have same problem with extra newlines when executing some .exe files.
If the executed program tries to read from stdin it will get an empty line
first.

Also I cant get some special symbols in bash with my estonian keyboard.
Bash doesnt seem to support combinations like AltGr+"~" spc for "~",
AltGr+"^" spc for "^" etc. Any ideas?




Elmet Orasson
<elmet AT cc DOT ttu DOT ee>

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

- Raw text -