cursive

Issues at: https://git.io/cursive-issues
cfleming 2020-09-02T05:27:59.009500Z

https://twitter.com/CursiveIDE/status/1301028728244330496

🎉 7
cfleming 2020-09-02T05:28:28.009700Z

@p-himik This contains the switch to turn off hiccup conversion you asked about.

p-himik 2020-09-02T05:31:06.009900Z

Awesome, thanks!

2020-09-02T06:32:54.012600Z

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

cfleming 2020-09-02T21:40:51.018200Z

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
1
2020-09-02T15:36:39.013800Z

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

2020-09-02T15:36:47.014100Z

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

borkdude 2020-09-02T15:37:11.014500Z

@cfleming Does Cursive have a similar thing to this? https://github.com/borkdude/clj-kondo/issues/872#issuecomment-685781515

2020-09-02T15:39:10.014900Z

Wait I think I found it

2020-09-02T15:40:54.015300Z

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

2020-09-02T15:41:02.015500Z

pretty printer didn’t like it

2020-09-02T15:41:07.015700Z

all good here, ty

cfleming 2020-09-02T21:24:15.015800Z

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

2020-09-02T21:25:10.016Z

It was an invalid keyword: :@timestamp

2020-09-02T21:25:21.016200Z

It plain-printed the response form.

2020-09-02T21:25:34.016400Z

No colorization, no indentation.

2020-09-02T21:26:08.016600Z

tbh it made sense once I figured out what was up

2020-09-02T21:26:52.016800Z

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

cfleming 2020-09-02T21:28:02.017Z

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.

borkdude 2020-09-02T21:28:36.017200Z

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

cfleming 2020-09-02T21:28:40.017400Z

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

borkdude 2020-09-02T21:29:13.017600Z

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

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

cfleming 2020-09-02T21:32:32.018Z

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.

2020-09-02T21:57:29.018400Z

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.

cfleming 2020-09-02T23:12:17.018600Z

:hail_mary: