Don't lead off with the history. #protip
History and Effective Use of Vim
211–220 of 226 posts
Re: History and Effective Use of Vim
#212Been using vim since 1998 and rarely stray unless I'm typing notes for something unimportant and them I use Nano. Back in the day when I was a Unix admin, we often worked in full screen terminals and when editing a config file didn't like having to close the vim instance to go look at something, so learned about this little gem: :sh (go back to shell and do your thing and leave vim running) Ctrl-d to return to intact…
I wouldn't even use nano for typing notes; I'm so used to vim that I don't see why I wouldn't want its powers, even for something as simple as writing notes. I might very well want to reorder the notes, for instance: that's very easy in vim with dd/p. nano might have some Ctrl-key combo that does the same thing, but why bother learning that when I already know vim?
The worst thing is when you start typing Vim commands in programs that are not Vim.
Re: History and Effective Use of Vim
#213Earlier quoted context omitted.
This makes sense if you don't use vim as an IDE, but if you do, configurations and plugins are essential. Of course, you wouldn't expect to have a fully configured jetbrains IDE when you SSH into a remote server, but that doesn't mean you can't use one on your local development machine.
> This makes sense if you don't use vim as an IDE, but if you do, configurations and plugins are essential. Your parent ( https://news.ycombinator.com/item?id=20481729 ) does say that: > > Of course, that's just me. I understand why someone would want to turn Vim into their personalized powerhouse editor with IDE powers, with their .vimrc a 'git pull' away.
I am pretty sure that was edited in after my comment, but it could just be a reading fail.
Re: History and Effective Use of Vim
#214After years of a love/hate relationship with Vim (I love what it does, but have configuring it), I had an epiphany: by sticking with the defaults, whether they are my preferred choices or not, I can instantly understand how to use Vim in any environment. Once you get used to biting the bullet and hitting escape instead of jj, or ctrl+c, it just works, everywhere. If you abandon the urge to pimp out your Vim with a bi…
I tend to only mess slightly with my .vimrc, but I get fancy in my .gvimrc for this reason.
Re: History and Effective Use of Vim
#215After years of a love/hate relationship with Vim (I love what it does, but have configuring it), I had an epiphany: by sticking with the defaults, whether they are my preferred choices or not, I can instantly understand how to use Vim in any environment. Once you get used to biting the bullet and hitting escape instead of jj, or ctrl+c, it just works, everywhere. If you abandon the urge to pimp out your Vim with a bi…
I’m a long time VI(m) user, who started with emacs. I’m proficient in both editors, but use vim as my daily driver. When I started my career, my mentor was an emacs user, and the reason I started with emacs. I became very proficient with the editor, learning how to handle multiple buffers, window splits, rectangle selects, etc. At that time, I didn’t know vi. Until I started working on another project, where the proj…
“Son, you got to know vi just enough so you don’t look stupid.”
Put that on a t-shirt.
Re: History and Effective Use of Vim
#216Earlier quoted context omitted.
You're quite green, aren't you?
It may seem that way, but no I've crossed that chasm long ago. I've debugged on production more than I would ever care to remember. But in all honesty it is easier than ever to stay completely off of production. It's also extremely cost effective. It's not simple and it is work, but it has never been easier to actually be successful at staying off if production.
Easier then ever maybe but still probably impossible to avoid. It's not that anyone wants to mess up with live, it's more like you don't have a choice.
Re: History and Effective Use of Vim
#217After years of a love/hate relationship with Vim (I love what it does, but have configuring it), I had an epiphany: by sticking with the defaults, whether they are my preferred choices or not, I can instantly understand how to use Vim in any environment. Once you get used to biting the bullet and hitting escape instead of jj, or ctrl+c, it just works, everywhere. If you abandon the urge to pimp out your Vim with a bi…
Some defaults aren't very usable, although "Debian defaults" are very close. I had the same approach, but lately I've decided to add plugins or configuration to "enhance" and never "replace", and I have never been happier as I'm now with vim. I also decided to invest some time to move to vim + tmux instead of using gvim and now that I'm used to the extras I get with tmux (yep, terminal support in vim 8 is nice but no…
There's also tpope's vim-sensible but I think nvim took nearly all of them.
Re: History and Effective Use of Vim
#218After years of a love/hate relationship with Vim (I love what it does, but have configuring it), I had an epiphany: by sticking with the defaults, whether they are my preferred choices or not, I can instantly understand how to use Vim in any environment. Once you get used to biting the bullet and hitting escape instead of jj, or ctrl+c, it just works, everywhere. If you abandon the urge to pimp out your Vim with a bi…
I usually stick to this rule almost everywhere, with just a few exceptions for some shortcuts.
Reconfiguring means trouble when, for instance, helping a colleague or teaching someone, as well as the overhead whenever the configs are lost.
Re: History and Effective Use of Vim
#219Earlier quoted context omitted.
It may seem that way, but no I've crossed that chasm long ago. I've debugged on production more than I would ever care to remember. But in all honesty it is easier than ever to stay completely off of production. It's also extremely cost effective. It's not simple and it is work, but it has never been easier to actually be successful at staying off if production.
Easier then ever maybe but still probably impossible to avoid. It's not that anyone wants to mess up with live, it's more like you don't have a choice.
Really? I haven't allowed people to log directly only a production environment in almost 10 years. There is definitely a choice.
Re: History and Effective Use of Vim
#220Earlier quoted context omitted.
wow good for them if they're getting people to pay $99. It does look well-designed, but the course outline seems a bit elementary. If anyone is thinking about buying this, you could probably just google the items in the course outline and try watching a youtube video on it.
Absolutely. The courseware runs entirely in the browser; gives great feedback; and helped me level up in a jiffy. Such that I have no qualms mentioning it here.
yeah, increasing your skill is easily worth $100. Back when I was employed as a developer, I bought all kinds of educational stuff. Now that I'm working on startups, everything's gotta be free.