https://stackoverflow.com/a/74546586/564509 Should also work for tree.

That did the treek

What are the local resources on your classpath? You can check with (System/getProperty "java.class.path") where you split its output by ":" and remove all jars.

boot.user=> (System/getProperty "java.class.path")
"/usr/bin/boot"

I'm using Boot to provide the repl

There's no boot.clj or anything like that

if you define vars only in running repl then you don't need to call require the code is already "required" and available via qualified var like myns/myfn beware that without "project" you wouldn't have access to any dependencies except provided by clojure itself

you could also look at beginners guide. There is a new way to manage clojure "project" without having project at all. It is called Clojure CLI

As in this? https://clojure.org/guides/deps_and_cli

this one is very useful. and I would definitely recommend to read throw other pages as well. For some reason a lot of beginners skip them idkw but there are answers on almost all early questions about the language and its ecosystem

They probably want to write code 😛

yeah, sure

ok, so I've jumped down the clj rabbit hole. I'm now trying to serve a repl via a socket using the instructions in that page. Unfortunately, anything that tries to connect to the socket just hangs without error. Running the server manually in the repl also yields no errors. Here's the code:

user=> (clojure.core.server/start-server {:name "foo" :port 5555 :accept 'clojure.core.server/repl :server-daemon false})
#object[java.net.ServerSocket 0x1869f114 "ServerSocket[addr=localhost/127.0.0.1,localport=5555]"]
user=>

Works on my end just fine:

$ clj
Clojure 1.11.1
user=> (clojure.core.server/start-server {:name "foo" :port 5555 :accept 'clojure.core.server/repl :server-daemon false})
#object[java.net.ServerSocket 0x5a12c728 "ServerSocket[addr=localhost/127.0.0.1,localport=5555]"]
user=>

$ telnet 127.0.0.1 5555
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
user=> 1
1
user=> 2
2
user=> 

But also, that seems to be completely unrelated to your initial question as you don't need a socket REPL for that - a plain local REPL works just fine, one that you used to call start-server in the first place. So if you for some reason still want to launch a socket REPL and can't do it, I'd suggest asking a separate question so that more people see it. Or maybe there's already some answer here - I'd try searching on Slack as well.

The socket repl is so that I can use it with my IDE

I'll try a different port but I thought 5555 was in the safe range

just run from the shell clj -J-Dclojure.server.repl="{:port 5555 :accept clojure.core.server/repl}"

btw which editor are you using?

vim with Fireplace

then you need to follow instructions to setup cider-nrepl first

I've been using that and lein repl :connect localhost:5555 as a client. I don't have telnet installed but I'll try something like that in a mo

https://docs.cider.mx/cider-nrepl/usage.html#via-clj

Hmm, that might be necessary, although I've been connecting to lein repl just fine. I think that stuff's for more advanced features

ok, so I can connect with netcat, so I guess I'll try setting up cider

oh, I'm under the misaprehension that nrepl means clojure.core.repl over a network and it doesn't. It's a separate package. This might be the reason I can't connect

Thanks everyone who helped. Got everything sorted. This was my final deps.edn. I think it would have also worked with nrepl/nrepl in place of cider/cider-nrel but I figured the Cider stuff will be useful eventually

{:paths ["src"]
 :aliases {:cider-clj {:extra-deps {org.clojure/clojure {:mvn/version "1.10.1"}
                                    cider/cider-nrepl {:mvn/version "0.28.5"}}
                       :main-opts ["-m"
                                   "nrepl.cmdline"
                                   "--middleware"
                                   "[cider.nrepl/cider-middleware]"]}
           }}}}

Can you provide repro with more detail?

Here is the minimal example:

user> (ns namespace-1 (:refer-clojure :exclude [dec]))
nil
namespace-1> (def dec #(- % 1))
#'namespace-1/dec
namespace-1> (ns namespace-2)
nil
namespace-2> (ns namespace-2)
nil
namespace-2> (ns-unmap *ns* 'dec)
nil
namespace-2> (require '[namespace-1 :refer [dec]])
nil
namespace-2> (ns namespace-2)
WARNING: dec already refers to: #'namespace-1/dec in namespace: namespace-2, being replaced by: #'clojure.core/dec
nil
namespace-2> 

Yes, above, I've just replaced previous much longer example with the simpler one.

I reload namespace in Emacs via cider-load-buffer (C-c C-k).

which calls ns form every time.

I think that can be slimmed down a bit more:

(ns namespace-1 (:refer-clojure :exclude [dec]))
(def dec #(- % 2))
(ns namespace-2)
(require '[namespace-1 :refer [dec]])

WARNING: dec already refers to: #'clojure.core/dec in namespace: namespace-2, being replaced by: #'namespace-1/dec

(ns namespace-2)               ;; warns

WARNING: dec already refers to: #'namespace-1/dec in namespace: namespace-2, being replaced by: #'clojure.core/dec

and in both warning cases, you can resolve this by using (ns namespace-2 (:refer-clojure :exclude [dec]))

Right, but the issue is (again) with fastmath.core/use-primitive-operators (or primitive-math/use-primitive-operators) which is convenient way to inject replacements for set of operators.

User does not know what is injected.

(usually)

The solution is to call unuse-primitive-operators at the end of the namespace, but...

seems right to me

Possibly other libraries use similar trick to replace vars. I don't know how this namespace manipulation method is common. If it's only fastmath I can deal with it. I mean, I can reorganize the code to avoid warnings in fastmath and related libs.

the first warnings exists with 1.11 too, that's not new

Yes, true, fastmath.core uses :refer-clojure :exclude cause I know what is going to be redefined. Also primitive-math does (https://github.com/clj-commons/primitive-math/blob/master/src/primitive_math.clj#L3)

no

you just walk to the end

if you never finish, then it's infinite

I see, any alternatives to calling count on a possibly infinite seq?

bounded-count ?

https://clojure.github.io/clojure/clojure.core-api.html#clojure.core/bounded-count

thanks @U064X3EF3, that may be a good option

as a note, bounded-count can't protect you from infinitely empty lazy sequences:

;; runs forever
(bounded-count 0 (filter (constantly false) (range)))

Perhaps https://github.com/exoscale/ablauf?

Or maybe add things to do to a queue? and take them of the queue as you go?