nrepl

enn 2026-05-26T19:18:35.806259Z

It looks like nrepl.server/start-server ignores the config file. Is this a bug or by design?

2026-05-26T22:02:40.004719Z

https://github.com/nrepl/nrepl/issues/221 may be interesting reading, tl;dr is nrepl doesn't have a config file, config files are things that other bits of tooling uses when they decided how to start nrepl

2026-05-26T22:04:11.233479Z

(although I am shocked to see an nrepl.config also exists, which why? I dunno)

enn 2026-05-26T23:16:18.968569Z

OK, then I feel like these docs are pretty misleading: https://nrepl.org/nrepl/usage/server.html#server-configuration

➕ 1
2026-05-26T23:30:38.691249Z

you may have better luck calling whatever nrepl.cmdline does instead of nrepl.server/start-server then

2026-05-26T23:32:54.316339Z

although even there, the start-server function is just a wrapper around nrepl.server/start-server, and the config file merging and stuff is part of the cli arg parsing

enn 2026-05-27T01:28:27.251089Z

I've started down this road of calling start-server directly because for the first time I find myself wanting to connect CIDER to a running command-line tool. The nrepl cli stuff conflicts with my own tool's cli handling (`-m`, CLI parsing, etc.). Is there a better approach here that I'm not seeing?