Wait, Shift+7 for slash? What keyboard layout is this? I had already noticed various other weird things about the layout depicted on the screen, but that one takes the cake.
Interactive Vim tutorial
201–210 of 230 posts
Re: Interactive Vim tutorial
#202Earlier quoted context omitted.
> I'm happy you like VSCode so much. I do too, but I don't think it really qualify as a IDE. Same goes for Atom. Unless you consider Sublime an IDE as well. It has all the features they do, mainly because they ripped it off to gain them. I never said it was an IDE. At least, I never intended to say it was, because it's not. > And now, after 3 years of learning, and tweaking, and practising, I get Vim. It took three y…
> I use VSCode, and I've found that I haven't had to leave the editor or install anything outside of VSCode plugins to make it operate as a Java IDE, Go IDE (OK, I had to install Delve), or Python IDE. You explicitly called it an IDE. > It took three years to learn to use Vim to be productive, is what you're saying here. Point and case. They didn't say that. Anyone without sever learning difficulties should be as pro…
> You explicitly called it an IDE.
I called it an editor that I made into an IDE. It operates no different than the most powerful IDEs available for the languages listed.
> Anyone without sever learning difficulties
Now you're just being rude.
Re: Interactive Vim tutorial
#203Earlier quoted context omitted.
> I'm happy you like VSCode so much. I do too, but I don't think it really qualify as a IDE. Same goes for Atom. Unless you consider Sublime an IDE as well. It has all the features they do, mainly because they ripped it off to gain them. I never said it was an IDE. At least, I never intended to say it was, because it's not. > And now, after 3 years of learning, and tweaking, and practising, I get Vim. It took three y…
> It took three years to learn to use Vim to be productive, is what you're saying here. Point and case. It didn't take three years to get productive. It probably took a few months before I was fully productive, and that was while learning a new language and new codebase at the same time. It's taken 3 years to get, not just comfortable and familiar but, beyond comfortable with Vim. It's taken 3 years for Vimming to be…
Fair enough!
I'm honestly glad it's working for you. The point of my original post was to talk to new users of Vim. You're quite well established with Vim so it's easy to have the opinion that it's not too difficult to use. However, I believe there are better options that enable people to be just as productive in a fraction, of a fraction of the time.
Good luck.
Re: Interactive Vim tutorial
#204(Incoming controversial anti-Vim comment. Down voting because you disagree is a poor show and a poor argument. Convince me otherwise with words, good sirs and madams.) Vim, beyond the very basics for server side administrative tasks, isn't worth your time. Vim isn't worth the investment in time for me, as an average programmer, and I doubt it's worth the time of most other (average) developers as well. It's a big inv…
Aside from the other comments, you're missing a huge part of what vim is about if you think that it's vim vs. every other IDE. I use IDE's but I use a vim plugin in every single one to enable the vim key binding so I can enjoy all the IDE has to offer AND vim at the same time. It's not just about the editor itself (which I will talk more about), it's about the editing paradigm it introduces. A paradigm that emphasizes programming efficiency over familiarity. I understand that trade off isn't for everyone though.
In contrast to what I just wrote, the ubiquitous nature of vim is a huge factor for anyone who does a lot of work on a number of remote servers where it's not feasible to use a GUI-based IDE. You can use nano if you really don't want to learn vim but I'd love to hear someone make a case for using nano over vim. You may only need to deal with this for 'basic server side administration tasks' but a lot of people have to do a significant amount of work on multiple servers due to data access and resource availability issues.
In addition, there is also the fact that a number of command line tools use vim key bindings for navigation (eg. man, less, more)
*Edit: grammar
Re: Interactive Vim tutorial
#205Wait, Shift+7 for slash? What keyboard layout is this? I had already noticed various other weird things about the layout depicted on the screen, but that one takes the cake.
Probably Spanish. It's a horrible layout for developers, curly braces involve alt-gr for instance...
Re: Interactive Vim tutorial
#206Earlier quoted context omitted.
> It took three years to learn to use Vim to be productive, is what you're saying here. Point and case. It didn't take three years to get productive. It probably took a few months before I was fully productive, and that was while learning a new language and new codebase at the same time. It's taken 3 years to get, not just comfortable and familiar but, beyond comfortable with Vim. It's taken 3 years for Vimming to be…
Fair enough! I'm honestly glad it's working for you. The point of my original post was to talk to new users of Vim. You're quite well established with Vim so it's easy to have the opinion that it's not too difficult to use. However, I believe there are better options that enable people to be just as productive in a fraction, of a fraction of the time. Good luck.
I mentioned this in another comment but it's worth reiterating: IDE's and vim are not mutually exclusive. Every IDE offers a vim mode or vim plugin that gives you the best of both worlds.
Re: Interactive Vim tutorial
#207Wait, Shift+7 for slash? What keyboard layout is this? I had already noticed various other weird things about the layout depicted on the screen, but that one takes the cake.
Probably Spanish. It's a horrible layout for developers, curly braces involve alt-gr for instance...
As well as the German layout. But you get used to if you don't know anything else.
Re: Interactive Vim tutorial
#208Earlier quoted context omitted.
For me the productivity boost is mostly a matter of having a suite of very powerful shortcuts/commands that I can use everywhere. I use them in all IDE's (IntelliJ, Visual Studio, Eclipse all have great vim plugins); I use them in any terminal I get access to, even when I can't install software; and I use them in less, Chrome, man and other other tools that copy vim's shortcuts either natively or through plugins. In…
+1 Also consider vim in your web browser (vimperator or vimfx or qutebrowser or vimium) Vim in your file explorer (vifm) Vim in your terminal (tmux in vim-mode) Vim in your mayonnaise for lunch ( https://lisalynnfit.vimtoday.com/images/thumbs/0000878_1200.... ) Vim as a floor wax/desert topping ( http://www.mysavings.com/img/link/large/74808.jpg ) and so forth.
You mentioned tmux... What is the best counterpart windows solution by you? vim+tmux is awesome.
Re: Interactive Vim tutorial
#209Author here. The tutorial succeeds if it gets people to have a superficial comprehension what Vim is about -- especially for those that have been putting off trying it out in a terminal. That's it. It doesn't really try to make you actually learn Vim. As a tutorial it could be made so much better. I don't have the energy slots for this project. But I feel anxious when I get feedback because I feel like there's some m…
It's a really, really good piece of work. I hope you keep making tutorials.
I was impressed with the high ratio of useful content to time spent, and how the full tutorial only seemed to take 10 - 20 minutes.
I'm a 6 or 7 year vim veteran, and your tutorial taught me I could combine numbers with commands. I didn't know that!
For anyone reading and scoffing, please don't think I'm some vimless noob, I know %s/regex/replacement/g visual block selection and edit mode ( ctrl-shift-v, cursor, shift-i, double esc ), split mode :sp, and so on, but I never knew about the numbers with commands, nor about shift-X for left of cursor delete.
So even as someone experienced in vim ( and who codes in vim for everything ), this has improved my productivity!
Thank you so much, a great piece of work. Hope you keep making more tutorials on topics.
Re: Interactive Vim tutorial
#210Author here. The tutorial succeeds if it gets people to have a superficial comprehension what Vim is about -- especially for those that have been putting off trying it out in a terminal. That's it. It doesn't really try to make you actually learn Vim. As a tutorial it could be made so much better. I don't have the energy slots for this project. But I feel anxious when I get feedback because I feel like there's some m…
It's a really, really good piece of work. I hope you keep making tutorials. I was impressed with the high ratio of useful content to time spent, and how the full tutorial only seemed to take 10 - 20 minutes. I'm a 6 or 7 year vim veteran, and your tutorial taught me I could combine numbers with commands. I didn't know that! For anyone reading and scoffing, please don't think I'm some vimless noob, I know %s/regex/rep…
Oh, that's informative to know--verifies my own perception--and makes me happy!
I appreciate your support. Thank you.