I was not happy with everything, I got some bugs which is ok, I reported and I tried to fix them but I had to learn one more language (elisp) to be able to do that. It took me like a month to understand everything and to work well. It was easier to do things because it has a real-time display of available key bindings, so while you type you can see your options, also it is mnemonic so if you want layouts you'd use SPC + l, if want to toggle something you'd use SPC + t, if you want buffers you'd use SPC + b, for projects SPC + p, for files SPC + f and to save a file you'd combine commands like SPC + fs which means spacemacs -> file -> save and SPC + pt to see the project tree of files. Spacemacs has vim key bindings so I was at home, I just needed to learn to handle different aspects of spacemacs like layouts and workspaces.
I tried to start from scratch writing down every config as I did with vim, but it was too much to learn and I had to get some work done so I tried spacemacs and with some help I could be productive in no time. I got other frustrating problems like that one and I see myself spending too much time debugging or trying alternative plugins, so I was tented to try something different and this is where emacs came to my attention.Įmacs has a GUI app which makes me don't need terminator or iTerm anymore and it has his own shell written in elist called eshell, so I'd have one config and plugins for everything. Not everything worked well between plugins too, for example I had auto completation on nvim and it works well unless I'm using multiple cursors which is a feature from another plugin, the auto completation would work only for the first cursor because they didn't integrated with each other. Then I see myself managing configs and plugins for nvim, tmux, zsh to run well on terminator on my Debian at work and iTerm on macOS at home. I used this stack for 3 years and I was happy. I don't use nvim anymore, but you can still find my configuration for vim and tmux. Since I was using nvim in the terminal it worked very well and I even found some plugins to integrate them smoothly. But I still don't like that.Īt that time people was talking about tmux which is a terminal multiplexer so you could split your terminal and have tabs and customize everything from shortcuts to how tmux looks like for example adding useful info to your status bar. UPDATE: I agree that my survey is too shallow. Ok, I didn't liked that, so I changed to neovim which gives credit for people when they contribute. Wait what? Only one contributor on the vim repository? How only one person could have done that? Checking the pull request list I saw that the author applies changes from other people as it was his changes. One day I heard about neovim, not sure exactly why I switched to it, but take a look on the github project for both projects: Finally I was happy and productive using vim.
#Vscode vs atom for mac code#
For the most of the time, we're editing files and moving between lines of code so that makes sense. I used vim for a few months and what I like about vim the most is that it's optimized for editing files not creating new ones.
#Vscode vs atom for mac how to#
It was not cool, it was too hard to learn how to use it, to load new config files I had to restart vim every time and so much other problems, but since they did, I convinced myself that I could learn it too so I did. The vim users worked on projects more closed to my own project so I started to check how they did things and then I started learning about vim. I used it for a few years at work too until the day I joined a company that had vim and emacs users. Also, it was fast and I had a few plugins installed to handle php, html, javascript and css. I used sublime text because I was learning with blog posts and videos and most of the content mentioned sublime text.
I started learning about programming when I was in high school, it was so much fun to write some code and see the results on the browser. I will talk about my experience using each of those text editors, maybe it could be useful for someone evaluating text editors to invest time learning.
0 kommentar(er)
