News for hackers. Stuff that matters.
Re:Sublime Text 3 marked as recommended build by Scarbutt on Tuesday May 31, 2016 @01:56AM (#11804886)
Is sublimetext as hackable(extensible) as emacs or atom?
Re:Sublime Text 3 marked as recommended build by rattray on Tuesday May 31, 2016 @02:01AM (#11804903)
It's not open-source, so generally, no.

Packages are in python, and most of those are open-source (and thus available as examples) so extending through packages is probably easy.

Re:Sublime Text 3 marked as recommended build by bjz_ on Tuesday May 31, 2016 @02:47AM (#11805079)
With Atom addons can also do a great deal of UI customization too, due to the fact that it is built on the web stack. You pay for it in performance though...
Re:Sublime Text 3 marked as recommended build by Johnny_Brahms on Tuesday May 31, 2016 @03:03AM (#11805131)
I doubt any editor is as hackable as emacs. The stuff/havoc you can create using advices in emacs is astounding.
Re:Sublime Text 3 marked as recommended build by stirner on Tuesday May 31, 2016 @09:22AM (#11806341)
Proprietary programs have a limit to their hackability and extensibility which is enforced by law.
Re:Sublime Text 3 marked as recommended build by wcummings on Tuesday May 31, 2016 @02:15AM (#11804951)
Atom? Maybe. Emacs? Nope.
Re:Sublime Text 3 marked as recommended build by Scarbutt on Tuesday May 31, 2016 @02:27AM (#11805006)
Well, in Atom you can replace any of the javascript Atom comes with with your own customizations, same in Emacs with elisp, where does the difference lie? (I'm a emacs/evil user).
Re:Sublime Text 3 marked as recommended build by Derbasti on Tuesday May 31, 2016 @03:49AM (#11805286)
Emacs is written almost exclusively in elisp, and every elisp function can be changed at any time. Much of Emacs' core lies wide open in the global namespace, and is thus easy to change from any level.

As far as I understand, Atom has quite a bit of code that is not openly accessible, be it because it is part of a Node.js, transpiled from something else, buried in closures, or simply too deep in the hierarchy to be easily reachable from the plugin level. Sure, you could change it if you set your mind to it and maybe patched a few files here and there, but it's certainly not as easy as in Emacs.

Re:Sublime Text 3 marked as recommended build by enibundo on Tuesday May 31, 2016 @03:56AM (#11805314)
1. Think about something; you can do that in emacs.

2. Think about something; you can maybe do that in Sublime.

I'm not even talking about running a shell on your emacs but just about text-editing.

Re:Sublime Text 3 marked as recommended build by provemewrong on Tuesday May 31, 2016 @02:48AM (#11805083)
I'm just guessing, but perhaps in the Elisp macro capabilities, that arise from the language's homoiconicity?
Re:Sublime Text 3 marked as recommended build by JeremyMorgan on Tuesday May 31, 2016 @01:59AM (#11804899)
I would say pretty likely, plugins are Python based and easy to create.