Fork me on GitHub
#cider
<
2016-03-20
>
fommil08:03:18

@malabarba: very weird, it worked on my laptop and I have exactly the same emacs config there

bozhidar09:03:32

well, clearly something is not exactly the same simple_smile

ericnormand13:03:46

has anyone seen this one while running tests:

ericnormand13:03:50

> error in process filter: Wrong type argument: stringp, nil

ericnormand13:03:26

I'm using cider 0.11.0

ericnormand13:03:03

I could run tests in a different project on friday

ericnormand13:03:08

I didn't upgrade anything

ericnormand13:03:30

the tests had no assertions

ericnormand13:03:33

I'll file a bug

bozhidar13:03:12

I think we already fixed this on master

bozhidar13:03:18

but you might want to double check this

fommil14:03:35

I use this package in Emacs https://github.com/nschum/highlight-symbol.el but M-x highlight-symbol occurrences are ignored in clojure code. Very bizarre.

fommil14:03:40

oh wow, cider is being too smart

fommil14:03:25

if I mark a symbol, e.g. an import from :as http then highlighting http doesn't show http/request usages. I guess that's actually pretty neat. I just need to remember this caveat.

malabarba14:03:12

I don't think that's cider. simple_smile

malabarba14:03:33

http, and http/request are different symbols

malabarba14:03:28

Highlighting all occurrences of the http symbol isn't going to highlight http/something

malabarba14:03:39

Bit maybe I misunderstood something

fommil14:03:36

yes, that's what I concluded

fommil14:03:01

in other languages the http part would be seen a separate symbol to the qualifier

fommil15:03:47

this is probably clojure mode, it must define / to be a legal symbol character. Whereas in, e.g. Java or Scala, the namespace separator (`.`) has a separate semantic meaning.

bozhidar15:03:11

when it's eventually done it will provide a much smarter highlighting than what could be achieved by a generic package

arrdem15:03:58

that'll be awesome.

fommil18:03:40

@bozhidar: well I guess ENSIME better catch up 😛 (we can actually do this in the backend now, just never thought to do it)