cider

A channel dedicated to the Clojure Interactive Development Environment that Rocks (aka CIDER). :cider:
grzm 2020-08-25T00:53:22.016300Z

I ssh from a macOS box into an Ubuntu box and run Emacs there. On the remote Ubuntu box, I upgraded Emacs to 27.1 via nix-env. cider-connect-clj is now failing straight away with Searching for program: No such file or directory, /usr/bin/security AFAIK /usr/bin/security is only macOS thing. google hasn’t been helpful. I’ve recompiled my elpa packages. I’ve grepped my entire home directory for /usr/bin/security How should I got about further debugging this?

grzm 2020-08-25T00:55:20.016500Z

I suspect I’m missing the forest for the trees, so I’m hoping there are some lumberjacks out there.

dpsutton 2020-08-25T01:13:54.017300Z

any chance you can completely remove CIDER from the equation? run whatever startup command CIDER is trying to run on the linux box

ag 2020-08-25T01:19:04.018200Z

interesting, apparently, if you try to cider-debug-defun-at-point while you already in debugging mode - CIDER gets a bit confused.

grzm 2020-08-25T01:38:37.018400Z

My emacs debugging isn’t what it could be, but by evaling (cider-connect-clj '(:host "localhost" :port 3188)) directly in a scratch buffer rather than interactively (via M-x), it works.

grzm 2020-08-25T01:45:54.018700Z

Hmm. I think it might be a change in auth-sources. I’ve got mac-os-keychain stuff in there in my common emacs config. Earlier versions didn’t seem to care so much about it. /usr/bin/security is related to macOS keychain access.

grzm 2020-08-25T01:46:06.018900Z

Thanks for the prompt and the push, @dpsutton!

1
grzm 2020-08-25T01:47:53.019200Z

Confirmed: removing that part of my init.el cleared the errors.

grzm 2020-08-25T01:48:16.019400Z

thanks Clojure once again for its stability across upgrades

bozhidar 2020-08-25T06:52:44.019700Z

🙂

bozhidar 2020-08-25T06:52:59.020100Z

@ag What happens?

ag 2020-08-25T14:37:30.022700Z

for me it just blocks Emacs. You can get out of it with C-g, it's not a big deal.

Casey 2020-08-25T08:13:00.021900Z

Occasionally it happens that some operation goes wrong, and a huge pile of SQL or other data is spilled into my cider repl buffer. This almost always causes emacs to go unresponsive, leading to a necessary kill -9 emacs . What options are available to me to deal with this, while not disabling the log entirely?

dpsutton 2020-08-25T12:34:57.022600Z

I’ve taken to not subscribing to out and failing logs elsewhere