Not that it is a bad experience or that Emacs can't pipe out to shell and do stuff. Maybe its just me, but the Emacs community felt a bit different and wanted everything inside Emacs. ![]() One main example for this is to sort in vim you select a region of text and call the sort unix function on that. With Vim the whole philosophy is to provide a good editing environment in Vim and hand over other things to other programs. Well, you ought to lose something right? It might not be a big deal to some but you kinda lose the whole unixy feel. Everybody loves and even people in Emacs community and we have similar to plugins to commentary, surround and others. ![]() I have not had any issues with the emulation but just saying almost everything to be on the safe side.Īnother thing you won't lose is Tim Pope's plugins. It emulates almost everything that Vim does. It is Vim emulation layer on top of Emacs and is really good. Well, you won't lose most of the core Vim stuff. The biggerst gain for me was the async nature of Emacs. Elisp feels more like a proper language and everybody plays nicely with each other. You can do that with Vimscript but nobody actually does that. In Emacs plugins work together rather than messing up the other one. Like inline images, different fon't sizes in a buffer etc.Īlso the whole community arround Emacs is different from that of Vim. You will learn to love elisp and its self documenting nature. I used to use Emacs just to use Magit even when I was a Vim use due to its ability to do chunked commits.Įlisp though more daunting at first is a much better and powerful language than Vimscript. One of the best plugins you will ever see is Magit and Emacs is home to it. I used to use tpope's commentary but I could not use that in Vue files and had to switch to NERD Commenter and do this to get the commenting working and still it was a slow and got the comment type wrong at times for some reason. You lack on good autocompletion and commenting. You have Vue plugin in Vim but its not that good. Vim has a really hard time dealing with templates. Now comes the biggest pain with using Vim was when I had to work with Vue. ![]() Emacs could do images inline and that was really something for me. Yeah we have gvim, macvim ect but those don't provide anything more than more colors. Now, another reason for switching from Vim is due to its lack of good gui support. This was once and issue when I had a big LaTeX file which I could not edit in Vim because it was too slow after adding the LaTeX plugin. Kudos to Sublime Text on handling that so well. The main issue with Vim was if I had any large file opened in Vim when I have a long lis of plugins( which I do ) I was having a really hard time getting anything done. We have ale and deoplete which are awesome but it lot of other things was messy in the plugin landscape. Yeah I know about Neovim and now with Vim 8 we have got async processing but its not on par with Emacs on that. It really got show when I had quite a bit of stuff going on. The one main issue I was facing with Vim was due to its synchronous nature of plugins. Well, Vim was a great tool for editing text, not for editing code. ![]() My emacs and neovim config What is the problem with Vim? # I was a fanatic Vim user for about two years and use to believe that Vim is the only text editor that was cool. How Emacs took over my Vim life meain/blog
0 Comments
Leave a Reply. |