Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Christopher Faylor Date: Tue, 15 May 2001 10:06:46 -0400 To: cygwin@cygwin.com Subject: Re: Keyboard handling, and CygWin 1.3.1 Message-ID: <20010515100646.H26560@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <008701c0dd46$aa63f2a0$9801a8c0@wellington> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i yrom: Christopher Faylor In-Reply-To: <008701c0dd46$aa63f2a0$9801a8c0@wellington>; from steven@greenius.co.uk on Tue, May 15, 2001 at 03:55:13PM +0200 On Tue, May 15, 2001 at 03:55:13PM +0200, Steven Green wrote: >On Thursday, May 10, 2001 12:17 PM, I wrote: > >> I have a UK keyboard with keyb uk loaded in autoexec.bat. Since version >> 1.3.1-1 of CygWin the pipe key (|) doesn't work inside Bash. Going back >to >> version 1.1.8-2 of Cygwin.dll works again. > >This seems to be a Windows 98/Me problem... on Windows 2000, the pipe key >works fine. > >Can someone familiar with the CygWin spurce code, point me towards where the >keyboard handling is done, so I can see what changed between versions. I >checked code out from CVS but can not find where keyboard stuff is done. >What I don't understand is how programs like Vim (which presumably use >Cygwin.dll) handle the pipe key properly, but Bash doesn't.... but it was by >downgrading Cygwin.dll that made it work again, which points towards Cygwin >being the culprit rather than Bash. Hmm. A grep for the word "keyboard" unearthed a plethora of likely candidates for investigation. Most of them were in one file. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple