161–170 of 262 posts
Earlier quoted context omitted.
Atom: http://i.imgur.com/0Qfwkp4.png SublimeText: http://i.imgur.com/frzYwwc.png Case in point.
They look similar. I'd like to be proven wrong and GitHub make Sublime a more maintained and transparent project, but it's doubtful.
Earlier 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.
This is already possible using gitgutter in both Vim and ST, and I've never noticed an impact on performance.
> Would the editor itself be open-source?
> yes
> a non-opensource editor from GitHub would be ludicrous
> seems like the source code will be up today
Earlier quoted context omitted.
Why not just use Vim?
Vim does not support graphical user elements, and is built around the unfamiliar language Vimscript. Those drawbacks are pretty baked into Vim and would be hard to change (though someone is trying to: https://www.bountysource.com/fundraisers/539-neovim-first-it... ). Many other editors don’t have these drawbacks, allowing them to support features such as these: • a graphical file tree browser (with icons, not restric…
Earlier quoted context omitted.
> 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…
so the grammars are still a bunch of regexes? that'd be kind of a letdown
Earlier quoted context omitted.
Maybe an announcement that git bought sublime and this is the web launch of it. I would be so excited if that happened.
The ST builds mysteriously stopped recently (ST3 beta and dev), which is a bit ominous.
Earlier 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.
Codebox works awesomely well, and you can host it locally. Still has bugs, but they do releases often.
Biscotto — A CoffeeScript API documentation generator based on TomDoc notation:
http://atom.github.io/biscotto/
React-Coffee — A little glue that makes Facebook's React easy to use from CoffeeScript without having to resort to JSX:
https://github.com/atom/react-coffee
SpacePen: A minimalist view library for jQuery, allowing custom methods, super calls, HTML-building, subviews, and easy event binding:
http://atom.github.io/space-pen/
... and the best bit about this bonanza is that everything is really quite readable. Keep up the good work, Kevin.
Website now says "SOON". Response from #atom irc channel: > Would the editor itself be open-source? > yes > a non-opensource editor from GitHub would be ludicrous > seems like the source code will be up today
Earlier quoted context omitted.
> An open, compile-less, hot-reloading editor sounds like a dream coming true. You're talking about Emacs, right? This actually seems really exciting, and I'll give it a whirl when and if I can. It's just funny to see people (the Light Table fans as well) rediscover what Emacs users already knew - modifying your editor in-place is really awesome .
You're talking about Emacs, right? Over the last 18 years, I've tried to figure Emacs out a few times, but it always ends up baffling me. It may be as powerful as you say, but given how obtuse I am (or perhaps how terrible Emacs is), I'll never know.
What made it work was (a) learning how to tweak the configuration to suit me, (b) learning Emacs jargon equivalents (chiefly: selection => region, cursor => point, open => find, file => buffer, pane => window) and (c) already knowing enough lisp to be able to tweak configuration further than simple variables and modes.
Then what really made it work was finding out about package repositories.
Emacs, when I first started out, didn't understand the arrow keys properly on my terminal, and required you to learn all the C-n, C-p, C-f, C-b etc. to move around. It also didn't have transient mark mode. But it can do all these things now (although I still have terminal configuration files to map function keys in Cygwin, Rxvt etc. because I mostly work in the terminal), all it really took was a Sunday afternoon researching settings, key bindings and modes, before it was almost as usable as any GUI editor.
Emacs is awesome. I'm sorry I didn't learn it sooner. I've gone through several generations of IDEs and programmer's editors that have come and gone in the past 20+ years. I could have been using Emacs all that time and increasing my knowledge and library.
It is, however, still weak with languages that heavily rely on IDE support, like Java and C#. emacs-eclim and other hacks aren't quite enough to make up for it. Although I still have an emacs session open on every Eclipse project because helm-git-grep is way too good to not use; and also it's better for certain text editing. I had a big aha moment when I found out that M-/ also works in Eclipse!