Re: Bugs in Cygnus Tools bash

2002-12-24 Thread Christopher Faylor
On Tue, Dec 24, 2002 at 02:28:55PM -, Cliff Hones wrote: >>>A word of advice - don't report things as bugs unless you are sure they >>>are bugs and not cockpit error - it can make you look foolish if you or >>>your configuration are to blame. >> >>That seems a bit harsh. How else are people su

Re: Bugs in Cygnus Tools bash

2002-12-24 Thread Cliff Hones
> > A word of advice - don't report things as bugs unless you are sure > > they are bugs and not cockpit error - it can make you look > > foolish if you or your configuration are to blame. > > That seems a bit harsh. How else are people supposed to figure out > what's wrong if they don't ask? Ther

Re: Bugs in Cygnus Tools bash

2002-12-24 Thread Larry Hall (RFK Partners, Inc)
At 07:37 AM 12/24/2002, Chris Game wrote: >In a recent post, Cliff Hones wrote: > > > A word of advice - don't report things as bugs unless you are sure > > they are bugs and not cockpit error - it can make you look > > foolish if you or your configuration are to blame. > >That seems a bit harsh. H

Re: Bugs in Cygnus Tools bash

2002-12-24 Thread Chris Game
In a recent post, Cliff Hones wrote: > A word of advice - don't report things as bugs unless you are sure > they are bugs and not cockpit error - it can make you look > foolish if you or your configuration are to blame. That seems a bit harsh. How else are people supposed to figure out what's wro

Re: Bugs in Cygnus Tools bash

2002-12-23 Thread Norman Vine
Scheinert Frank writes: > > 1st Bug > myPrompt>man man > bash: man: command not found USER ERROR: you didn't install the man package > Finally, the bash itself doesn't know the getopts function USER ERROR: % help help help: help [-s] [pattern ...] Display helpful information about bu

Re: Bugs in Cygnus Tools bash

2002-12-23 Thread Cliff Hones
[EMAIL PROTECTED] wrote >... > Finally, the bash itself doesn't know the getopts function > > ... > User defined functions like > > function usage > { > echo blabla > } > > produce a "function: not found" output. Are you trying this in a shell script? If so, you may be inadvertently using th

RE: Bugs in Cygnus Tools bash

2002-12-23 Thread Vince Hoffman
> -Original Message- > From: Scheinert Frank EXT > [mailto:[EMAIL PROTECTED]] > Sent: 23 December 2002 13:20 > To: '[EMAIL PROTECTED]' > Subject: Bugs in Cygnus Tools bash > > > Version : GNU bash, version 2.05b.0(8)-release (i686-pc-cygwin) > &g

Re: Bugs in Cygnus Tools bash

2002-12-23 Thread Max Bowsher
Scheinert Frank EXT <[EMAIL PROTECTED]> wrote: > bash: man: command not found So install man. > info command gives no getopts information. Shell builtins have never been individually listed in info. > 2nd Bug > User defined functions like > > function usage > { > echo blabla > } > > produce

Re: Bugs in Cygnus Tools bash

2002-12-23 Thread Corinna Vinschen
On Mon, Dec 23, 2002 at 02:19:46PM +0100, Scheinert Frank EXT wrote: > Version : GNU bash, version 2.05b.0(8)-release (i686-pc-cygwin) > > 1st Bug > following output is created by man, help and info commands: > > myPrompt>man man > bash: man: command not found You didn't install the man package.

Bugs in Cygnus Tools bash

2002-12-23 Thread Scheinert Frank EXT
Version : GNU bash, version 2.05b.0(8)-release (i686-pc-cygwin) 1st Bug following output is created by man, help and info commands: myPrompt>man man bash: man: command not found myPrompt>help ... getopts optstring name [arg] ... myPrompt>info ... * fold: (coreutils)fold invocation.