-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Obscure error message when no nREPL is running #41
Comments
Previous version was relying on a |
(to make my previous comment clearer) |
That's interesting. How are you finding the nrepl port when there is no |
I phrased that poorly. I mean, how do you find the nrepl port before looking for the |
There are two functions on Another, much simpler way is to use "This will start a nrepl server with default arguments and cider and refactor-nrepl middlewares.
lua require("acid.nrepl").start{}
"This will start a nrepl server with only the piggieback middleware.
lua require("acid.nrepl").start{middlewares = {"cider/piggieback"}} |
Also, one can use jazz.nvim, which is a set of extensions of acid that make use of impromptu.nvim to have interactive menus. I splitted that from acid since I didn't want to impose another extra dependency, so the menus are opt-in. |
Oh, cool -- I didn't realize that you can use acid to start an nREPL. I'll have to play around with that. My typical workflow is usually to start my own nREPL in another terminal, so that I can have more control over the environment, dependencies, etc. There will often be old In that case, maybe a good error message would be something like "Unable to connect to nREPL on port 12345." |
That is possible to happening, yes. I think it's safe to assume that either way I should stop doing that on python and try to find my way through with lua, so one could auto-connect if a I'll look into it. :) |
* #41: Add .nrepl-port from lua if it's found * Add single log fn * Clear output before result
I believe this one is fixed now by 9667705, but I'll keep this open so I remember to refactor the python end. |
The issue is fixed from my perspective. 👍 BTW, I discovered something interesting. At least with Boot, when you quit the REPL by either running At any rate, things are feeling much nicer now. Much appreciated! |
Awesome! I'm really glad those issues are being solved and the experience of using acid is getting nicer :) Please don't refrain from opening issues and let me know if you have any other problems or suggestions! I'll close this now, but, as always, feel free to reopen if needed. Cheers, |
This is just a little thing I noticed where the experience could be a bit nicer:
If I don't have a REPL running, and I run
:AcidRequire
, I get this uncaught error:It would be nice if acid could recognize this scenario and say "No REPL found" or something.
The text was updated successfully, but these errors were encountered: