X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4A1FD2B7.90506@cornell.edu> Date: Fri, 29 May 2009 08:19:03 -0400 From: Ken Brown User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: emacs -nw keypad, tpu-edt.el, and C-h References: <4A168F2B DOT 4020805 AT cornell DOT edu> <4A1BD971 DOT 70808 AT cornell DOT edu> <83bppfskbt DOT fsf AT gnu DOT org> <4A1C5831 DOT 6030008 AT cornell DOT edu> <99716858969849F89D65A4015B9948F7 AT HEPNTLTIM3> <4A1C9952 DOT 8040100 AT cornell DOT edu> <4A1D9D05 DOT 40407 AT cornell DOT edu> <838wkhsm5e DOT fsf AT gnu DOT org> <4A1E7C50 DOT 8020505 AT cornell DOT edu> <416096c60905280702m6e4cb748ic305be3592d81c70 AT mail DOT gmail DOT com> <83ws8042o2 DOT fsf AT gnu DOT org> In-Reply-To: <83ws8042o2.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 5/29/2009 6:35 AM, Eli Zaretskii wrote: >> Date: Thu, 28 May 2009 15:02:35 +0100 >> From: Andy Koppe >> There's an ancient and pointless argument about whether the Backspace >> key should send ^H (0x08) or ^? (0x7F). > > Actually, this holy war can be bypassed, without sacrificing Emacs > correctly working on a console. What the console should send for that > is the function key. Makes sense to me. Andy, is there any reason all cygwin terminals shouldn't do this (including mintty)? This already happens under X, and users would then have consistent behavior. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/