Fork me on GitHub
#cursive
<
2020-06-09
>
salam01:06:42

the following is another exception that obscured the underlying problem with my code that calls cognitect's aws-api s3 api. in my case, the problem was simply a missing bucket name.

steveb8n05:06:40

@cfleming I’ve started using https://github.com/amperity/greenlight and have found it to be a great addition to my toolset

steveb8n05:06:19

using it in cursive has been good but there’s a couple of test integration quirks. do you have any interest in knowing about these?

cfleming08:06:21

Sure, feel free to file an issue and I’ll take a look.

thumbnail07:06:37

Hey! I’m using the debugger (cool stuff btw!), but i can’t seem to evaluate expressions (am inside a java library). :thinking_face:

cfleming08:06:01

That’s https://github.com/cursive-ide/cursive/issues/2345, which is fixed in the latest EAP but not the latest stable build yet. If you’d like to try the EAP builds see here: https://cursive-ide.com/userguide/index.html#eap

3
reefersleep08:06:32

Is there some smart way to start two REPLs in Cursive without having to wait for one to get the prompt before you start the other? In my work project, I mostly work with a CLJS REPL for the frontend and a CLJ repl for the backend. If I start them immediately after each other, they’ll occupy the same window, which is unusable. Therefore, I have to wait until one gets a prompt before I can start the other.

cfleming08:06:25

Unfortunately, not easily, no. That’s top of my large-things-to-fix list, along with a lot of other REPL experience improvements.

reefersleep09:06:18

Cheers @cfleming, looking forward to it 🙂

Vachi14:06:04

hi everyone, it is possible to wrap the forms sent to the repl to be evaluated with a function? like tap> , so any form that we send to the repl would be evaluated as (tap> form)

imre14:06:34

You could create a repl command that does this, see https://cursive-ide.com/userguide/repl.html#repl-commands

Vachi15:06:24

many thanks! that was exactly what I needed

Vachi15:06:00

(tab> ~top-level-form) did the job

salam19:06:42

i'm curious how everybody's experience with using a remote socket repl with cursive is. we've been having problems with this set-up. one particular problem that we had today was that the cursive repl client wouldn't show the output from expound. that is if you evaluate (expound/expound string? 42), all you get in the repl client output is nil. am i missing something?

salam20:06:05

here's extra context. it seems like a flushing issue with the output stream?

salam21:06:13

we had to evaluate (prn) to "force" cursive to flush the output stream. this also applyes to clojure.spec.alpha/explain.

cfleming22:06:04

Ok, I’ll look at that, thanks.

thheller20:06:38

how come the "execute in original ns" is always grayed out? how do I get that to be available?

cfleming22:06:37

So that “execute in original namespace” is when you’re repeating a previous command. There actually isn’t an option for “execute in file namespace”, but I will add one.

12
❤️ 4
thheller07:06:15

ah ok. the in-ns trick works fine for my purposes too.

serioga13:06:01

in-ns works... but when I change REPL ns via command the indicator of current ns remains unchanged 😞

thheller20:06:33

ah nvm. just using (in-ns '~file-namespace) (tap> ~top-level-form) also works.

aw_yeah 4