Earlier quoted context omitted.
I believe Vim-proper needs a plugin for that behaviour, so keep that in mind.
Do you know what plugin it is? I will try to search for an evil version (Or I could just write my own, but my task list is large and my energy very low these days)
Show HN: I built an online interactive course that helps you learn Vim faster
151–160 of 283 posts
Re: Show HN: I built an online interactive course that helps you learn Vim faster
#152I know I felt a constant social pressure to learn vim or emacs over the years in order to fit in with those religions. I gave in to that social pressure early on. But even 30 years ago in the early 90s when I started learning vim (and Linux), vim and emacs were very dated programs. Over the course of thirty years I have managed to finally learn how to set up syntax highlighting, terminal colors, and spaces vs tabs an…
Lots of people use vim just to appear hardcore and not because it confers serious editing advantage. Vim itself is a really really bad editor. It's so obvious that it was written by a programmer with commands like 5dd, 6gg etc. I find it so ridiculous that a computer program can be that much loved and yet it doesn't even provide line numbers out of the box nor indentation. Does a person really need to spend half an h…
Re: Show HN: I built an online interactive course that helps you learn Vim faster
#153Earlier quoted context omitted.
Even though, admit it... If the course is really good, the extra $10 are nothing compared to the several hours of frustration that you could save.
Or save all frustration and just don’t use vim ;-)
Re: Show HN: I built an online interactive course that helps you learn Vim faster
#154Earlier quoted context omitted.
> " by the way why on earth does this monstrosity want me to use hjkl? That don't make any sense!!!!" Indeed, why? Using hjkl is about the worst way to move around in vim...
/% qqnxq19@q is clearly the solution to the "navigate to % and delete it"
Re: Show HN: I built an online interactive course that helps you learn Vim faster
#155Re: Show HN: I built an online interactive course that helps you learn Vim faster
#156Enormous vim fan here. I’ve been toying with the idea of 1:1 “tutoring” of beginner vim and other Unix tools. If anyone might be interested in a free 1st lesson, send a DM!
Re: Show HN: I built an online interactive course that helps you learn Vim faster
#157Earlier quoted context omitted.
I just see a gray screen (after enabling javascript). EDIT: with another browser, it seems to work, and it looks very cool! But I wonder, what is the interest of learning vim outside of vim ? What are the advantages with respect to the similar tutorial "vimtutor" that comes with vim itself?
Awesome, glad you got it working :) I use vim inside of vs code and it’s been awesome for my workflow. vimtutor is a fantastic resource and I’d definitely recommend using it for anyone interested in learning vim. vim.so gives you more interactive exercises and helps to show you real life examples of where and how vim would be useful. Thanks for checking it out!
Re: Show HN: I built an online interactive course that helps you learn Vim faster
#158Re: Show HN: I built an online interactive course that helps you learn Vim faster
#159Can someone please explain to me why I should learn vim? I've made several attempts in my lifetime because I thought there would be some magical "ah-ha" moment, but it never came. Separate modes for command & insert just feels inherently clumsy and slow to me. Is there some other killer feature that can't or hasn't been reproduced by modern editors?
In vim, most commands take the form "[count] operator [count] motion". When you learn a new operator, you can use it with any motion that you know and vice versa; and you can add a count to either. To give a few examples: - gqip to format (gq) a paragraph (ip). - g?g? to ROT13 a line (doubling the operator makes it operate on the current line — in this case, g?? also works). - y2w to copy (y) the next two words (2w)…
From reading the rest of the replies, it sounds like the real answer is "because it's everywhere", which isn't really satisfying. I don't work on lots of machines that aren't my own (embedded/mobile space, which don't have vi installed!), so I don't actually encounter it everyday despite living on the command line.