Hello, i've got a macro that is a thin wrapper around fn, but in the 'resolve as' menu I can't find fn. How can I do?

@pbaille So I still haven’t fixed this so you can enter arbitrary vars to resolve as, sorry. There’s a workaround you can use by hacking config files here: https://github.com/cursive-ide/cursive/issues/1440#issuecomment-232776904

It’s a bit ugly sorry.

@cfleming thank you I will try this

@cfleming by the way, have you got an idea when the standalone version of cursive will be available?

@pbaille Not really, the install process is pretty easy these days so it’s less compelling.

I do still want to do it but it’s a lower priority than it was. Do you have a case where it would be useful?

no i was just wondering 🙂

Ok - I do want to do it, in particular a simpler version (or a version that could easily be configured to be simpler) for educational purposes is a use case I’d like to support.

Something more like DrRacket

Keybindings have also been an awkward part of setup but should be much easier in the next release.

ok I see, Personally I find cursive pretty simple to setup these days.

Yeah, that’s mainly why I’ve de-prioritised the standalone version. It’s a complicated thing to set up that is not at all documented by JetBrains, and it’s unclear how a non-JetBrains standalone would update itself etc.

I've got another question: I'm wondering why repl evaluated forms doesn't print the same that when wrapped in a 'println' call, specifically \newline chars looks to be omitted

i've noticed that print-method is called with a stringwriter instead of a printwriter when I send an expr to the cursive repl

Umm, I’m not sure why that would be the case. Cursive doesn’t mess with how print-method etc work, but since Cursive parses + pretty-prints the output on the client side, the results are sometimes different from what you might expect.

If you have a concrete example of something unexpected I can take a look at it.

i cannot see newlines when I evaluate this

Right.

this is really a dummy exemple

Here’s what’s happening.

nREPL just returns eval values back to the client as pr-str‘ed strings.

and it works in this case:

Cursive, in order to pretty print them, will try to parse them as Clojure data structures and then print the parsed version using fipp. What’s happening in your case is your output is correctly parsed as a form and then pprinted, but it all fits on one line so that’s how it’s printed.

ok I see

it treat it as a list

in the first case

You can disable that if you like in Settings->Languages & Frameworks->Clojure->Pretty print REPL return values

I like the pretty colors 🙂

But then none of your results will be formatted unless you install a middleware or something.

I don't want to remove it

Right 🙂

In your second example, the newlines are preserved because you essentially have 3 top level forms.

maybe I can extend some fipp stuff?

So unfortunately it’s not extensible at the moment, because it’s built in to Cursive. I’m planning to allow it to be extended, but I’m not sure how that will work yet.

okok I see

thank you!

and if I disable pretty print repl, can I insert fipp myself as a nrepl middleware?

if it makes sense 🙂

Yes, you can - I think https://github.com/greglook/whidbey is what you want.

I believe there’s something similar which just uses pprint, too.

ok that's great, I will look at this

thank you a lot

No problem, let me know if you run into trouble - I’m not sure many people are using whidbey with Cursive, so I’d be interested to know how it goes.

ok I will tell you

I've just tried, I can't make it works. I've added whidbey stuff in my profiles.clj. It works as intended when used at the terminal with 'lein repl'. but doesn't works in cursive repl (i've unchecked Pretty print REPL return values). Also i've tried to check whidbey in profiles (lein intellij panel) but nothing seems to do the trick.

@pbaille Hmm, ok - I’ll take a look at that tomorrow. Could you file an issue to remind me?

sure!

@cfleming double shift search find my project/my_namespace but not project.my-namespace... It's a know bug?

@souenzzo Sort of - unfortunately the double shift search isn’t extensible. So the only way I can contribute to it is to use symbols, which isn’t great for namespaces.

That means namespaces will also show up in the Find symbol… search, which you almost certainly don’t want.

Actually, looking at it, IntelliJ does actually add classes to the Find symbol… dialog. So perhaps I should add namespaces there too.

@souenzzo Could you file an issue for that and I’ll add them there?

I guess that means that keywords should probably go there too