I use Emacs as a text editor, which means I use it to edit anything that has text. Granted that is a huge part of my computing needs.
I don't want Emacs to be able to do anything. I already have an operating system and a text editor.
I use Emacs as a text editor, which means I use it to edit anything that has text. Granted that is a huge part of my computing needs.
I don't want Emacs to be able to do anything. I already have an operating system and a text editor.
"We used the same idea here (in the hybrid technique), that most of the editor would be written in Lisp, but certain parts of it that had to run particularly fast would be written at a lower level"
http://www.gnu.org/gnu/rms-lisp.html
That's the beauty of Emacs. Considering that he built it in the early 80s, you have to wonder if the whole thing couldn't be written Lisp today.
I use emacs as a source navigation and exploration tool, even more than for text editing. Its ability to run code customized to the language and projects I'm working on is far more important than its ability to edit text.
I actually don't like a lot of its text editing functionality, and had to work hard to get things like selection, tab indenting, scrolling etc. to work in a way that didn't drive me up the walls. I had to give up on virtual space, one of the things that stopped me learning it 10 years ago. It's also very hard to record keyboard macros without accidentally cancelling (I tend to press C-g reflexively when I type a wrong shortcut); I use multiple cursors these days instead, even though that is much riskier / harder to use when you can't see the whole buffer / all edit locations on screen at once.
A browser, I don't really need that per se - unless it's linked to library documentation. But it's hard to integrate modern docs without at least understanding HTML, if not HTTP. So I can see the need for a browser implementation.
If you only use Emacs as a text editor, that's fine for using a subset of it. Just like a casual user uses Linux without never using its underlying tools in the terminal.
> saying that Emacs is only a Lisp interpreter implies that the entirety of the text editor is implemented in Lisp, which is clearly not the case.
With this argument, I guess Python is also not an interpreter because clearly it is not entirely written in Python.