Fork me on GitHub
#cider
<
2016-05-31
>
bhauman00:05:06

@gastove: I think you may be assuming things, you can't just launch a cljs repl.

bhauman00:05:29

you need figwheel or something to do all the wiring for you

bhauman00:05:32

and there is a lot of wiring

gastove00:05:33

…..huh. Well… that damn sure would expain my “no repl” results. I also definitely got the impression from the cider docs that cider would “do the right thing” — given a couple deps (piggieback, for instance) it would fire up a rhino repl for you.

bhauman00:05:57

hmmmm, well, I don't know enough to answer that

bhauman00:05:35

I guess piggieback should fire up a rhino repl for you

bhauman00:05:33

nope doesn't look like it at all

bhauman00:05:02

and they give you three options to start a repl service

bhauman00:05:36

really either weasel, or figwheel

bhauman00:05:56

@malabarba: I'd love to chat sometime about nREPL messages for ClojureScript compile warnings as well as Compile Exceptions.

gastove00:05:18

Oh lord, got it — something about clj-refactor is interfering with starting the clojurescript repl.

gastove00:05:32

bhauman: you probably already know this, but figwheel is neat as heck 😄 Thank you so much for it!

gastove00:05:49

And thanks for taking the time to help debug things. Whee, debugging.

bhauman00:05:06

Thanks! Glad you like it!

malabarba01:05:10

@gastove: make sure you're up to date on all of these packages

malabarba01:05:24

And even if you are, try upgrading them

malabarba01:05:47

I mean. Try reinstalling them

malabarba01:05:52

@bhauman sure. You mean like getting cljs exceptions to display like we display Clojure exceptions?

malabarba01:05:58

That would be pretty nice

gastove05:05:43

malabarba: ah, yep. Blowing away and re-installing clj-refactor and refactor-nrepl seem to have done it. Thanks!

bhauman13:05:27

@malabarba: yeah, actually there are 3 different things here, javascript runtime exceptions and this should be pretty easy to fix.

bhauman13:05:21

Then compiler exceptions, these are syntax and reader errors and often come with column and line information along with a brief explanation.

bhauman13:05:26

Then there are compiler warnings. There can be multiple warnings per compile and these come with a description and location information as well.

malabarba18:05:31

@hans: Turns out it's not a cider bug. Dots in var names is simply not supported. Or maybe it's a bug in clojure.core.

malabarba18:05:05

Just boot up a plain lein repl. Then evaluate (def a.a 1). And try to evaluate (resolve 'a.a).

malabarba18:05:15

The resolve will throw an exception.

malabarba18:05:21

@bhauman: Handling this stuff on the Emacs side should be simple. In fact, all of the exceptions should be trivial, only the warnings might be more work.

malabarba18:05:50

It's the nrepl side that I have *no idea* how to do

malabarba18:05:59

I mean. I understand how nrepl works

bhauman18:05:08

I got the nrepl side

malabarba18:05:23

But when you throw cljs and piggieback in the middleway, I'm in dark waters . 🙂

bhauman18:05:24

I understand the piggieback code intimately now

bhauman18:05:52

I can make cljs-only response messages

malabarba18:05:02

@bozhidar: should probably be a part of this too

malabarba18:05:18

And maybe we should move this to a github issue

bhauman18:05:32

yeah makes sense

malabarba18:05:37

This slack has a very short history 🙂

bhauman18:05:42

yeah it does

malabarba18:05:03

OK. I'll create an issue for it and ping you

bhauman18:05:04

excellent!

malabarba18:05:52

The link, in case anyone else was following the conversation: https://github.com/clojure-emacs/cider/issues/1771

hans18:05:52

@malabarba: interesting. thank you for the clarification. i wonder if there is a formal definition of the characters that a symbol may contain. clojure should probably refuse to use unsyntactic symbols in any case.

malabarba18:05:19

@hans The only definition is the source code AFAIK

malabarba18:05:30

But you're right, it's a clojure bug either way

malabarba18:05:49

Either the reader shouldn't take it, or resolve shouldn't barf with it

hans19:05:41

@malabarba: case closed, thanks 🙂