When I run clojure -Sdescribe I get a map with symbols as keys instead of keywords. Any idea why? (macOS, clojure installed with homebrew)

❯ clojure -Sdescribe
{ version "1.11.1.1182"
  config-files ["/usr/local/Cellar/clojure/1.11.1.1182/deps.edn" "/Users/thomas/.clojure/deps.edn" ]
  config-user "/Users/thomas/.clojure/deps.edn"
  config-project "deps.edn"
  install-dir "/usr/local/Cellar/clojure/1.11.1.1182"
  config-dir "/Users/thomas/.clojure"
  cache-dir "/Users/thomas/.clojure/.cpcache"
  force false
  repro false
  main-aliases ""
  repl-aliases ""}

are you sure the : just isn't printing for some reason? there is a suspicious space in front there

not sure at all 😛

the only reason it bothers me is that Cursive-IDE is not working because of this

if you have hexdump something like clojure -Sdescribe | hexdump -b|head -1 | awk '{print $3}' should print 072 (octal for ':')

but I would expect if it is just a printing issue it wouldn't bother cursive

the result of that command is 040

user=> (char 040)
\space
user=>

so it is what it is, weird

I would check your clojure script

looks like that map should come pretty directly from here https://github.com/clojure/brew-install/blob/1.11.1/src/main/resources/clojure/install/clojure#L464-L475

looks the same

that's .... pretty weird

yup

oh well. thanks for helping out. I’ll leave it for a while. Not in a hurry 🙂

maybe try a different terminal?

something with encoding?

good idea. I tried both Terminal and iTerm now, but the result is the same

I would try editing the map in the clojure shell script (add an extra key or something) and see if it prints out when you run -Sdescribe again

added a :lol which becomes lol when printed 😬

fascinating

well it is Halloween, probably a ghost

is /usr/bin/env bash --version actually bash?

what shell are you using ( echo $0 )?

I’m using fish.

❯ /usr/bin/env bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin21)
Copyright (C) 2007 Free Software Foundation, Inc.

Fish uses spaces to define lists (e.g. a PATH in fish is separated by spaces, not colons). To be backwards compatible with bash, there are code paths that will automagically swap between colons and spaces. From the docs: > Variables whose name ends in “PATH” are automatically split on colons to become lists. They are joined using colons when exported to subcommands. This is for compatibility with other tools, which expect $PATH to use colons. I suspect @tskardal may be hitting some weird corner case. 😅 Note: I am not a fish user, but did try looking this up out of curiosity. :)