Subject: Re: Extra newline with bash read?
From: [email-masked] (Elmet Orasson)

2 Jun 1997 09:16:24 -0700
Approved: [email-masked]
Distribution: cygnus
Message-ID: <Pine.GSO.3.95.970602125017.24883C-100000.cygnus.gnu-win32@marvin>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Original-To: Fabio Somenzi <[email-masked]>
Original-cc: "Richardson,Anthony" <[email-masked]>,
        "'Gnu-Win32 List'" <[email-masked]>
In-Reply-To: <[email-masked]>
Original-Sender: [email-masked]

On Fri, 30 May 1997, Fabio Somenzi wrote:

> >>>>> "R" == Richardson,Anthony  <[email-masked]> 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
<[email-masked]>

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".