X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Fri, 18 Jul 2008 09:16:40 -0400 From: "Mark J. Reed" To: cygwin AT cygwin DOT com Subject: Re: configuring the backspace key, etc. (un-indenting doesn't work with vim) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1216369565 DOT 12256 DOT ezmlm AT cygwin DOT com> X-Google-Sender-Auth: a11c40a59ee21321 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Fri, Jul 18, 2008 at 5:21 AM, Jay wrote: > While Andrew's tone is a bit strong/rude, I do agree. > The keyboard should just work. And it does. Andrew had a misconfigured vim setup that was getting in the way. > PC keyboards have been for a very long time now. Yes. But, again, you're not always on the local attached keyboard when interacting with a Linux system. Admittedly, even when not local, 99.9% of the time you'll be using some sort of VT100/ANSI terminal emulator, so a lot of the flexibility of the termcap/terminfo system is overkill at this point. But the underlying abstraction - no matter how you are connected, it looks like a tty to the host software - is still valuable. > > That's the price of using stuff without understanding it. > > Oh man. > Let he who has not sinned cast the first stone.. Fair enough. But I do at least try not to blame "the system" when I screw something up because I didn't know what I was doing... -- Mark J. Reed -- 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/