Fork me on GitHub
#calva
<
2019-04-13
>
pez07:04:12

@hoppy: stuff you evaluate in the repl window will print stdout in that window. Stuff you evaluate inline will print in the Calva says output channel.

hoppy12:04:59

what I'm asking is where does what the compiled progam output go (stdout) That's what I can't find

pez10:04:13

Do we have any Emacs users in here who can tell me if there is some in-file symbol navigation in CIDER? This PR: https://github.com/BetterThanTomorrow/calva/pull/163 has started to add this to Calva, and I would like to know a bit about how it is implemented elsewhere. Specifically, I’d like to know what happens when lines are removed or added to the file. The ns-vars op seem to operate on the last evaluated information it has on the ns, which makes sense, but makes the symbol navigation a bit strange in the edited case.

pez11:04:42

This build has @alexander.minolta’s fix for making files in eval error messages clickable, adds paredit grow/shrink selection to repl window, renames some commands based on feedback in this channel and fixes a bug with the wrong repl window being opened for “send to repl” commands.

pez12:04:53

That was what I answered on. 😃 Maybe there is a bug?

pez12:04:14

Is it clj or cljs you have trouble with?

hoppy12:04:00

this is clj

hoppy12:04:43

I'm not sure we are understanding each other. you are talking about eval'ing, and all of that is fine.

hoppy12:04:26

I'm talking about I'm running a web server, that for example, prints the client request (via println)

hoppy12:04:46

I'm sitting in the repl with this, hit it with a rq, and the printlin happens, but the output goes nowhere

hoppy12:04:04

or at least nowhere I can glean

pez12:04:44

So, if you eval (println "foo") all is fine, but the stdout side effects happening in your webserver do not show up?

pez12:04:14

Have you jacked-in or just connected?

hoppy12:04:18

jacked in

pez12:04:37

See if you see anything in the “Calva Jack-in” output channel.

hoppy12:04:07

I recall doing that, but just wakin up here, so let me take another look

pez13:04:20

If you inline eval, you do not get the prints either?

pez13:04:59

It seems the source maps from the cljs compiler have improved. I can step through Calva’s cljs code in the vscode debugger (Chrome debugger, I think).

hoppy13:04:20

the difference seems to be whether we are in an eval or not. I'm assuming the output comes back while nrepl is doing that work for us. Stuff that arises spontaneously (aka we are not in an nrepl transaction) is never seen.

hoppy13:04:40

calva connect or jack-in no difference.

hoppy13:04:17

if I connect with cider, I get identical behavior. It neither pops out of the repl console, nor does it find its way back to emacs.

hoppy13:04:05

I recall using this technique when jacked in with cider, but in that case it's a subprocess of emacs, so that is what is different.

hoppy13:04:37

Unfortunately, My emacs is roasted atm to prevent jack-in - I need to go see if that has been updated

hoppy13:04:47

(piggieback won't compile in the jack-in)

hoppy14:04:57

I don't think there is anything actionable on the calva side

pez15:04:19

@hoppy: Calva Jack-in doesn’t work because of piggieback not compiling.

hoppy15:04:58

calva jack in does work for jack in, it's my cider that is currently messed up after upgrading it.

hoppy15:04:32

but the good news is, its been broken for a week, and I've not cared enough to fix it because calva is working that good

pez15:04:08

There is something going on with piggyback, try adding the dependency to your project.clj and it will probably start to work in Emacs too.

pez15:04:44

About stdout. Did you get any output in the jack-in channel?

pez15:04:59

That’s a bit strange