Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sourceware.cygnus.com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin@sourceware.cygnus.com>
List-Help: <mailto:cygwin-help@sourceware.cygnus.com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Wed, 5 Apr 2000 17:47:10 -0400
To: Cygwin Mailing List <cygwin@sourceware.cygnus.com>
Subject: Re: bug or feature
Message-ID: <20000405174710.A4300@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cgf@cygnus.com,
	Cygwin Mailing List <cygwin@sourceware.cygnus.com>
References: <001d01bf9e5b$4b3a2ea0$930f4dd1@TIMYX18EWDT6RQ> <Pine.LNX.4.10.10004052254420.2202-100000@bono.reversers.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.8i
In-Reply-To: <Pine.LNX.4.10.10004052254420.2202-100000@bono.reversers.net>; from stefan@lkcc.org on Wed, Apr 05, 2000 at 11:05:01PM +0200

On Wed, Apr 05, 2000 at 11:05:01PM +0200, stefan wrote:
>2) Do Home and End work ? At my installation these keys produce a single
>   tilde (~).

That would depend on what you have your term type set to and if the key
definitions are part of the termcap or terminfo settings for the terminal
type.  I've just added them to the standard termcap that is bundled with
cygwin.

>3) Windows95 crashes now on Ctrl-C, that is *really* annoying ! Can anyone
>   help ? Windows NT does not.

What does "crashes now on Ctrl-C" mean?  You run bash and hit CTRL-C and
your Windows 95 system crashes?  Or, does just bash die?  If so, does
bash produce an error message?

>4) The bash produces now permission errors. Also very annoying. When
>   typing:
>   $ cat <<FOO
>   > 1
>   > 2
>   > 3
>   > FOO
>   you should get:
>   1
>   2
>   3
>   But i get something like "cannot document here: permission denied".
>   This is only when using bash.exe, sh.exe works out fine. Before i made
>   the above update it worked with bash too.

I don't see this, but I'm running the latest snapshot.  Is there some
reason why you decided to run an older snapshot?

>5) The newly created directory i686-??? for the header files is not
>   automatically used by the compiler. I guess these are just for another
>   target. But i would like to use the updated headers, because
>   "vsnprintf(), snprintf()" and other fixes from earlier headers.

Update your gcc.  See Mumit Khan's web page for details.  Check out
http://sourceware.cygnus.com/cygwin/ for a link to his web page.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com