Fork me on GitHub
#cursive
<
2020-09-02
>
cfleming05:09:28

@U2FRKM4TW This contains the switch to turn off hiccup conversion you asked about.

p-himik05:09:06

Awesome, thanks!

Nick Cernis06:09:54

Thank you for Cursive. I bought a licence and really like it. Does Cursive accept bounties via https://www.bountysource.com/ or similar? Some issues I'd be willing to put money towards if it helped to prioritise their development: • Inline form evaluation (this is my most-missed feature from other editors): https://github.com/cursive-ide/cursive/issues/391 • Shadow CLJS support: https://github.com/cursive-ide/cursive/issues/1804 • Test runner: https://github.com/cursive-ide/cursive/issues/247

cfleming21:09:51

Hi Nick, thanks for the kind words, I’m glad you’re liking Cursive! There’s no bounties for Cursive, simply because money isn’t the limiting factor, my time is. However those three issues are on my shortlist to get fixed ASAP, so I hope they’ll be there soon.

❤️ 1
thanks3 1
potetm15:09:39

@cfleming After updating this morning, I’m not getting colorization/formatting on some REPL evaluations.

potetm15:09:47

I can’t quite figure out what the pattern is.

cfleming21:09:02

It doesn’t, but it should. There’s some debate about what they should look like too, since not all forms accept metadata. Possibly something like #_:no-unused-symbol before the form for those cases.

borkdude21:09:36

@cfleming That's exactly the discussion I'm having in that issue. Maybe we could come up with a common format

borkdude21:09:13

Instead of the uneval (which also came along in the issue) I've also proposed:

^{:clj-kondo/ignore-nth 1} (foo "bar" (baz ...))

cfleming21:09:32

Ok, I’ll think about it - I’ve actually just been adding some inspections and missed being able to disable them. I’ll check what IntelliJ provides/requires for this as well, since that may limit my possible solutions.

potetm15:09:10

Wait I think I found it

potetm15:09:54

Yeah, there was a key in the response that started with an @

potetm15:09:02

pretty printer didn’t like it

cfleming21:09:15

Interesting, what did those look like? I can have a go at fixing that.

potetm21:09:10

It was an invalid keyword: :@timestamp

potetm21:09:21

It plain-printed the response form.

potetm21:09:34

No colorization, no indentation.

potetm21:09:08

tbh it made sense once I figured out what was up

potetm21:09:52

But I updated the EAP today, and Jumped To Conclusions!™

cfleming21:09:40

Ah, I see - yes, unreadable keywords can cause interesting issues 🙂

potetm21:09:29

I was once on a crusade to un-keywordize all json. Sheer momentum put a stop to it, and now I, for one, welcome the pile of unnecessary errors I will live with forever and ever amen.

cfleming23:09:17

:hail_mary:

potetm15:09:07

all good here, ty