Okay, it's an issue with the rlwrap script.
System clojure (Debian bullseye):
ehashman@fedora:/tmp/app$ clojure Clojure 1.10.2 (map inc [0 1 2]) (1 2 3) user=>
With a copy of the Clojure CLI wrapper script set to use upstream Clojure binaries instead of the system ones:
ehashman@fedora:/tmp/app$ ./clojure Clojure 1.10.2 (map inc [0 1 2]) (1 2 3) user=>
Running those upstream ones directly with java:
ehashman@fedora:/tmp/app$ java -cp /home/ehashman/.m2/repository/org/clojure/clojure/1.10.2/clojure-1.10.2.jar:/home/ehashman/.m2/repository/org/clojure/core.specs.alpha/0.2.56/core.specs.alpha-0.2.56.jar:/home/ehashman/.m2/repository/org/clojure/spec.alpha/0.2.194/spec.alpha-0.2.194.jar"$extra_classpath" clojure.main Clojure 1.10.2 user=> (map inc [0 1 2]) (1 2 3) user=>
Running Debian's jar directly:
ehashman@fedora:/tmp/app$ java -cp /usr/share/java/clojure.jar clojure.main Clojure 1.10.2 user=> (map inc [0 1 2]) (1 2 3) user=>
Okay, it's an issue with the rlwrap script.
System clojure (Debian bullseye):
ehashman@ fedora: /tmp/app$ clojure
Clojure 1.10.2
(map inc [0 1 2])
(1 2 3)
user=>
With a copy of the Clojure CLI wrapper script set to use upstream Clojure binaries instead of the system ones:
ehashman@ fedora: /tmp/app$ ./clojure
Clojure 1.10.2
(map inc [0 1 2])
(1 2 3)
user=>
Running those upstream ones directly with java:
ehashman@ fedora: /tmp/app$ java -cp /home/ehashman/ .m2/repository/ org/clojure/ clojure/ 1.10.2/ clojure- 1.10.2. jar:/home/ ehashman/ .m2/repository/ org/clojure/ core.specs. alpha/0. 2.56/core. specs.alpha- 0.2.56. jar:/home/ ehashman/ .m2/repository/ org/clojure/ spec.alpha/ 0.2.194/ spec.alpha- 0.2.194. jar"$extra_ classpath" clojure.main
Clojure 1.10.2
user=> (map inc [0 1 2])
(1 2 3)
user=>
Running Debian's jar directly:
ehashman@ fedora: /tmp/app$ java -cp /usr/share/ java/clojure. jar clojure.main
Clojure 1.10.2
user=> (map inc [0 1 2])
(1 2 3)
user=>