Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vim clutch

github.com

Post reply on HN
Print view View original

121–130 of 227 posts

Re: Vim clutch

#121

Post by weaksauce »

orthecreedence wrote: post #111
ehsanu1 wrote: post #91

Earlier quoted context omitted.

di" is one of my favorite commands. Delete everything inside the quotes not including the quotes. You usually want to replace what's inside the quotes, so hence use ci" cit is pretty nice for replacing a tag's inner html. And of course this works with parentheses - ci( - and brackets - ci[ - and curly braces and single quotes and angle brackets.. I love vim :)

Wow cit ...I've been wondering if this exists for a year now. I remember reading about it when I first started learning vim but it somehow eluded me afterwards. Thanks! I use ci{ all the time for functions and CSS. It's like magic. Whenever I'm using something like nano, I'll instinctively type what looks like a long string of gibberish: "jjjddo [oh crap] ..." Once you really start getting used to the language, it ma…

> Once you really start getting used to the language, it makes it frustrating to use anything else.

Indeed... That is why I have been contributing to Xvim[1] for Xcode it's so nice to have vim bindings in Xcode.

[1] https://github.com/JugglerShu/XVim

Re: Vim clutch

#122

Post by robomartin »

sofal wrote: post #119
robomartin wrote: post #109

I'll be the one voicing a contrarian opinion here. vi and vim are holdbacks from the days of 300 to 9600 BAUD modems. A time when more sophisticated interfaces were prohibitive. Back in those days it wasn't too uncommon for people to actually write their own text editors. I wrote a few, mainly in Forth, as I would bring-up self-designed systems. While I use VIM today when I have to I continue to think that in today's…

I don't think you'd find a military helicopter cockpit very "user friendly" either: http://www.helis.com/h/h53ecab.jpg We're talking about a general-purpose text editing tool used by experts for hours, days, and years on end. I understand that you like to click through your menus, but you'll have to excuse those of us who know what we're doing in vim and don't have the time or patience for that.

Who said anything about menus?

And, yes, funny enough, it just so happens that I would find the cockpit of a military helicopter very user friendly.

Re: Vim clutch

#123

Post by robomartin »

devth wrote: post #112
robomartin wrote: post #109

I'll be the one voicing a contrarian opinion here. vi and vim are holdbacks from the days of 300 to 9600 BAUD modems. A time when more sophisticated interfaces were prohibitive. Back in those days it wasn't too uncommon for people to actually write their own text editors. I wrote a few, mainly in Forth, as I would bring-up self-designed systems. While I use VIM today when I have to I continue to think that in today's…

I think you're missing the point that many developers choose vim over "modern" editors because of its highly efficient text-editing capabilities. The same points could be made about emacs. As to "user friendly" - depends on who the user is. Yes, this text box is infinitely more user friendly than vim when your mom is using it. That a foot-pedal might make vim more usable has nothing to do with vim being outdated or u…

OK, I'll bite. Please educate me. Give me a list of the "highly efficient text-editing capabilities".

Re: Vim clutch

#124

Post by sofal »

robomartin wrote: post #122
sofal wrote: post #119

Earlier quoted context omitted.

I don't think you'd find a military helicopter cockpit very "user friendly" either: http://www.helis.com/h/h53ecab.jpg We're talking about a general-purpose text editing tool used by experts for hours, days, and years on end. I understand that you like to click through your menus, but you'll have to excuse those of us who know what we're doing in vim and don't have the time or patience for that.

Who said anything about menus? And, yes, funny enough, it just so happens that I would find the cockpit of a military helicopter very user friendly.

With no justification of how you think a military helicopter cockpit is user friendly, I suspect you're just trolling now.

Re: Vim clutch

#126

Post by sofal »

robomartin wrote: post #123
devth wrote: post #112

Earlier quoted context omitted.

I think you're missing the point that many developers choose vim over "modern" editors because of its highly efficient text-editing capabilities. The same points could be made about emacs. As to "user friendly" - depends on who the user is. Yes, this text box is infinitely more user friendly than vim when your mom is using it. That a foot-pedal might make vim more usable has nothing to do with vim being outdated or u…

OK, I'll bite. Please educate me. Give me a list of the "highly efficient text-editing capabilities".

Start here: http://www.vim.org/docs.php

Re: Vim clutch

#128

Post by Freaky »

robomartin wrote: post #109

I'll be the one voicing a contrarian opinion here. vi and vim are holdbacks from the days of 300 to 9600 BAUD modems. A time when more sophisticated interfaces were prohibitive. Back in those days it wasn't too uncommon for people to actually write their own text editors. I wrote a few, mainly in Forth, as I would bring-up self-designed systems. While I use VIM today when I have to I continue to think that in today's…

> The damn text box I am using in this browser to enter this comment is far more user-friendly than VIM.

Either you're a terrible Vim user or you have a pretty awesome browser text box. I had to install a third party browser extension just to make the damn thing resizeable - woe is me if I want to do search/replace, indent anything, or do anything but the most trivial undo/redo operation. And who hasn't permanently lost stuff they've written into a form by hitting the wrong key?

Re: Vim clutch

#130

Post by robomartin »

sofal wrote: post #126
robomartin wrote: post #123

Earlier quoted context omitted.

OK, I'll bite. Please educate me. Give me a list of the "highly efficient text-editing capabilities".

Start here: http://www.vim.org/docs.php

That doesn't really answer the question, does it? The other poster made an assertion about VIM being more efficient. I would like to get a list from him (or her).
Post reply on HN