41–50 of 79 posts
OSX build seems to work really well: ./configure --with-gif=no --with-ns make make install
OSX build seems to work really well: ./configure --with-gif=no --with-ns make make install
checking host system type... i386-apple-darwin11.3.0 configure: error: Emacs hasn't been ported to `i386-apple-darwin11.3.0' systems. Check `etc/MACHINES' for recognized configuration names.
the only time i hate the packaging system [apt] is when a new version of some software is released
Nix and apt are very complementary to each other; apt has all the stable never-breaks stuff, and nix has all the latest new code. And when you pull in something too new that breaks, you can roll it back trivially.
This means that I can finally try out Emacs Prelude [1]. Fantastic! I've been wanting to check it out for a while, but I haven't been brave enough to run a non-stable release of GNU Emacs. http://batsov.com/prelude/
What functionality does prelude provide? Unless I'm missing something, the website suggests that you can find out by "reading the source." I had a similar experience once with the emacs starter kit [1]. Though it's a noble effort and probably does have a ton of great features, there are some problems: you pretty much get all or nothing (ESK split it out into a "core" and "per-language" set of libraries but still, the…
For what it's worth, I've come around to this viewpoint. I rewrote ESK for version 2, and the emphasis was on packaging as much functionality in independent packages as possible. So as of v2, the Starter Kit is mostly just about providing a default set of packages and turning on a few flags that it's just crazy to leave off (like ido). But this way more of the functionality is available to everyone, not just users of ESK.
Anyway, it certainly needs more documentation, but these days I recommend the Starter Kit more as a source of inspiration than something people should just use outright, at least if they're not in a hurry.
Earlier quoted context omitted.
It's opt-in, otherwise most packages would break. To enable it per-file use a file-local variable: ;;; -*- lexical-binding: t -*-
How ironic. Wouldn't it make much sense to enable it per lexical scope? Or as Perl did it (18 years ago) with a new keyword, so that you can use both dynamic and lexical variables in the same file? Best of both worlds.
Earlier quoted context omitted.
What functionality does prelude provide? Unless I'm missing something, the website suggests that you can find out by "reading the source." I had a similar experience once with the emacs starter kit [1]. Though it's a noble effort and probably does have a ton of great features, there are some problems: you pretty much get all or nothing (ESK split it out into a "core" and "per-language" set of libraries but still, the…
Author of the Starter Kit here. For what it's worth, I've come around to this viewpoint. I rewrote ESK for version 2, and the emphasis was on packaging as much functionality in independent packages as possible. So as of v2, the Starter Kit is mostly just about providing a default set of packages and turning on a few flags that it's just crazy to leave off (like ido). But this way more of the functionality is availabl…
OSX build seems to work really well: ./configure --with-gif=no --with-ns make make install
And the formatting didn't survive pasting. Should have been: ./configure --with-gif=no --with-ns; make; make install