This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Extra newline with bash read?
- To: Fabio Somenzi <Fabio at Colorado dot EDU>
- Subject: Re: Extra newline with bash read?
- From: Elmet Orasson <elmet at cc dot ttu dot ee>
- Date: Mon, 2 Jun 1997 13:05:56 +0300 (EET DST)
- cc: "Richardson,Anthony" <ARichard at stark dot cc dot oh dot us>, "'Gnu-Win32 List'" <gnu-win32 at cygnus dot com>
On Fri, 30 May 1997, Fabio Somenzi wrote:
> >>>>> "R" == Richardson,Anthony <ARichard@stark.cc.oh.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@cc.ttu.ee>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".