Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <004c01c0dd88$3f506ce0$d938a8c0@Hadfield> From: "Mark Hadfield" To: "Steven Green" , References: <008701c0dd46$aa63f2a0$9801a8c0 AT wellington> Subject: Re: Keyboard handling, and CygWin 1.3.1 Date: Wed, 16 May 2001 09:44:41 +1200 Organization: NIWA MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 From: "Steven Green" > 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. In February this year there was an extensive discussion of Cygwin's handling of the AltGr key and a patch was submitted. This is an obvious place to look. I suggest you look at this message http://sources.redhat.com/ml/cygwin/2001-02/msg01636.html and/or search on the list archive for "AltGr" --- Mark Hadfield m DOT hadfield AT niwa DOT cri DOT nz http://katipo.niwa.cri.nz/~hadfield National Institute for Water and Atmospheric Research -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple