4 ms·
When I was talking about discoverability I meant assuming you don’t know all the exact command names and what they do. I thought you neeeded to know the exact c
by eradicatethots 9y ago
When I was talking about discoverability I meant assuming you don’t know all the exact command names and what they do. I thought you neeeded to know the exact command name to use :help, so I’m not seeing how that’s an answer here.
Also, yes the mouse can be slow for some purposes, but if you’re not in a typing frenzy it’s probably easier to be in mouse mode which is something like reading mode. Scrolling is much easier for me outside of vim than inside of vim. Also I considered that this is maybe a better match to my workflow, which is often more readingand thinking than actual keyboard input. So it’s ok for keyboard input to be less prioritized. For this workflow having inline documentation, intellisense and compiler errors as you type is fundamental.
Also I doubt I ran into the beginner traps. I used it pretty seriously and exclusively for a year or two and am still proficient at navigating. I even got into using macros like other commenters mentioned, and learned all the different edit mode shortcuts (cxsSDCiaAOo). Seriously editing in vim is really really fast. Although maybe there are traps for people that I don’t already know about, and you could fill me in on those.
- nextlevelwizard 9y agoI'm getting tired of this back and forth, same already solved issues are being rehased, I just have this last note >Scrolling is much easier for me outside of vim than inside of vim. you might want to try `set mouse=a`