X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <17393e3e0807171001m325de647y512d008a6f533ff0@mail.gmail.com> Date: Thu, 17 Jul 2008 13:01:51 -0400 From: "Matt Wozniski" To: cygwin AT cygwin DOT com Subject: Re: 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: <20080711130135 DOT GO24644 AT calimero DOT vinschen DOT de> <20080716155746 DOT GR24644 AT calimero DOT vinschen DOT de> <17393e3e0807170141v6dcc5088kc1d23ab59653a24e AT mail DOT gmail DOT com> 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 Thu, Jul 17, 2008 at 12:46 PM, Andrew DeFaria wrote: > Seems like my problem was I had a set t_kb=^? in my .vimrc as well as the > aforementioned fixdel. Indeed the mere fact that I included such things in > my .vimrc indicate that I was having problems with backspace not doing a > backspace. I assume that the ^? isn't the two characters ^ and ? and I > forget how to generate that anymore. In any event I found > http://www.stripey.com/vim/terminals.html which says to do "execute 'set > t_kb=' . nr2char(8)". This seems to be working now. Well, there's your problem. You told vim that the backspace key sends 0x7F, when in fact it sends 0x08 in your terminal emulator. Vim would have done the correct thing, if it ever saw a backspace, but it never saw 0x7F, only 0x08. :fixdel is archaic, and never necessary on modern systems; moreover you should always understand what a command does before trying to use it. ~Matt -- 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/