                                                                                                                                                                                                                                                                
Received-SPF: neutral (google.com: 67.192.241.153 is neither permitted nor denied by best guess record for domain of c...@cemerick.com) client-ip=67.192.241.153;
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Where to put nREPL init options?
From: Chas Emerick <c...@cemerick.com>
In-Reply-To: <7BEB1909-46AA-4F7A-83FE-1B2FCB9C2789@gmail.com>
Date: Mon, 8 Oct 2012 13:38:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <51D25EB7-9981-4EF9-A2A2-94EAF14D977F@cemerick.com>
References: <10bb3fc8-d95a-4ef7-abc4-0a20f0b0252a@googlegroups.com> <C37D9BC9-8DD6-4E2C-9938-793C761AB...@cemerick.com> <7BEB1909-46AA-4F7A-83FE-1B2FCB9C2...@gmail.com>
To: clojure-tools@googlegroups.com

On Oct 8, 2012, at 1:19 PM, Sam Aaron wrote:

> On 8 Oct 2012, at 17:56, Chas Emerick <c...@cemerick.com> wrote:
>=20
>> I personally think that :init probably should be included in the =
bootstrapping of all REPLs started from `lein`, including headless ones. =
 Filing an issue with Leiningen would be your next step if you agree.
>=20
> If I'm correct in assuming that this would allow you to boot an nREPL =
server with a specified port without starting reply, then I totally =
agree.

You can do that already with this in project.clj:

    {:repl-options {:port XXXX}}

`lein repl :headless` will start nREPL on port XXXX.

The :init option would just give you the ability to add code that should =
always be evaluated after the nREPL server is up.

- Chas=