Earlier quoted context omitted.
Unix has a big flaw: through the pipes pass random data. It's up to the receivers to interpret it. Lisp gives you the possibility to easily structure your data and pass it around, plus the ability to pass programs around. Other than this, the unix way and the lisp way are nearly parallel, though in lisp "command line utility" is called a "procedure".
So, JSON passed between a bunch of Javascript things from Github means that the browser is the new EMACS ?
Why GNU Emacs?
241–250 of 317 posts
Re: Why GNU Emacs?
#242Out of curiosity, I have tried Vi and Emacs, but the CLI text editor I have gone back to is GNU nano. Am I missing something?
I don't use Emacs on the command line; I use a graphical instance. I usually only have two programmes open: Emacs and a graphical browser (eww still needs some work).
Being able to use my very own Emacs that has been molded according to my habits for pretty much every task is a great feature, but it only becomes obvious after some time of continued usage.
Re: Why GNU Emacs?
#243Earlier quoted context omitted.
Joel Moses has been credited with coining the phrase in the 1970s APL is like a beautiful diamond - flawless, beautifully symmetrical. But you can't add anything to it. If you try to glue on another diamond, you don't get a bigger diamond. Lisp is like a ball of mud. Add more and it's still a ball of mud - it still looks like Lisp.
> Lisp is like a ball of mud. Add more and it's still a ball of mud - it still looks like Lisp. Such claims are usually made by people who haven't discovered the power of Lisp yet. http://www.defmacro.org/ramblings/lisp.html
Re: Why GNU Emacs?
#244Earlier quoted context omitted.
Unix has a big flaw: through the pipes pass random data. It's up to the receivers to interpret it. Lisp gives you the possibility to easily structure your data and pass it around, plus the ability to pass programs around. Other than this, the unix way and the lisp way are nearly parallel, though in lisp "command line utility" is called a "procedure".
So, JSON passed between a bunch of Javascript things from Github means that the browser is the new EMACS ?
"Do everything in Emacs" isn't really so different from "Do everything in the browser."
Arguably, modern browsers are more heavyweight and complex at that. They certainly eat a hell of a lot more RAM than my Emacs ever does.
Re: Why GNU Emacs?
#245Earlier quoted context omitted.
I tried this, but found that the issue is that most major modes use a "grammar" that make sense to native-emacs user, and ended up fighting with them.
After a day of editing on Emacs on a MacBook Pro, my hands felt like they were going to shrink and stick into a contorted state. So I tried Evil which does work fairly well for editing text. In some ways it's better than Vim--the :substitute is really nice as it shows all pending substitutions in the buffer. But as you said, some major modes work with Evil and others don't, so I'm never sure what I'm going to get. Ir…
Re: Why GNU Emacs?
#246I enjoyed this; I moved from Vim to Emacs a couple of years ago and indeed the most important thing to recognise is this: Emacs does have a great text editor, and it's Vim! With evil-mode you can use all the Vim bindings you're used to (including sed commands with ':'), but with the added benefits (and drawbacks) of Emacs! I've also found that fiddling with my .emacs is really fun, fiddling with .vimrc was usually qu…
I tried this, but found that the issue is that most major modes use a "grammar" that make sense to native-emacs user, and ended up fighting with them.
Re: Why GNU Emacs?
#247Earlier quoted context omitted.
I tried this, but found that the issue is that most major modes use a "grammar" that make sense to native-emacs user, and ended up fighting with them.
I used vim for 20 years before switching to emacs. I'd actually tried switching twice. Firt time with viper (I think), which didn't have good enough vim emulation. Second time evil-mode finally convinced me to switch completely. Then I ran in to the same issue as you, that a lot of emacs modes had native emacs keybindings. So what I wound up doing was re-binding those to be more vim-like. I didn't rebind everything,…
An important realisation was that I only need my Emacs to do the basic Vim things and then some extensions I commonly use. At that point, I can survive using only Emacs and building onto it as I feel like I need something.
Re: Why GNU Emacs?
#248Many Emacs advocates fall for the trap of apologizing for why Emacs is not Unixy, as though it were some sort of defect. They should celebrate the fact that Emacs doesn't come from the Unix tradition of small, composable tools and "doing only one thing and doing it well". It is rooted in the ambitious work of the MIT Artificial Intelligence lab, the LISP programming language, and the single user MIT Lisp Machine that…
Emacs does only one thing. And does that one thing very well - "Extensibility"
Re: Why GNU Emacs?
#249Earlier quoted context omitted.
Unix has a big flaw: through the pipes pass random data. It's up to the receivers to interpret it. Lisp gives you the possibility to easily structure your data and pass it around, plus the ability to pass programs around. Other than this, the unix way and the lisp way are nearly parallel, though in lisp "command line utility" is called a "procedure".
So, JSON passed between a bunch of Javascript things from Github means that the browser is the new EMACS ?
Re: Why GNU Emacs?
#250Earlier quoted context omitted.
So, JSON passed between a bunch of Javascript things from Github means that the browser is the new EMACS ?
The article more or less makes this precise comparison. "Do everything in Emacs" isn't really so different from "Do everything in the browser." Arguably, modern browsers are more heavyweight and complex at that. They certainly eat a hell of a lot more RAM than my Emacs ever does.