231–240 of 265 posts
:set nu / whatever you want to find [return] i *edit stuff and use arrow keys for nav* :wq Or :q to quit without saving That’s all the vim most people need. The fact that less is installed on many more systems than nano is a testament to the bad assumptions too many devs make about who will be using these systems in the future. And yes, it’s not hard to "apt -y install nano" except at work where we have proxies and i…
Absolutely haram
Earlier quoted context omitted.
That's somewhat comforting to know. I'm in the beginning stages of building out a keyboard-heavy application, and I keep wondering about how to support different keyboard types. I suppose it's not possible to satisfy all customers if even Vim can't do it.
Just support QWERTY but allow the user to remap everything. Even among programmers, the share of people that use alt layouts is so small that is not worth your time.
I have done that briefly years ago but I find it a dead end.
After a while you just get used to the cursor keys being in a different place and if you’re touch typing it doesn’t mater much.
Also what you loose to cursor key placement you gain back on other navigation.
So in short just support qwerty and it’ll be fine.
My pet peeve is Vim tutorials that start with "use hjkl to move around" instead of "use `set mouse=a` to turn on the mouse." In my opinion you need to make sure that you are very clearly disclaiming that you are teaching a harder way of doing things in exchange for incredibly small productivity gains that will be realized years in the future, if ever. (This is basically a copy-paste of previous comments I’ve made, I…
a harder way of doing things initially in exchange for incredibly small productivity gains that when applied millions of times over the course of a programming career, make a monumental difference A key ethos of Vim is that once you climb the initial learning curve, you're on a path of increased efficiency for the long haul. Moving the hand to the mouse, dragging the cursor to the spot you want, then moving the hand…
I’ve been using Vim as my primary editor for 25 years and at this point the keyboard nav is burnt into me.
I still use two finger scrolling on my track pad though. If I’ve been in another window I might also start the cursor at a point with trackpad.
It works fine over ssh too.
I think most newbies that care enough to try Vim know there is a Vim Way. They know about Vim Golf.
That get tiring all the time when you’re starting out. Sometimes they just want to get the job done until they learn, I’m ok with that. Just have a go.
It’s absolutely fine to make use of all the features Vim provides and use it any way you want because you’re always going to me slowly learning more.
I once tried to migrate from VS Code to Neovim. I use TypeScript at work, and use many languages for my side projects. But the worst part was making Vim provide with things that you'd expect programming editors to have. So many options, what's best is up to opinion, integrating language servers, getting intellisense to work as you would expect, searching the project folder for file names. Then I realized that all I'm…
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.
It’s been a few years since I last tried so hopefully this has improved. I tried the vim plugin for Jetbrains and found it lacked window navigation and support for things like registers that I use a lot in vim.
At the time I was using webstorm (at a client’s insistence) and found that for the weird JS project we were working on Tern.js was actually better at refactoring and navigating anyway so I just went back to using it with Vim.
Earlier quoted context omitted.
Okay, but you spend 2000 hours per year at work. So 10 hours on a config is only .5%, which is the productivity gain you need to realise to get that time back in one year (assuming you also spend 0 hours on fighting vscode). Unless you're retiring within the year, that calculus doesn't make sense. The productivity boost you get with from Emacs/vim is huge once you learn it well. I strongly believe that learning one o…
I've been coding for nearly 40 years and I just don't see any correlation between editor usage and developer productivity. Being able to design and work with complex software systems is what makes a senior dev productive, not which keys they hit to copy and paste.
What the vim movements do is allow you to focus on your code without interruption. You can do everything without shifting your focus from the block of code you're currently editing. It's hard to describe until you've experienced it. I think it's just easier to get into and maintain a flow when the editor gets out of your way.
Our experiences differ with regards to the correlation. In my career I've seen a massive discrepancy between effectiveness of editor use and developer impact. Off the top of my head, save for one person (who used Sublime), every outstanding engineer I've worked with have either used vim or emacs.
Earlier quoted context omitted.
I’m a power Vim user. I do not recommend it for code editing. Learn it as a curiosity if you want. It’s also handy for quickly editing over SSH. IDEs with multiple cursors are so much nicer than Vim.
This is odd to hear because the general consensus online is that vim/vim motions makes for seamless text editing. I also feel like multiple cursors is an antipattern, you don't need multiple cursors in vim. You need a macro, which is easy to make and you can pass this to a buffer to modify it or apply it to certain lines or the entire file.
Macros are more flexible but visual block works well in a lot of situations.
Either way if one was really tied to multiple cursors Vim and NeoVim of course have plugins that support it. I don’t bother with them myself.
:set nu / whatever you want to find [return] i *edit stuff and use arrow keys for nav* :wq Or :q to quit without saving That’s all the vim most people need. The fact that less is installed on many more systems than nano is a testament to the bad assumptions too many devs make about who will be using these systems in the future. And yes, it’s not hard to "apt -y install nano" except at work where we have proxies and i…
now I need to use vim to reconfigure apt sources just so I can use a more normal editor Prepare and paste this into your terminal: echo "another line" | sudo tee -a /etc/apt/sources.list Sorry for your pain, but choosing hard ways is a person’s business.
I see that there's a pretty big miss in the syllabus: surround! yes, true, it's not "official" but rather a plugin, but you can't really do without it, can you?
In addition to surround, what other plugins do you think beginners should almost always use?
Earlier quoted context omitted.
now I need to use vim to reconfigure apt sources just so I can use a more normal editor Prepare and paste this into your terminal: echo "another line" | sudo tee -a /etc/apt/sources.list Sorry for your pain, but choosing hard ways is a person’s business.
or just "echo 'another line' >> /etc/apt/sources.list"