![]() ![]() Otherwise, the Esc at upper left corner is high risk for Repetitive Strain Injury. If you go with evil, i highly recommend setting Esc to somewhere near your thumb, or the capslock key. I recommend evil/spacemacs, ergoemacs-mode, or try my own xah-fly-keys. My own opinion is never use default emacs keys, whatever you do. (be warned that MS's wireless keyboards are password leaking) ergodox, kinesis, keyboardio, Microsoft natural. If you really want to stick with emacs default, I'd recommend you get a good keyboard with nice thumb keys so you can hold down as control. (there's a package keyfreq.el on MELPA that can log and report your own command/key usage.)Įmacs default is pretty bad, I think you'll find many blogs in agreement on this today. And modal saves you 1 or 2 keys per command, but deduct the switching mode problem, I estimate that if all things are equal it saves you 10% key strokes. This is because from my statistics, more than 50% of programer's key strokes are spend on editing commands, not typing letters for insertion. Vim is scientifically more efficient, from my studies. They're not impossible to memorize, and if you bind Caps Lock to Control and Esc, you won't have to worry about Emacs Pinky. So you will need to be familiar with at least basic Emacs navigation.Įmacs bindings aren't a language like Vim's bindings are, but they do have a logical structure sometimes. Sometimes Vim keybindings clash in certain modes, for example Magit or Gnus. I still record Vim-style macros, because that's worked well enough up until now. I don't even have line numbers on-which is something I would have never gone without in Vim. why press ESCi when I can just do a two-letter chord and be done with it? I stopped using G to move to other lines, and switched to Avy. I don't use evil-leader, I bind chords (usually ⌘-) or write hydras. For example, $ is uncomfortable, so I use C-e. Up your coding within your preferred editor.I switched from Vim to Emacs, and use Evil. IDEs do have their uses, but editors can be faster under the fingers andĮasier to run on slower machines exuberant-ctags is useful to speed Tag names, try Ctrl-P (this will also autocomplete other words in the file), Plugin, which will give you a tag overview side panel. Round through tag definitions if there’s more than one of them.įor Vim, you can also try the taglist.vim The tag under the cursor), and M-* to return. Tagname), and use :ta tagname to jump to a tagname, or Ctrl-] to jump Use the tags in Vim once they’ve been generated, fire up one of your sourceįiles in Vim (or use vim -t tagname to start at a particular Your tags are stored in either a TAGS (Emacs) or tags (Vim) file. Type ctags -list-languages for a list of supported languages. To generate Emacs-compatible tagfiles, use: ctags -e -R ![]() (for vi(m)) and etags (for Emacs) is that it has a recurse option: ctags -R The major advantage of exuberant-ctags over the older versions of ctags Tip of the Trade: With exuberant-ctags you can take advantage of any IDE’s source code navigation features - without ever leaving the comfort zone of Emacs or Vim. Package offers some of the source code navigation features of an IDE within Preference for an editor you already know. IDEs can be useful when you’re coding however, you may, like me, have a ![]()
0 Comments
Leave a Reply. |