Connection logic

[danielsz]

With the latest release CIDER 0.8.0alpha (package: 20140924.148), cider doesn't autodetect the repl host and port like it used to. I saw that the latest merge touches on this functionality, and I'll be happy to provide any information you might need.

[vspinu]

It might be a regression. Is this windows? Which host and port do you mean more precisely? The current nREPL server in the same emacs instance?

On linux and mac the latest merge should detect all running repls on current or remote host.

I think it would be safe to compliment current system with a check of .nrepl-port in the current directory tree, and also sweep all running instance of nREPL server in the current emacs for host:port pairs. I will add this tomorrow.

[kij]

current master dont use nrepl-default-port (which was used read the port from ./repl-port)
gone with 57ac604.

[danielsz]

@Vitoshka Yes, a regression. I mean the nREPL launched with lein repl :headless outside of Emacs, and connecting with M-x cider-connect. I'm on mac.
@kij Spot on.

[vspinu]

@danielsz Could you please post the result of (shell-command-to-string cider-ps-running-nrepls-command).

Please look at cider-ps-running-nrepls-command and cider-ps-running-nrepl-path-regexp-list. They might need to be adjusted for mac.

[danielsz]

With pleasure.

Here is cider-ps-running-nrepls-command

"danielszmulewicz 30378   0.1  3.6  5049364 150600 s006  S+    6:10AM   0:58.87 /usr/bin/java -client -XX:+TieredCompilation -Xbootclasspath/a:/usr/local/Cellar/leiningen/2.5.0/libexec/leiningen-2.5.0-standalone.jar -Dfile.encoding=UTF-8 -Dmaven.wagon.http.ssl.easy=false -Dleiningen.original.pwd=/Users/danielszmulewicz/Documents/clojure/twitter-fu/twitter-fu-back-end -Dleiningen.script=/usr/local/bin/lein -classpath :/usr/local/Cellar/leiningen/2.5.0/libexec/leiningen-2.5.0-standalone.jar clojure.main -m leiningen.core.main repl :headless
danielszmulewicz 30233   0.1  1.3  5041248  55564 s008  S+    5:53AM   0:51.70 /usr/bin/java -client -XX:+TieredCompilation -Xbootclasspath/a:/usr/local/Cellar/leiningen/2.5.0/libexec/leiningen-2.5.0-standalone.jar -Dfile.encoding=UTF-8 -Dmaven.wagon.http.ssl.easy=false -Dleiningen.original.pwd=/Users/danielszmulewicz/Documents/clojure/testing/test -Dleiningen.script=/usr/local/bin/lein -classpath :/usr/local/Cellar/leiningen/2.5.0/libexec/leiningen-2.5.0-standalone.jar clojure.main -m leiningen.core.main repl :headless
"

And here is the value of cider-ps-running-nrepl-path-regexp-list

cider-ps-running-nrepl-path-regexp-list is a variable defined in `cider.el'.
Its value is
("\\(?:leiningen.original.pwd=\\)\\([^ ]+\\)" "\\(?:-classpath +:?\\(.+\\)/self-installs\\)")

[vspinu]

Ok. So the regexp works. You have two running instance on nREPL server on your computer and both of them should be detected.

What's the value returned by M-: (cider-locate-running-nrepl-ports) and M-: (cider--get-running-nrepl-paths)?

My best guess is that you don't have .nrepl-port in file in your project directories. It seems that sometimes leiningen deletes them for no reason.

[danielsz]

(cider-locate-running-nrepl-ports):

(("test" "59218") ("twitter-fu-back-end" "59307") ("twitter-fu-front-end" "60430"))

(cider--get-running-nrepl-paths):

("/Users/danielszmulewicz/Documents/clojure/testing/test" "/Users/danielszmulewicz/Documents/clojure/twitter-fu/twitter-fu-back-end" "/Users/danielszmulewicz/Documents/clojure/twitter-fu/twitter-fu-front-end")

All projects have a .nrepl-port in the root directory.

(In the meantime, I've started another nREPL, so that's why the count is 3)

[vspinu]

(("test" "59218") ("twitter-fu-back-end" "59307") ("twitter-fu-front-end" "60430"))

Ok, so it works. Are these all of your running leiningens? M-x cider-connect should show them in completion.

[danielsz]

OK, then we have two problems. One is usability. I see only a host: prompt, and I don't know there is completion. Second, when I select 127.0.0.1, then tab complete, I see my local nrepls, but when I select any of them, it says: nREPL: Direct connection failed.

[danielsz]

For the usability problem, the default should show local nREPLs, and then there should be an option to select remote hosts. Overall, the new feature is good, but it should not make it more troublesome to select a local nREPL.
The second problem is related to how the host and port arguments get concatenated via the echo area interface.

[vspinu]

One is usability. I see only a host: prompt, and I don't know there is completion.

This is how standard emacs works. All complains go there. You are not using ido, so you don't have a hint of your completions. This is what I see #808.

he default should show local nREPLs,

There are several. What's the default one?

The second problem is related to how the arguments get concatenated.

What do you mean? Could you please go to the source of cider-connect instrument it with C-u M-C-x and when it starts stepping through see the value of "port" and "host".

Sometimes it happens that open-network-stream cannot connect to the running server. I guess it's some lein issue. We cannot do anything with that. Sometimes it works on the second trial.

[danielsz]

Here's how I think the default should work: if I type M-x cider-connect from a buffer with a Clojure source file, the pre-selected nREPL should be the one that can be found in the root directory of the project to which said source file belongs.

[danielsz]

This is how standard emacs works. All complains go there. You are not using ido, so you don't have a hint of your completions. This is what I see #808.

Ah, I see. Well, I am using ido, but I don't see what is shown on #808. What am I missing?

[danielsz]

My ido config is this:

(setq ido-enable-flex-matching t)
(setq ido-everywhere t)
(ido-mode 1)

[vspinu]

What am I missing?

ido-ubiquitous should activate ido for almost all completions in emacs.

the pre-selected nREPL should be the one that can be found in the root directory of the project to which said source file belongs.

I agree and I will try to add this today. A slight issue is that users like you, with no IDO, will never find that they can complete and connect to any running repl.