Earlier quoted context omitted.
Yay, the original Holy War! (vi, for the record)
I'm pretty sure that vi hasn't been distributed for years. All the vi's in modern distros are just pointers to vim.
GitHub's new text editor leaked on Twitter
171–180 of 262 posts
Re: GitHub's new text editor leaked on Twitter
#172Is this a replacement for gist?
Re: GitHub's new text editor leaked on Twitter
#173Earlier quoted context omitted.
I always wonder why I learned emacs over vim. There is never support for it.
Because when you learn elisp, it runs circles around vim.
Re: GitHub's new text editor leaked on Twitter
#174Earlier quoted context omitted.
Yay, the original Holy War! (vi, for the record)
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
#175All of the competition can only be good for us developers. This, ST3, Light Table, Brackets, etc. Bring on the text editor wars!
Don't forget IDE family like http://c9.io/ Edit anywhere just with a browser is a win IMHO. Also easy pairing.
Re: GitHub's new text editor leaked on Twitter
#176holy cow this thing has like 70 repositories! And I found a screenshot... looks very much like sublime text: https://f.cloud.github.com/assets/1424/1228569/cce6eb26-27a6... edit: based on this[1], it looks like this is a GitHub-aware/integrated text editor that targets both desktop (Mac, at least) and web [1] https://gist.github.com/elcuervo/eb68883f233baf5a46c8
> it looks like this is a GitHub-aware/integrated text editor that targets both desktop (Mac, at least) and web I can confirm, from looking at the code. It uses CSS / LESS for highlighting, and CoffeeScript for client-side programming (eg, the fuzzy completion[0], or the autocompletion). The surprising part is that the editor doesn't seem to be a fork of either Ace or CodeMirror, the two big guys in the field. The hi…
The tmLanguage syntaxing, while limiting, is still pretty damn easy to create and edit, thus I approve. The idea that you have to learn a new way to build new syntaxes for every editor out there is a big issue for me as if you're going to be on the edge using new templating syntaxes, flavors of other languages etc. you just have to be able to fiddle with syntax highlighting, especially with new editors with poor/incomplete syntaxes and few user created syntaxes to fill the holes.
Re: GitHub's new text editor leaked on Twitter
#177Re: GitHub's new text editor leaked on Twitter
#178A text editor in a browser? There seems a lot of excitement about it but I can't work out why - can anyone explain? I'm not trying to be argumentative; I really am curious! It's for editing text and there appears to be massive excitement about it....?
Re: GitHub's new text editor leaked on Twitter
#179Never thought I'd be excited for a text editor, but damn I can't wait for this to come out.
If this thing delivers sublime-tier quality code editing in the browser and desktop AND commands a big enough community to allow for even more features (due to being open source), perhaps even IDE tier features... Sign me the fuck up. I'm tired of using closed source crap, patiently waiting for the dev to get off his ass and build more API functionality.
Re: GitHub's new text editor leaked on Twitter
#180Earlier quoted context omitted.
I love the edit markers in the last screenshot. But too skeptical about the performance of a text editor running in webkit. All of my experiences writing text online have been bad. So the jump into using webkit for an entire dev environment fills me with dread.
Have you used LightTable? It's quite fast as the editor. I'm sure Atom is similarly fast. It doesn't run in the browser; it just uses WebKit as the engine.