From:	dbe AT wgn DOT net ("$Bill Luebkert")
Subject:	bash won't accept the letter 'k', etc
29 May 1997 09:23:14 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<338D0DAB.63AF.cygnus.gnu-win32@wgn.net>
Reply-To:	dbe AT wgn DOT net
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (Win95; U)
Original-To:	"gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

I've managed to get most of the stuff in b18 running (still have a lot
of questions and playing to do) on Win95.

When i type 'k' on the command line I get a gong on Win95 and no echo 
of the 'k'.  All other keyboard chars are ok.

Anyone know what's up?

Is there some further info on setting up your environment somewhere?

In particular, directories /etc and /bin (or /usr/bin), mounts, 
termcaps, config files in general, what gets called when, and all 
of that kind of stuff.  Maybe a nice detailed FAQ on setup of both 
bash and b18 in general (mounts and such).  Sorry if I missed a 
pointer somewhere, but I can't find much in the doc area online.

Someone mentioned using vim for man pages.  I use vim all the time,
how do you get it to convert nroff in vim?  Is there a macro or 
set stmt you need to issue?

-- 
  ,-/-  __      _  _         $Bill Luebkert
 (_/   /  )    // //       DBE Collectibles
  / ) /--<  o // //      http://www.wgn.net/~dbe/
-/-' /___/_<_</_</_    Email: dbe AT wgn DOT net
-
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 -