<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'>Oh, and by the way, when I do use Netbeans, I use a plugin that puts it in "vi mode". ;-)<br><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Scott Plante" <splante@insightsys.com><br><b>To: </b>"Atlanta Linux Enthusiasts" <ale@ale.org><br><b>Sent: </b>Wednesday, October 23, 2013 2:22:49 AM<br><b>Subject: </b>Re: [ale] Survey -- preferred Text Editor<br><br><style>p { margin: 0; }</style><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div>vim</div><div><br></div>I'm similar. I began using vi coding on Wyse or Link terminals and <div>the flow control never worked. You couldn't just hold an arrow key </div><div>down or the terminal would get completely hosed up. So I was forced</div><div>to learn and use all the vi movements, like w for next word and $ for </div><div>end of line, and eventually more complicated ones. They became</div><div>muscle memory and now I can edit much faster in vim usually.</div><div><br></div><div>Occasionally I'll use Netbeans when I'm doing GUI development</div><div>or some of it's handy refactoring tools, but I still use vim. The trick</div><div>I think is getting past the basic learning curve--it's a horrible editor</div><div>when you only use the arrow keys, insert, and backspace, which I've</div><div>seen some sysadmins & programmers do in the past. </div><div><br></div><div>Scott<br></div></div></div></div></body></html>