Can anyone tell me why vim is better than emacs? I've been happily using emacs for a few years but would switch if vim is really better.
Vico Editor (Mac text editor)
61–70 of 141 posts
Re: Vico Editor (Mac text editor)
#62Earlier quoted context omitted.
If you are capable of switching editors, what does it matter if it's closed source or not? This adversity to switching editors is a common trait in programmers I can't quite understand. We programmers learn new things all the time, it's part of what makes us excel in our profession. And yet, adopting a new editor is apparently extremely hard.
Because learning new editors takes away from time we could be coding.
Learning new tools to use, new techniques to employ, new languages to express yourself, new environments to deploy in, new projects to hack on ... and for devops, new daemons to configure, new setups to benchmark ... these are the vast majority of a working programmer's time so switching editors is trivial in comparison.
Arguing against something because it takes away coding time is a sign that you probably need to broaden your experience.
Re: Vico Editor (Mac text editor)
#63Good start !
It seems a bit heavier than MacVim (bigger memory footprint), but the simplicity of configuration and the textmate bundles will surely make it very nice for users coming from mainstream text editors.
Focusing on a clear and usable OS X experience is definitely the way to go.
Re: Vico Editor (Mac text editor)
#64This is _exactly_ what I'm looking for. I've been using MacVim and Janus with good results, but this has so much promise.
Looks like Visual Block Mode isn't yet supported... did anybody find this?
Re: Vico Editor (Mac text editor)
#65I've been searching for this for a long time. If you opensource this, I will become an active contributor.
Something things:
Padding on the left file pane would be nice. http://cl.ly/3m223V172r3R3b1B1P1A
Also, with the left pane, some way to navigate between files like NERDTree allows would be useful.
vi' and similar should be supported. It means visual select inside quotes.
If you use command-w to kill the last open tab, so that nothing is open, you can't use the command-line ':', which is useful when changing directories to work on another project
Again, I love this project
Re: Vico Editor (Mac text editor)
#66Earlier quoted context omitted.
I don't want to take anything away from Vico (because so far it is pretty rad), but if you stick with MacVim you eventually start using TextMate less and less until you just stop altogether. For me, it took a good 3 months or so. The last holdout was using TextMate for formatting JSON output, but I found a Chrome plugin for that.
I love MacVim too, and have dropped Textmate completely. The only thing that I don't like about MacVim is that scrolling through text (vertically and especially horizontally) feels choppy compared to Textmate. When I see someone else scrolling through code in Textmate, it looks unbelievably smooth and fluid compared to what I'm used to in MacVim.
That's because scrolling with the mouse was a bit of an afterthough, I think. If you use motions, word objects and Ctrl+f/Ctrl+b you don't really notice this choppiness.
Re: Vico Editor (Mac text editor)
#67I really want to try out vim and tiling wm setup. Is this a good place to get my feet wet? I was going to just set up VM of ArchLinux.
vim works on mac anyway - macvim for gvim equivalent. As far as I know there aren't any decent tiling wms for mac.
There are quite a few nice tiling utilities for Mac :)
http://www.irradiatedsoftware.com/cinch/ (for mouse)
http://www.irradiatedsoftware.com/sizeup/ (for keyboard)
http://mizage.com/divvy/ (the one I use)
Re: Vico Editor (Mac text editor)
#68Earlier quoted context omitted.
My editor has been opened for 2-3 weeks now so I just keep piling the files from all the different projects. I prefer typing 'C-x b [strat]' to opening '~/dev/projects/something_else/lib/strategy.rb' but it might just be the way I'm used to working.
Leaving emacs open makes it more IDE like, the stuff you were working on last is still loaded. Instead of having to quit and then find all those files again. I work the same way as you. Tabs for any large number of buffers would be a nightmare
I work with both tabs, and buffers in vim. Best of both worlds. Switching to another tab quickly is easy, and opening up files becomes even easier with NerdTree (never did like Command + T). I also have BufferExplorer that allows me to switch buffers easily, but I tend to just use NerdTree anyway.
But I agree with you, I hate quitting vim, it seems like I lose my place much easier when I no longer have those files open.
Re: Vico Editor (Mac text editor)
#69Earlier quoted context omitted.
Personally, I tend to think that an overly dogmatic commitment to backwards compatibility does more harm than the benefit produced by supporting a tiny minority of users with five year old hardware. Backward compatibility is the enemy of elegance. Just look at C++ or the x86 instruction set to see examples of that.
I do agree to some extent. On the other hand, I've been using Apple hardware off-and-on again since the MC68030; I already went through this with the 68k->PPC transition, then again with the introduction of the PPC750 series processors, then again with the PPC->Intel transition. At this point, I fully expect that if I were to buy an Intel series Apple system in the next couple of years, shortly afterward Apple would…
It's understandable that you wouldn't want to buy a new Mac just before they do a hardware refresh or something, but come on. At some point you need a new computer. Somehow I doubt that Apple is going to do some kind of crazy Intel -> Atom transition anytime soon, and even if they do they'll support Intel for at least a few years.
You sound like my friend who won't upgrade to an HDTV "because the price keeps dropping." :D
Re: Vico Editor (Mac text editor)
#70I look forward to the SFTP feature, a zone where Vim isn't confortable.