X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 17 Jul 2008 14:02:08 -0400 From: "Mark J. Reed" 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-Google-Sender-Auth: 2793a05d20c0c7c7 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 > It is only in Unix that often the backspace key does not perform the function > of moving backward a space and deleting the previously character. I have > never, I repeat never had backspace not do a back space except under > Unix - have you? I've had such issues on many systems. VMS. MVS. NOS and NOS/VE. Not to mention several BBSes... You're forgetting that UNIX predates PC's. When not in a GUI, or when focus is in a terminal window, pressing the backspace key doesn't "perform" any "function" except to transmit a character to the input stream, just as if you were using a serial terminal. ASCII control characters were developed for printing teletypes, on which ASCII BS (chr(8)) would back the carriage up a character position (without deleting anything) while ASCII DEL (chr(127) a.k.a. RUBOUT) would delete (white out or X out) the character under the cursor without moving the carriage. Just as with CR/LF, CRT terminal behavior didn't match either of the definitions exactly, and different terminal manufacturers chose different ways of indicating to the host system that the terminal user had pressed the "undo that last keystroke" key. Most sent either BS or DEL, but some sent multibyte sequences ("escape sequences", even if they didn't involve the ASCII ESC code) or other values (the Commodore PET character set used CTRL-T for this; the Atari used a high-bit value [155, IIRC]). So UNIX software grew up in an environment of variable terminals. It is designed to be flexible about such things for that reason, and doesn't assume (the way other PC software does) that you're on the console of a PC with a local keyboard. Which means it is entirely possible to set things up so that it doesn't work as you expect. This is not UNIX's fault. The default configuration on Cygwin works as expected; you seem to have blindly imported a configuration file from some other UNIX environment, and poof, things broke. That's the price of using stuff without understanding it. -- 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/