-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port arg is missing :parse-fn #201
Comments
Which version of reply are you using? This was a bug fixed in 0.4.4 - details in #199 |
Oh! I'm on 0.4.3, thanks! While I have you here, I've been trying to work reply into my workflow with calva. Right now if I start a standalone nrepl, nrepl automatically chooses a port and exposes a port you can connect to, as well as making an
I may have missed this but I did not see how to mimic this when using reply, is this supported? |
Hmm, I'm not sure there's currently a way to get that generated port number other than (a) doing the thing I did, where you reply/src/clj/reply/eval_modes/nrepl.clj Lines 156 to 169 in 4456223
I don't think I'd want us to write an |
I'm going to go ahead & close this issue - feel free to open another (or a PR!) if the above answer doesn't get you what you need for connecting to a port! |
Thanks again for the help! |
Trying to start reply with a
--port
arg throws the following exceptionLooks like there needs to be a
:parse-fn
added to parse strings to int.reply/src/clj/reply/main.clj
Line 45 in 4456223
The text was updated successfully, but these errors were encountered: