@mbcladwell One of the reasons we don't release Arei 1.0 is because guile is not yet updated in guix, so it requires some hussle to setup correctly: rebuilding guix and other packages with guile-next to work with ares, carefully setting apropriate load paths and so on.
@abcdw
Here I start the server without specifying #:port:
mbc@ins3910:~$ guix shell guile-next guile-ares-rs -- \
guile -c '((@ (ares server) run-nrepl-server))'
nREPL server started on port 7888 on host localhost - nrepl://localhost:7888
again:
mbc@ins3910:~$ guix shell guile-next guile-ares-rs
mbc@ins3910:~ [env]$ guile -c '((@ (ares server) run-nrepl-server))'
nREPL server started on port 62181 on host localhost - nrepl://localhost:62181
again:
mbc@ins3910:~$ guix shell guile-next guile-ares-rs
mbc@ins3910:~ [env]$ guile -c '((@ (ares server) run-nrepl-server))'
nREPL server started on port 51474 on host localhost - nrepl://localhost:51474
again:
mbc@ins3910:~$ guix shell guile-next guile-ares-rs -- guile -c '((@ (ares server) run-nrepl-server))'
nREPL server started on port 7888 on host localhost - nrepl://localhost:7888
As a one liner or with the bash continuation I always get port 7888
Split into two commands I always get a random port. Is this expected?
I thought bash \ was simply continue command on next line but here it seems to affect behavior.
I do get a ~/.nrepl-port file containing the port ID but when I start emacs it seems to ignore it and always looks to port 7888, which is why I thought I need to specify with #:port
@abcdw
Here I start the server without specifying #:port:
mbc@ins3910:~$ guix shell guile-next guile-ares-rs -- \
guile -c '((@ (ares server) run-nrepl-server))'
nREPL server started on port 7888 on host localhost - nrepl://localhost:7888
again:
mbc@ins3910:~$ guix shell guile-next guile-ares-rs
mbc@ins3910:~ [env]$ guile -c '((@ (ares server) run-nrepl-server))'
nREPL server started on port 62181 on host localhost - nrepl://localhost:62181