javajosh writes:
> Ok, I decided to nuke ports, fink, and delete every package they ever
> installed. I successfully installed emacs 23.2 via homebrew (there's a
> good overview of homebrew here
> http://ascarter.net/2010/02/22/homebrew-for-os-x.html).
I'm coming late to this game, and I see tha
On Mon, Dec 13, 2010 at 9:10 PM, javajosh wrote:
> But seriously, it looks like despite the SLIME error it installed, and
> the lein stuff installed without a problem, so I have a pretty decent
> environment. Phew, that was easy!
Yeah, though it's not so bad on OSes that have a good built-in pack
On Dec 13, 8:51 pm, Phil Hagelberg wrote:
> If you check out the source for Emacs 24, it comes with package.el
> already, so once it's released it will definitely be the lowest-hassle
> way to get started. No need to worry about instability; I've been
> following Emacs trunk since 2007 or so witho
On Mon, Dec 13, 2010 at 8:27 PM, Robert McIntyre wrote:
> I don't know how applicable this might be for you, but I've had no
> problems whatsoever checking out the latest source for emacs 23 and
> compiling from source using the mac developer tools, all on my
> friend's laptop. All I did was type
On Dec 9, 11:11 pm, Andy Fingerhut wrote:
>
> Follow the instructions on the ELPA page for installing it:
>
> http://tromey.com/elpa/install.html
>
> After you do M-x package-list-packages, go down the list of packages
> until the cursor is on the line for the package "clojure-mode", pre
I don't know how applicable this might be for you, but I've had no
problems whatsoever checking out the latest source for emacs 23 and
compiling from source using the mac developer tools, all on my
friend's laptop. All I did was type make and cross my fingers.
you might give it 5 minutes if other
Aha! You're a genius!
On Dec 13, 8:06 pm, gaz jones wrote:
> homebrew installs a mac application to:
>
> /usr/local/Cellar/emacs/23.2/Emacs.app/
>
> by default which you can run from there, or copy to your /Applications
> folder to run. running from the terminal doesnt seem to work so well
> in m
homebrew installs a mac application to:
/usr/local/Cellar/emacs/23.2/Emacs.app/
by default which you can run from there, or copy to your /Applications
folder to run. running from the terminal doesnt seem to work so well
in my experience.
On Mon, Dec 13, 2010 at 8:43 PM, javajosh wrote:
> Ok, I
Ok, I decided to nuke ports, fink, and delete every package they ever
installed. I successfully installed emacs 23.2 via homebrew (there's a
good overview of homebrew here
http://ascarter.net/2010/02/22/homebrew-for-os-x.html).
I started the emacs it installed, but I didn't know how to access the
Chris Maier writes:
>> (if window-system (set-exec-path-from-shell-PATH))
>
> This was a huge help for me, but I had to replace the "-i" flag with
> "--login" in order to fully replicate my path that I see in Terminal.
> I have a few things set in /etc/paths.d (TeX, X11, and git,
> specifically),
On Fri, Dec 10, 2010 at 6:24 AM, Steve Purcell wrote:
>> If you have issues with emacs failing to pick up the right executables,
> you can use the following nifty trick to ensure Emacs' $PATH matches the
> one you've configured for Bash in Terminal:
>
> (defun set-exec-path-from-shell-PATH ()
> (
+1 to Andy Fingerhut's GNU-via-MacPorts instructions; WFM. I need an
exact workalike across Mac, linux and cygwin, which is why I prefer it
over the better-integrated Aqua/Carbon/Cocoa alternatives.
A big +1 to Phil Hagelberg's make-the-wiki-authoritative call. I can
attest to the confusion
brew install emacs --cocoa
worked pretty well for me. and then my fork of emacs-starter-kit if
that is useful to anyone:
https://github.com/gar3thjon3s/emacs-starter-kit
my default-profile.el has a few settings for making the brew installed
emacs work better with os x.
by the way thanks for the
On Sat, 11 Dec 2010 01:07:51 +
Alec Battles wrote:
> > I don't use OS X so I can't comment on such a consensus, but while I
> > appreciate the sentiment, it's actually harmful to some degree to have
> > lots of blog posts scattered around everywhere that all have slightly
> > different advice
On Fri, Dec 10, 2010 at 5:07 PM, Alec Battles wrote:
>> I strongly suggest improving the docs on the
>> Clojure wiki instead; that way errors can be fixed by the community.
>
> Why does the one preclude the other?
>
> Also, if people aren't going to blog about Clojure, what future does it have?
S
> I don't use OS X so I can't comment on such a consensus, but while I
> appreciate the sentiment, it's actually harmful to some degree to have
> lots of blog posts scattered around everywhere that all have slightly
> different advice, especially since that advice usually becomes
> outdated within
On Fri, Dec 10, 2010 at 11:20 AM, javajosh wrote:
> (conflicting advice snipped)
>
> If we can reach consensus on best (easiest, least error-prone) path to
> getting a working emacs clojure environment up on OSX I'll happily
> execute and even write up my experience.
I don't use OS X so I can't c
javajosh writes:
> (conflicting advice snipped)
>
> If we can reach consensus on best (easiest, least error-prone) path to
> getting a working emacs clojure environment up on OSX I'll happily
> execute and even write up my experience.
I think there is consensus; the respondents to this thread se
(conflicting advice snipped)
If we can reach consensus on best (easiest, least error-prone) path to
getting a working emacs clojure environment up on OSX I'll happily
execute and even write up my experience.
--
You received this message because you are subscribed to the Google
Groups "Clojure" g
javajosh writes:
>> failing to load in the error message and all, I'd try that.
> I would still like to see slime in action, however. I have two emacs
> installed, GNU and Aquamacs. macports is still not able to do anything
> - I'm actually rather concerned about it's health.
>
> $ emacs --version
Here is a list of steps that should get you to a working Emacs+Clojure
SLIME on Mac OS X. I've also used it on Linux (without the MacPorts
command, instead using its package manager to install a working GNU
emacs).
If you don't have many MacPorts programs installed, or don't mind
reinsta
> I would still like to see slime in action, however. I have two emacs
> installed, GNU and Aquamacs. macports is still not able to do anything
Sorry if this sounds silly but have you tried with carbon emacs? I
heard from old time hardcore emacsers that that is the best emacs for
OS X (I'm not one
On Dec 9, 5:41 pm, Alec Battles wrote:
> > On Dec 6, 9:16 pm, Phil Hagelberg wrote:
> >> On Mon, Dec 6, 2010 at 9:00 PM, javajosh wrote:
> >> > Sorry for asking here, but I think it's at least a little relevant to
> >> > Clojure since I for one wouldn't be installing emacs if it wasn't for
> >>
> On Dec 6, 9:16 pm, Phil Hagelberg wrote:
>> On Mon, Dec 6, 2010 at 9:00 PM, javajosh wrote:
>> > Sorry for asking here, but I think it's at least a little relevant to
>> > Clojure since I for one wouldn't be installing emacs if it wasn't for
>> > Clojure and Slime. Getting prompts about what th
On Dec 6, 9:16 pm, Phil Hagelberg wrote:
> On Mon, Dec 6, 2010 at 9:00 PM, javajosh wrote:
> > Sorry for asking here, but I think it's at least a little relevant to
> > Clojure since I for one wouldn't be installing emacs if it wasn't for
> > Clojure and Slime. Getting prompts about what the fu
On Mon, Dec 6, 2010 at 9:00 PM, javajosh wrote:
> Sorry for asking here, but I think it's at least a little relevant to
> Clojure since I for one wouldn't be installing emacs if it wasn't for
> Clojure and Slime. Getting prompts about what the function arguments
> are seems like a HUGE benefit whe
26 matches
Mail list logo