X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:  Re: configuring the backspace key, etc. (un-indenting doesn't work  with vim)
Date:  Fri, 18 Jul 2008 09:05:17 -0700
Lines: 40
Message-ID: <g5qf00$m4l$1@ger.gmane.org>
References:  <1216369565 DOT 12256 DOT ezmlm AT cygwin DOT com> 	 <COL101-W50D2DC39337F44D82B613EE6890 AT phx DOT gbl> <f60fe000807180616r3e3dccdbjaf41a66b8d973305 AT mail DOT gmail DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
In-Reply-To: <f60fe000807180616r3e3dccdbjaf41a66b8d973305@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Mark J. Reed wrote:
> On Fri, Jul 18, 2008 at 5:21 AM, Jay <jayk123 AT hotmail DOT com> 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.
Don't speak for me! I will speak for myself. I misconfigured vim for a 
reason. That reason was that backspace was not performing it's function 
in the first place. I didn't willy nilly go in there and say "Well let 
me add this just because it oughta be fun". Something was broken and I 
was attempting to fix it. What was broken was the natural and normal 
functioning of the backspace key. If that key was working in an expected 
and normal way why the hell would I be in there mucking around?!?

And as I said, the "documentation" was, ahem.... well less than 
instructive in this regard.
>> 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.
Come on now! 99% of the time you are. 99% of the other OSes get it 
right. Stop making excuses!
> 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.
I would not consider it valuable if it doesn't perform it's intended and 
labeled (mind you) function.
>> > 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...
You would if you admit that it was the system that was screwed up before 
that made you get under the hood in an attempt to fix it in the first 
place! You would if you were open minded enough to admit that it's only 
Unix that suffers this affliction with this specific key.
-- 
Andrew DeFaria <http://defaria.com>
Bureaucracy: a method of turning energy into solid waste.


--
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/