News for hackers. Stuff that matters.
Re:GitHub's new text editor leaked on Twitter by baby on Wednesday February 26, 2014 @04:06AM (#7303783)
I always wonder why I learned emacs over vim. There is never support for it.
Re:GitHub's new text editor leaked on Twitter by jaredmcateer on Wednesday February 26, 2014 @07:18AM (#7304446)
Don't feel bad, there's nothing worse (for editing) than using a half baked version of vim in another editor. The best of implementations will leave you with an uncanny valley feeling of disgust. I'd rather use a non-modal editor, all or nothing.
Re:GitHub's new text editor leaked on Twitter by DennisP on Wednesday February 26, 2014 @03:22PM (#7307402)
Funny, I'm just the opposite. I'd rather have the basics than nothing.

Mostly I've used VsVim and Viemu. They're both pretty decent. (Viemu is better though, it's got everything I normally use except for :norm. VsVim is missing column mode and the vap doesn't work.)

Re:GitHub's new text editor leaked on Twitter by jaredmcateer on Thursday February 27, 2014 @10:36AM (#7312694)
I've built a suite of useful shortcuts that only work with my vimrc, which isn't a problem since installing my config from my github repo is a 3 step process, but when I'm running in some "vim-mode" editor I find myself tripping up on not having these things that I've committed to muscle memory and it ends up killing my productivity. At least if I know the editor is always in insert mode I can adjust with the occasional :w here.
Re:GitHub's new text editor leaked on Twitter by DennisP on Thursday February 27, 2014 @11:24AM (#7313006)
I could see that being annoying. VsVim and Viemu both support a vimrc.
Re:GitHub's new text editor leaked on Twitter by davidw on Wednesday February 26, 2014 @04:18AM (#7303817)
Because when you learn elisp, it runs circles around vim.
Re:GitHub's new text editor leaked on Twitter by admnor on Wednesday February 26, 2014 @04:29AM (#7303853)
Yay, the original Holy War!

(vi, for the record)

Re:GitHub's new text editor leaked on Twitter by masukomi on Wednesday February 26, 2014 @07:42AM (#7304561)
I'm pretty sure that vi hasn't been distributed for years. All the vi's in modern distros are just pointers to vim.
Re:GitHub's new text editor leaked on Twitter by omaranto on Wednesday February 26, 2014 @08:49AM (#7304833)
That's probably not true, in that among the myriad distros there's probably one in which vi is nvi.
Re:GitHub's new text editor leaked on Twitter by markeganfuller on Wednesday February 26, 2014 @08:45AM (#7304813)
vi is still included in the arch linux base system
Re:GitHub's new text editor leaked on Twitter by crashandburn4 on Wednesday February 26, 2014 @08:46AM (#7304817)
true, but that's why we have evil mode[1], so we can have our elisp cake and eat our delicous sugary vim bindings too.

[1] https://gitorious.org/evil/pages/Home

Re:GitHub's new text editor leaked on Twitter by avendael on Friday February 28, 2014 @12:18AM (#7317370)
You can try this out https://atom.io/packages/atomic-emacs. It's not yet complete, and I'm still working on it, but I think it's a start. Feature requests are welcome :)
Re:GitHub's new text editor leaked on Twitter by jbeja on Wednesday February 26, 2014 @09:18AM (#7305008)
You could always use emacs evil-pluging.
Re:GitHub's new text editor leaked on Twitter by Flenser on Thursday February 27, 2014 @10:02AM (#7312507)
Re:GitHub's new text editor leaked on Twitter by rayiner on Wednesday February 26, 2014 @02:44PM (#7307140)
I learned Emacs because there was nothing that supported Common Lisp editing the way Emacs did.
Re:GitHub's new text editor leaked on Twitter by duaneb on Wednesday February 26, 2014 @07:28AM (#7304491)
Unless you use a Mac!