unrepl 2018-02-01 | Slack Archive

> though with cider I have to jump through hoops to get code navigation working

Supposedly we fixed this recently. I never develop over remote connections, that’s why I didn’t notice for a while something was broken there.

bozhidar06:02:55

FYI https://github.com/clojure-emacs/cider/issues/2148

j0ni18:02:54

It's been a while, it may be fixed. I will try it on a locally running docker-compose setup. The problem always used to be mapping local paths to remote paths, and the nasty solution was to do something like sudo ln -s /path/to/my/local/workspace /app or whatever the remote path is to the code. Not sure how that relates to a running jar with no remote copy of the repo now I think about it...

bozhidar06:02:21

The problem with having too many features that are hard to test with unit tests is that it’s relatively easy to break something without noticing it.

cgrand14:02:06

speaking of ssh etc. I never thought about this before but ssh [email protected] nc localhost 5555 is a possibility

cgrand14:02:34

no?

j0ni18:02:53

I'm trying to start a new repl from inside emacs, but spiral-connect-to and spiral-connect seem to be behaving identically

j0ni18:02:23

they both are prompting me for a host and port

volrath18:02:58

spiral-connect prompts when it cannot recognize a clojure project for the buffer you're visiting

volrath18:02:13

maybe you are in a temporal buffer? or outside a clojure project

j0ni18:02:36

yeah that would be it

j0ni18:02:42

I'm in a directory with a deps.edn in it

j0ni18:02:46

getting a ton of these now

error in process filter: parseclj-unparse-clojure: Wrong type argument: char-or-string-p, nil
error in process filter: Wrong type argument: char-or-string-p, nil
error in process filter: parseclj-unparse-clojure: Wrong type argument: char-or-string-p, nil
error in process filter: Wrong type argument: char-or-string-p, nil

j0ni18:02:09

might be due to running with a dev build of emacs

volrath18:02:29

oh...

volrath18:02:36

hmm that's new..

volrath18:02:13

I tried it in emacs 27 a few months ago but I don't know if there might be something new that breaks spiral

volrath18:02:20

when exactly are you getting those errors?

j0ni18:02:30

to begin with when I connected to the repl I'd started on the command line using the clj line from spiral's readme (the code file has only a ns declaration, no requires or code yet)

j0ni18:02:35

then I saw 2 instances

j0ni18:02:51

as I started typing a (require [... line into the repl, I saw a lot more

j0ni18:02:24

got as far as (require '[com.]) and saw 12 pairs of those errors

volrath18:02:34

sounds like it might be related to completion

j0ni18:02:41

yeah

volrath18:02:59

are you running emacs master branch?