Earlier quoted context omitted.
Emacs is GUI desktop software. Few people use it in a terminal. Also, people didn't born knowing Javascript. They learnt it. And one could argue that Lisp is just as easy to learn, if not easier.
I mostly agree with that although I think it's also kind of irrelevant in a practical sense because many programmers already have to know javascript for their work so you get a lot more people who can contribute right away. Aside from that -- lisp or javascript as the extension language, I'd love to see a brand-new extensible editor like emacs just to have a shot at changing terminology and some of the APIs. Emacs te…
Atom
251–260 of 662 posts
Re: Atom
#252I for one am more enticed by the possibility of a WebKit frontend, with a NeoVim core and a libuv backend. Finally, Vim as an embeddable library.
Re: Atom
#253It could be really great. I wonder if Jon Skinner knew, and said to himself "Welp, I might as well stop with Sublime". However, Sublime is (mostly) blazingly fast. I don't expect this from a node based app, especially in Windows. And: I didn't see it under Features, but Atom definitely needs the command palette from Sublime baked into core. Only if it's core, plugin authors will set their hooks correctly from the beg…
Re: Atom
#254Earlier quoted context omitted.
Well, one can only assume, based on the wording they use here: https://github.com/atom/welcome/blob/master/lib/welcome.md > Atom is free during the beta period.
How refreshing, a correct usage of "the exception that proves the rule"!
Re: Atom
#255Pair editing.
Specifically, having the ability to pair two editors over a network and edit the same set of files.
Lots of other editors do this, but here's the key: Each editor keeps its own settings and environment.
I'm a vim guy. I can set up my Atom to be vimlike. My buddy, the Emacs (heretic!) guy, can set up his Atom the way he likes, and we can work in harmony.
That's all I want.
Re: Atom
#256Atom team, if you're reading this, I have a big feature request that would make this far, far greater than just another editor. Pair editing. Specifically, having the ability to pair two editors over a network and edit the same set of files. Lots of other editors do this, but here's the key: Each editor keeps its own settings and environment. I'm a vim guy. I can set up my Atom to be vimlike. My buddy, the Emacs (her…
Re: Atom
#257Earlier quoted context omitted.
> and there's no compilation step or anything -- then it's almost a fundamental paradigm shift for what desktop software could be. > It already makes me dream of a word processor I could hack like that, or a music player. Just by opening up a text editor. It's an inspiring thought. Not to rain on your parade or anything, but you can already do this with Emacs, not to mention that Emacs is free, open source software.…
True, but it's a question of accessibility. Far more people can program in JavaScript than Lisp, and far more people use GUI desktop software that follows traditional GUI user-interface paradigms, than do things inside their terminal. (Edit: or terminal-style buffers/frames.) So that's why my statement was limited to what " desktop software" could be. :) I mean, I use LibreOffice, which is FOSS, but I am never going…
WTF do you mean by "terminal-style buffers/frames?"
Re: Atom
#258Earlier quoted context omitted.
Emacs is GUI desktop software. Few people use it in a terminal. Also, people didn't born knowing Javascript. They learnt it. And one could argue that Lisp is just as easy to learn, if not easier.
Most emacs users I know alias emacs to emacs-nw, or install emacs-nox. Myself included (:
Re: Atom
#259Earlier quoted context omitted.
In practice, the ST3 API is extremely limiting and poorly implemented. The docs are both lacking and dated (read incorrect). It is trivial to crash ST3 by making the incorrect sequence of correct API calls. It is also common to resort to polling the editor to make up for other deficiencies. The API also only allows for extremely limited UI choices forcing highly unintuitive interfaces on end users. The ST3 runtime al…
What do you mean polling the editor? Are there any examples of plugins that do that?
In terms of ease of development, the order goes like this: IntelliJ ~ Emacs > Sublime ~ Ace >> Vim. In terms of community and support, the former ordering is also true.
POLLING:
Here we are trying to get the Window, from the Sublime API. Sometimes it doesn't exist (even when windows are open). There is no reliable API to tell us when new ones are made or when old ones go away. Presumably, post_window_command (http://www.sublimetext.com/docs/3/api_reference.html#sublime...) would fire off with a close command, but this function has never worked.
https://github.com/Floobits/floobits-sublime/blob/master/flo...
Here is another quick hack polling the editor to know when its safe to call the sublime API: https://github.com/Floobits/floobits-sublime/blob/master/flo...
Here is a yet anther example needed for functionality and using callbacks to keep sublime from crashing: https://github.com/Floobits/floobits-sublime/blob/master/flo...
Here is another example of pure craziness forced on us by ST3. We need to patch Views, but ignore our own patches (locally) so we don't form an echo loop. We also need to move the cursor so it doesn't jump. Sublime deals with these changes so poorly, we are forced to jump through hoops. In contrast- emacs/vim/intellij are basically fine just dumping on the entire buffer.
https://github.com/Floobits/floobits-sublime/blob/master/flo...