For those who prefer a language with namespaces (python) sublime editor is a good modern alternative.
Let's just use Emacs
81–90 of 169 posts
Re: Let's just use Emacs
#82I resonate somewhat with the gripes about Emacs' crustiness. But on the other hand, I don't understand the complaints about it being ugly. I haven't heard that for a while. I'd like to think that my Emacs is quite pretty: http://jlongster.com/s/emacs.png There are things Emacs can do which VIM will never do. And vice-versa. They are separate editors embracing separate philosophies. Lastly, keep in mind that this is 4…
Re: Let's just use Emacs
#83I use Emacs for coding, wanderlust mail, rcirc and jabber-el. All which are provided as packages in the distros I run. I've been trying to get into clojure which entails installing clojure-mode, swank-clojure, leiningen (which brings the pain of maven) and slime. This is where emacs has always broken down for me. Once I step outside the distro provided packages I find broken tutorials, unspecific versions, and instru…
Whenever installing software for Emacs, it's usually worth checking ELPA http://tromey.com/elpa/ (which comes installed on Emacs by default now,) to see if the package is there already. The ELPA provide both slime and clojure-mode and they work out of the box with swank-clojure. You'll still need to install Leiningen/Cake with swank-clojure separately, but there isn't much Emacs can do to help there.
Re: Let's just use Emacs
#84Earlier quoted context omitted.
Whenever installing software for Emacs, it's usually worth checking ELPA http://tromey.com/elpa/ (which comes installed on Emacs by default now,) to see if the package is there already. The ELPA provide both slime and clojure-mode and they work out of the box with swank-clojure. You'll still need to install Leiningen/Cake with swank-clojure separately, but there isn't much Emacs can do to help there.
Ah, but now you're not following the instructions provided by swank clojure which says to use marmalade (which is an elpa extension/replacement/clone/additional repository?) The clojure-mode available through elpa ( clojure-mode 1.7.x) is not new enough to deal with swank-clojure which needs 1.9.x (specifically I was after M-x clojure-jack-in) Plus, the elpa instructions don't include emacs23 because it allegedly com…
Once that has had a stable release, this will become a lot easier. In the mean time, the link to package.el for Emacs 23 is right at the top of marmalade-repo.org: http://bit.ly/pkg-el23
Re: Let's just use Emacs
#85Articles about why anything you can do in a "simpler" text editor can and should be done in emacs strongly resemble articles about why anything you can do in a less powerful programming language can and should be done in Lisp. I don't think it's a coïncidence.
I'm not sure if you're making a general point, but I don't think it's universally true. Anything you can do on a netbook can be done faster and more accurately on a supercomputer. Working backwards from why we don't all use supercomputers, we can probably figure out why not everyone uses lisp and emacs.
Re: Let's just use Emacs
#86Earlier quoted context omitted.
Ah, but now you're not following the instructions provided by swank clojure which says to use marmalade (which is an elpa extension/replacement/clone/additional repository?) The clojure-mode available through elpa ( clojure-mode 1.7.x) is not new enough to deal with swank-clojure which needs 1.9.x (specifically I was after M-x clojure-jack-in) Plus, the elpa instructions don't include emacs23 because it allegedly com…
I can't say that I've run into this exact issue, or even exactly what the issues have been that I've run into with Emacs, but I know I've spent many hours reading instructions, following tutorials and generally just trying to get a basic emacs/lisp setup running. It's really difficult to do. I think I had a partially working Clojure setup, but then I tried to make it support Common Lisp in addition, and things comple…
This is due to the SLIME developers' insistence on making everyone run from CVS trunk. I wish I were joking, but they really seem to have no interest in creating stable release packages, so I have to go in and try to make it work without their cooperation.
Re: Let's just use Emacs
#87tl;dr Use Emacs 23 to create a distraction-free writing environment using org-mode, darkroom-mode & markdown-mode.
For linux environments, instead of darkroom-mode you can put this in your .emacs file to toggle fullscreen: ;;; Fullscreen (defun switch-full-screen () (interactive) (shell-command "wmctrl -r :ACTIVE: -btoggle,fullscreen")) (global-set-key (kbd " ") 'switch-full-screen)
Re: Let's just use Emacs
#88Earlier quoted context omitted.
Sorry, you're right. I was confused by the ELPA page which lists instructions only for emacs 21 and 22, but says elpa will be included in the next version of Emacs. (edit: now I can't find where I read this. I'm incredibly confused.) Now I'm confused about how my other installs have it working.
I've suffered from the same confusion, on finding that ELPA no longer worked for me with Aquamacs 2.0, I tried using the Marmalade repo with no joy. Quite frustrating as I was using ELPA in my fork of the Aquamacs Emacs Starter Kit: https://github.com/evangineer/aquamacs-emacs-starter-kit
Re: Let's just use Emacs
#89Articles about why anything you can do in a "simpler" text editor can and should be done in emacs strongly resemble articles about why anything you can do in a less powerful programming language can and should be done in Lisp. I don't think it's a coïncidence.
The title raised my hackles as well, but it turned out to be a fun, un-dogmatic read with nothing to do with the editor wars. Upvoted. Or perhaps it was just that he didn't bash my favorite editor :)
Re: Let's just use Emacs
#90Articles about why anything you can do in a "simpler" text editor can and should be done in emacs strongly resemble articles about why anything you can do in a less powerful programming language can and should be done in Lisp. I don't think it's a coïncidence.
Simple text editor = simple + powerful
Emacs = complex + powerful
Lisp = simple + powerful
Blub = complex + powerful
Given this your association doesn't make much sense.I think most people prefer simple + powerful. And this isn't black and white - Blub can often be simpler for X simple task. However the real yard stick is whether as your problem domain gets more complex does Blub suddenly lose its veneer of simplicity?
I always bring up Alan Kay in these kind of threads but his observations are always so damn salient - agglutinative PLs (features) vs style PLs (simple principles).