![]() It is really easy to get a nice working environment while you use vim-style keybindings. ![]() However as soon as you start to work on larger projects and you start customizing neovim a lot then my advice is to checkout spacemacs. I would recommend you use neovim for learning vim keybindings as it is arguably easier to setup than vim, and arguably best fit to learn vim-style navigation. However, I guess if you are serious about prrogramming then learning vim-keybindings is worth the small investment. Using some editor that makes this simple will be the easiest for a beginner. It is simply because vim-style navigation is great! Furthermore, depending on which language you are learning first, for most scripting languages you do not need a full IDE as you will just write scripts and try them. I think there is a good reason that most IDE’s come with vim-bindings and that there even is an evil mode for emacs. So here follows some humble personal advice. Additionally I guess it is still worth to provide an updated answer for other people directed here. I still got directed here somehow, and I think this question is still very relevant today. If the concept of mixing Vim & emacs is interesting you might look into the spacemacs project.Īlthough this is a very old topic. If that doesn’t work I then go to vi which is the editor that Vim is built to improve. if nano isn’t available I try ee for easy edtior (a BSD staple). It’s about as no frills as it gets and is pretty approachable for most needs. The terminal editor I grab first if it’s a clean/new instal of *nix is nano. The benefit to both Vim & emacs is that they can be accessed via the terminal, so we go back to ubiquity. I recommend Prelude as a good entry point. It’s over sized and over powered but there are many good ways to gently on board yourself into the emacs lifestyle. It also does have a GUI version so you’re “stuck” in just a terminal window.Īs a matter of preference, I tend toward emacs. ![]() Vim is in just about every distribution of Linux and BSD. If you’re going to end up in a *nix or BSD environment, which as dev you probably will at some point, then a basic understanding of Vim is good. I second all votes for VS Code, if you “just want to get things done” and are more comfortable in a GUI. ![]() You should be willing to spend extra time learning vim/emacs and get annoyed often because getting anything done takes ages… until you get it :~) And I was already familiar with using the hjkl keys as movement keys, add another month or so if you are not. It took me about two months until I felt as productive as before, and another week to feel vastly limited by conventional arrow-keys text editing. Vim (and Emacs) have a learning curve similar to a brick wall. Vim’s scripting language is arguable not great, but it’s easier to understand what is going on in your. However, if you want to use emacs you should at least be able to read lisp, which is not an easy task for the uninitiated. I’ve heard of people who have migrated to emacs because of evil mode. It’s a monster and it even has an Evil Mode, which supposedly feels like vim. I’ve barely used emacs, but people jokingly call it an operating system :~). I recommend starting with vim because it concentrates on being a fantastic text editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |