vim is already too slow (i typically code edit with elvis which is good but not for huge text data files). evil's lagginness is utterly maddenning. and emacs isn't typically installed everywhere. i'm a multi terminal user who typically works remotely via ssh, remote usually being over a gigabit connection. I can probably burst 120+ wpm and yeah watching other people code is typically very painful. And I don't use plugins, thats what a posix shell is for.
From Vim to Emacs
81–90 of 123 posts
Re: From Vim to Emacs
#82If anybody would ask me "should I learn emacs or vi?"
My answer is "lern vi!"
Re: From Vim to Emacs
#83I began using Vim about a month ago and it has been totally revelatory to me, and believe quite honestly that it was the best career decision I've ever made. The one thing, however, is its speed. MacVim gets very slow sometimes, particularly with buffers. So my question: How does Emacs and Vim compare speed-wise? I come from a Sublime Text background and really miss the ability to quickly navigate between tabs (buffe…
> it was the best career decision I've ever made I hear this a lot, and I'm not debating whether it's true or not since ymmv. I'm curious if anyone here has gone the other way. I used vi in my teens then switched to emacs, which I used for over a decade. A couple years ago I switched to JetBrains IDEs and have never been happier. I hadn't used an IDE since Borland Turbo C, and forgot what I was missing. Are there any…
Are there any other former vi/emacs users (like, hardcore - I used to browse the web in emacs) who ditched it for an IDE?
Whenever I have to use Visual Studio, the VsVim extension gives me the best of both worlds.
Re: From Vim to Emacs
#84The "problem" with vi is that you'll outgrow it very fast. People tend to work around this by installing a dozen of plugins but I think you should use Emacs for that. I'm quite proficient in both editors and while I resort to Emacs for 95% of my coding (and mail, and notes, and agenda, and...) sometimes nothing beats the simplicity of firing up vi for a quick edit in a remote server. Using vanilla vi with a minimal t…
Huh? vi does not have any plugins; only vim. vi is even more bare-bones than vim, lacking a lot of features (macro recording and text objects being the ones I miss). It is extremely common to find vi pre-installed on countless servers, however, making it extremely convenient if you're an expert with it.
What's amusing to me is how many people don't know vi very well and use plugins in vim that vi can handle as well or better through macros, ex scripts or external commands.
Re: From Vim to Emacs
#85I always have a hard time figuring out why people would switch from one tool to another just to start configuring the other to behave like the original tool. Can someone name some reasons to switch from vim to a vim-like configured Emacs?
The reason I've seen mentioned by the author is to learn the other tool, in this case Emacs. But for that I think the smarter way would be to learn to use Emacs like Emacs users do it. There's a reason why things are implemented differently, right?
Re: From Vim to Emacs
#86Earlier quoted context omitted.
> it was the best career decision I've ever made I hear this a lot, and I'm not debating whether it's true or not since ymmv. I'm curious if anyone here has gone the other way. I used vi in my teens then switched to emacs, which I used for over a decade. A couple years ago I switched to JetBrains IDEs and have never been happier. I hadn't used an IDE since Borland Turbo C, and forgot what I was missing. Are there any…
Old (old) school vi user here. When I was working at a .net shop, VS became my vim (mostly because it was already always running), also because it was incredibly familiar. Since leaving the .net world though, I've relapsed. Have had trouble with eclipse|intelli-j|etc due to their general java slugishness on the mac.
Nice, I looooove old school vi. O'Reilly's book on vi: Mastering the vi editor: 6th edition is my bible. I wish there were other sources of information and tips for vi. I really want to know what sort of workflows other people have.
Re: From Vim to Emacs
#87The "problem" with vi is that you'll outgrow it very fast. People tend to work around this by installing a dozen of plugins but I think you should use Emacs for that. I'm quite proficient in both editors and while I resort to Emacs for 95% of my coding (and mail, and notes, and agenda, and...) sometimes nothing beats the simplicity of firing up vi for a quick edit in a remote server. Using vanilla vi with a minimal t…
Huh? vi does not have any plugins; only vim. vi is even more bare-bones than vim, lacking a lot of features (macro recording and text objects being the ones I miss). It is extremely common to find vi pre-installed on countless servers, however, making it extremely convenient if you're an expert with it. What's amusing to me is how many people don't know vi very well and use plugins in vim that vi can handle as well o…
This bothers me. People should just call it vim when they mean vim. I suspect most people here haven't actually touched Joy's vi or its closest derivative, nvi.
I don't know where this practice comes from but it feels exactly the same as when people say Unix when they are very obviously talking about GNU/Linux.
Re: From Vim to Emacs
#88I always have a hard time figuring out why people would switch from one tool to another just to start configuring the other to behave like the original tool. Can someone name some reasons to switch from vim to a vim-like configured Emacs? The reason I've seen mentioned by the author is to learn the other tool, in this case Emacs. But for that I think the smarter way would be to learn to use Emacs like Emacs users do…
Emacs isn't superior to Vim in every possible way. I personally find Vim's modal editing hard to let go of. On the other hand, vimscript is an atrocity compared to Elisp. Vimmers have certainly managed to make some amazing extensions to the editor despite that fact, but no tool is perfect; the whole point of an extension layer is to make the tool work the way you want. The defaults aren't necessarily what everyone likes (or ought to like).
Re: From Vim to Emacs
#89I'm vim guy and I started to watch http://emacsrocks.com/
There are another similar sites?
Re: From Vim to Emacs
#90I love seeing this on the front page. I've been a Vim user for a few years and feel like there isn't a ton of help out there for switching to emacs + evil.
I should probably write a blog or something about this since I've spent quite of time getting Emacs to behaving like Vim with Evil. I went the Prelude route, because it included a lot of cool things out of the box and I felt like I could just customize it a bit. My main goal was to get an Emacs environment that behaved like Vim for working through the SICP using the Geiser plugin. There's surprisingly little that has to be customized to get a well-behaved Emacs.
Here is my prelude customizations:
https://github.com/humana/dotfiles/blob/master/emacs/persona...