Show HN: I built an interactive course that helps you learn Vim faster
241–250 of 265 posts
Re: Show HN: I built an interactive course that helps you learn Vim faster
#242I often use vim for editing files but not code. The need to adhere to corporate style pretty much kills it for that.
Is editorconfig any use there? It definitely makes life easier on projects where the contributors have a mix of tools. https://editorconfig.org/
Re: Show HN: I built an interactive course that helps you learn Vim faster
#243Earlier quoted context omitted.
Definitely a hurdle to overcome for beginners. Although, it would help to show beginners exactly why abandoning the mouse will be better in the long run. It wouldn't do well for them to always rely on it in place of more efficient commands. Some people might always use the arrow keys instead of hjkl, for example, when hjkl will be better in the long run since they are on the home row.
I buy the idea that the more advanced features of vim are worth it, being able to quickly cut+paste bits of text around, skip to end of line/bracket/etc. I don't believe I'd write usefully larger amounts of code by using hjkl instead of arrow keys, and personally I am always going to use the mouse when I want to move more than a couple of lines.
Re: Show HN: I built an interactive course that helps you learn Vim faster
#244Re: Show HN: I built an interactive course that helps you learn Vim faster
#245Re: Show HN: I built an interactive course that helps you learn Vim faster
#246Earlier quoted context omitted.
I use VSCode with NeoVim as a backend. https://github.com/vscode-neovim/vscode-neovim I highly recommend this if you know vim keybindings and want an IDE experience.
I use this too. This extension used to work amazingly well for me, but lately it’s been troublesome. I switched to it from vscode-vim after it destroyed my undo buffer one too many times, and vscode-neovim was great. It was fast, and it seemed solid. Now though, it will randomly stay stuck in command mode no matter how many times I mash i or I or A or o. Other times it will make changes a few lines away from where th…
Re: Show HN: I built an interactive course that helps you learn Vim faster
#247Earlier quoted context omitted.
I tried the same a couple of month ago and I came to the conclusion that VIM will never come close to editors like VS Code.
How is it that nobody seems to know that every major editor has either vim mode or a vim plugin. I love vim, but I almost never use it directly. I usually use JetBrains IDE with vim plugin. Best of both worlds.
What are you doing, 0 ??
Re: Show HN: I built an interactive course that helps you learn Vim faster
#248Earlier quoted context omitted.
Thanks for the feedback! The 8 lessons you mention are actually 8 chapters. There are actually 34 lessons right now (you can see the lessons if you click on the chapters to expand them). Please let me know if there are topics that you want to see, I wanna add what people want to learn!
Sorry, I meant 8 chapters. I read through the 34 lessons. I suggest you take a look at typingclub. 700+ lessons free of charge. Repetition, and metrics are the selling point. If you incorporate that model in vimified I think you’ll have way wider adoption.
I left the site and bought his other Vim book instead.
Re: Show HN: I built an interactive course that helps you learn Vim faster
#249Earlier quoted context omitted.
>...more efficient way of doing things? Is that a fact, or you just parroted other people who made similar claim?
For me it is not a fact, and I find vim objectively much more harder to use than “regular” editors. But it matches my thinking in a way that I don’t have to plan ahead how many times to press an arrow, or to wait until a key repeat rate gets the cursor where I want it to be. Acquired vim reflexes erase the complexity and leave this benefit. I always found this “faster” claim somewhat stretched and zealous. I don’t ne…
> I don’t have to plan ahead how many times to press an arrow
Usually, I'll just do something, e.g., hit dd to delete a line and then even though I could hit "3." to delete three more lines, I'd usually just repeatedly tap . to repeat that dd action. It doesn't really matter if the action is deleting a line or commenting/uncommenting it or changing capitalization or modifying a word in a certain way. The general strategy of doing the action you want and then repeating with . it is very useful.
Re: Show HN: I built an interactive course that helps you learn Vim faster
#250This looks very cool, kudos on the launch! I feel like vim tutorials mostly focus on navigating and editing a single file, which is great! But I mostly struggle with how to replicate opening a whole directory in VSCode, which makes it easy to browse the directory, switch between files, open multiple panels, etc. I'm almost certain vim does all these things out of the box, but tutorials always end at "this is how you…