Oooh, this is interesting... Well the code block is below, and you can see
where the arrow is stopping on execution.
;;;###autoload
(defun nrepl-jack-in (prompt-project)
(interactive "P")
*=>*(let* ((cmd (if prompt-project
(format "cd %s && %s" (ido-read-directory-name "Project:
")
*nrepl-server-command*)
nrepl-server-command))
(process (start-process-shell-command
"nrepl-server" "*nrepl-server*" cmd)))
(set-process-filter process 'nrepl-server-filter)
(set-process-sentinel process 'nrepl-server-sentinel)
(set-process-coding-system process 'utf-8-unix 'utf-8-unix)
(message "Starting nREPL server...")))
That form has several calls, the first result is nil. The second result
error's out with the message below. And this is where execution just dies
and goes away
- nil
- *Symbol's value as variable is void: nrepl-server-command*
I can see in nrepl.el where nrepl-server-command is defined. But I don't
know enough about elisp to say what the problem is.
Tim Washington
Interruptsoftware.ca
416.843.9060
On Wed, Sep 19, 2012 at 3:31 PM, Tassilo Horn <t...@gnu.org> wrote:
> Timothy Washington <twash...@gmail.com> writes:
>
> > Well after *M-x nrepl-jack-in*, I notice that the "*Starting nREPL
> > server... *" message never goes away. But I don't *think* that's the
> > main problem.
>
> I think, it is. Normally, after that message it takes ~10secs and then
> a *nrepl* buffer should pop up. If that doesn't happen for some reason,
> then there's something wrong.
>
> > *1)* That help window looks like the following. So it doesn't look
> > like the *nrepl-interaction-mode* is enabled on emacs startup.
>
> It's enabled automatically in all clojure buffers as soon as nrepl
> successfully started, which doesn't seem to happen for you.
>
> > *2)* After executing the emacs command '*nrepl-interaction-mode*', I
> could
> > then execute *C-x C-e*, but got the following message
> >
> > No buffer named *nrepl-connection*
>
> Yeah, this buffer is also created once nrepl has successfully started.
>
> > *3)* So I went ahead and fired up *M-x nrepl*, and supplied the host
> > and port. Again, the result message "*Connecting to nREPL on
> > localhost:57260...*" never goes away (hopefully not the real problem).
>
> Hm, hm, why doesn't it want to connect...
>
> What you could do to debug the issue is open nrepl.el, goto the function
> definition of nrepl-jack-in, place point (the emacs cursor) on the
> function name, do `M-x edebug-defun RET', and then `M-x nrepl-jack-in
> RET'. Now you'll see an arrow in the margin indicating the flow of
> control. With `n' you can step one expression further, and the results
> are printed in the echo area. What are those values? Especially the
> result of `start-process-shell-command' might give a clue.
>
> Bye,
> Tassilo
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
