4 ms·
This is wonderful, and as a side effect clearly shows that emacs is much better than vim.
by xrd 12y ago
This is wonderful, and as a side effect clearly shows that emacs is much better than vim.
- enneff 12y agoWell, it was Brad's machine, so my vim environment wasn't set up as it is normally. Not really a fair comparison. :-)
- xrd 12y agoCan I modify my comment to say that this presentation changed my mind about Vim because it shows it can coexist with Emacs?
- percept 12y agoOh, I thought it looked a little plain. ;)
- vhost- 12y agoPhew! I thought Acme had ruined you and you were all about that no-syntax highlighting. What did you use to switch between emacs and vim? It seemed like a quick hot-key.
- enneff 12y agoWe were using a shared screen session (you can re-attach to a session with the -x flag), and we had the same files open in both vim and emacs. I was recording my laptop screen and would switch back and forth between my Vim session and Brad's Emacs session. It worked surprisingly well.
- mseepgood 12y ago> and you were all about that no-syntax highlighting He is. He usually does not use syntax highlighting: https://twitter.com/enneff/status/571067872291594240 https://twitter.com/enneff/status/571067872291594240
- rxaxm 12y agobrad has a fairly light-weight go setup for emacs. from what i can tell, he just has gofmt run on save and the go import plugin that reads his code and adds/removes import statements appropriately. mine includes auto-complete (that is conscious of the AST) and linting/error checking. i suspect brad has jump-to-definition and the other stuff that comes with the go emacs mode, but he doesn't use it.