61–70 of 85 posts
I hate those YouTube videos "turn vim into an IDE". The people who watch those only care about bragging that they use vim, nothing else.
No?
Some people want to know how to get IDE features such as errors, goto definition and type inlay hints into their editor of choice.
It's frankly hilarious to think that "it's only for bragging rights". It says more about you than anyone else.
I hate those YouTube videos "turn vim into an IDE". The people who watch those only care about bragging that they use vim, nothing else.
> The people who watch those only care about bragging that they use vim, nothing else. No? Some people want to know how to get IDE features such as errors, goto definition and type inlay hints into their editor of choice. It's frankly hilarious to think that "it's only for bragging rights". It says more about you than anyone else.
And I think the people who watch these would be better off using a regular IDE. The only reason someone would watch that is so they can haphazardly configure vim to mimic their existing workflow. I don't know. Maybe I'm being too judgemental.
What is the consensus on productivity with Vim? I have thought about trying out the keyboard only approach, but haven't wanted to invest time in it yet. When I see people on YouTube using Vim it slightly feels like there's a whole lot of keypresses happening, but not a lot is actually gained compared to using a mouse or even frequently it seems it takes a while to do something that is much quicker with the mouse. I u…
Very simply, for me, keeping my hands on the keyboard feels right and means less movement overall. If I’m typing and want to correct something two words back, say “how rae you?” I can either - grab my mouse and click where I want the cursor, fix the typo, and then click back to where I was (or hit End, or was it Ctrl+Right? Opt+End?) - type Faa ar $ Ok, that’s a lot of weird keystrokes, but in my brain my hands just…
2 + 2 + 2 + 2 = 8 keystrokes. It also works in every single text input on macOS
Your solution is 1+3+1+1+2+1+1 = 10 keystrokes and only works inside vim.
I do kinda get the feeling you get when you can transfer your thoughts to screen as efficiently as possible.
But really, if your typing speed is the only thing holding you back when coding, it's a bit suspicious to me.
What is the consensus on productivity with Vim? I have thought about trying out the keyboard only approach, but haven't wanted to invest time in it yet. When I see people on YouTube using Vim it slightly feels like there's a whole lot of keypresses happening, but not a lot is actually gained compared to using a mouse or even frequently it seems it takes a while to do something that is much quicker with the mouse. I u…
In my experience non-vim people are neither more or less productive than vim people. Pick your poison. Productivity comes down to so much more than typing/navigating/yanking fast. Especially when it comes to programming, which is 95% thinking, 4% swearing internally and 1% typing.
> if you think it's everywhere One of the counterpoint is vim not being available on Windows. But It is. Not by default, but most critical stuff aren't there by default anyway and vim will be one of the easiest block to have ready. Then Windows comes with WSL, where I think most people who even care in passing about vim will spend their time, so we're back to the editor they'd use on Linux anyway. That was to me the…
The "everywhere" argument is exactly about the defaults, otherwise there's no benefit, most alternatives are available via an install
Vim is either already installed or at one click/one command away almost whatever the system you use, that's the closest we'll ever have from "everywhere" in this day and age IMHO.
I'm a big fan of Vim, but I hardly use it as my primary editor anymore (applies for Neovim as well). I think the ecosystem is amazing, but I hardly have the patience to set things up to feature parity with other editors. Debuggers are the biggest missing/hard to configure feature. I do, however, use Vim bindings in every editor that supports them (and extensions for browsers like Vimium). The extensions/Editor functi…
Do you know about :termdebug and what are you missing with it? It's just dbg hooked into vim, and you can use any other compatible debugger instead if you prefer, for example rr.
That's the beauty of vim, the tools you use are the tools you'd use in your terminal anyway.
Earlier quoted context omitted.
Very simply, for me, keeping my hands on the keyboard feels right and means less movement overall. If I’m typing and want to correct something two words back, say “how rae you?” I can either - grab my mouse and click where I want the cursor, fix the typo, and then click back to where I was (or hit End, or was it Ctrl+Right? Opt+End?) - type Faa ar $ Ok, that’s a lot of weird keystrokes, but in my brain my hands just…
option-left arrow twice, delete 2 times, type 'ar' and cmd-right arrow to get where you are. 2 + 2 + 2 + 2 = 8 keystrokes. It also works in every single text input on macOS Your solution is 1+3+1+1+2+1+1 = 10 keystrokes and only works inside vim.
And every other tool that supports it. I use it everywhere, window manager, terminal and every terminal program I use (via readline), my browser, and the list goes on. I rarely have to reach for my mouse, if I do it's frustrating and breaks my flow and I will fix it next time I have a few minutes to spare. I even have a shell script to move the cursor out of the way.
Earlier quoted context omitted.
option-left arrow twice, delete 2 times, type 'ar' and cmd-right arrow to get where you are. 2 + 2 + 2 + 2 = 8 keystrokes. It also works in every single text input on macOS Your solution is 1+3+1+1+2+1+1 = 10 keystrokes and only works inside vim.
> 10 keystrokes and only works inside vim And every other tool that supports it. I use it everywhere, window manager, terminal and every terminal program I use (via readline), my browser, and the list goes on. I rarely have to reach for my mouse, if I do it's frustrating and breaks my flow and I will fix it next time I have a few minutes to spare. I even have a shell script to move the cursor out of the way.
My method is the default working method for every single piece of software.
How many 10+ year veterans of the software industry are actually only limited by their typing speed and need to maximise it with vim? I do kinda get the feeling you get when you can transfer your thoughts to screen as efficiently as possible. But really, if your typing speed is the only thing holding you back when coding, it's a bit suspicious to me.
For example, make a key binding that moves between only functions that have a particular signature. Or a shortcut that takes heap snapshots, filters and format the output to your liking, and have it displayed alongside the source file with the suspected memory leak your hunting.
Otherwise no I still can’t get used to using j and k to move up and down even after a decade of vim.