![]() Vim's `.` to repeat the last action is really powerful and can save you a ton of time for small ad-hoc edit repetitions that don't warrant doing a full macro with `q`. I then press `j.` a bunch more times (which is really easy to do rapidly with your index and ring finger on Qwerty) and in 2 seconds I'm done. In Vim I'd press `j` to get to the first entry, then `A,` to append the `,` after the first one, then `j.` to move down and repeat the action. Or suppose I'm looking at this and want to add a `,` character to the end of each of the type entries, because I forgot Python likes its commas: If I tried to do this editing with arrow keys and backspaces I'd need 12 down keystrokes just to get to the right line. I could also do `/[` which is only four keystrokes, but a little more awkward to reach. If I've just used a fancy shortcut key to jump to this function, my cursor is probably on the function name. Warn("could not parse hgignore pattern '%s'" % line) Return lambda s: arch(s if s.startswith('./') else s) # Mercurial globs also have to match to the end of the pattern. ![]() # Mercurial ignore globs are quasi-rooted at directory boundaries or the You're talking about how it's easy to move to a function or a file, and then you're "ready to edit", but edanm is talking about actually doing the editing.įor example: say I jump to this function and want to fix a bug (the `search` should strip off the first two characters here, not just one). If I could do it the other way around, I would - I'd love to be able to use vim-like editing inside of an IDE, but every vim-mode I've tried so far just doesn't work properly (except one - evil mode in Emacs - which is why I recently switched to Spacemacs, but that's another story). Unfortunately, because vim sucks at everything else, my setup has to be complex to actually get it to do the other things a good IDE does out of the box. (not that extreme, but that's what it feels like). If you don't know vim, then it's hard to understand how slow editing text feels without it - it's kind of like going from not knowing how to type properly to being a solid touch typer. I'm talking the pure "move the cursor to a certain place and enter some text" aspect of it. I'm not talking about variable lookups / etc. The problem is, once you learn to use vim's text editing capabilities, then editing code using anything else feels like a pain. Unfortunately, vim is terrible at basically everything else. Vim is a better text editor than anything else. I can tell you exactly how I feel about it: I mainly use vim and occasionally use Jetbrains.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |