Fork me on GitHub
#cursive
<
2020-06-23
>
wilkerlucio15:06:58

hello, I'm having an issue with protocols, I did define one and using it, but Cursive is complaining about the wrong signatura, but the signature is correct:

wilkerlucio15:06:32

the code loads and runs fine, but I don't understand why Cursive is complaining about it, a bug?

cfleming21:06:04

I think the problem is that it’s not managing to parse the defrecord form. The arity warning means that Cursive thinks that form is an invocation. Is this public somewhere I could take a look at?

wilkerlucio21:06:37

one strange thing, for the clojure.lang.IFn it did recognized correctly

wilkerlucio21:06:48

maybe the problem is that I have the protocol and the record on the same file? (and that may be confusing Cursive, also its a cljc file)

henryw37415:06:27

when I type a ; on a line in cursive, the semicolon and the line content after that jumps over to the right. anyone know if there is a way to stop it doing that?

cfleming21:06:57

Yes, setting the comment alignment setting that @U06CM8C3V mentioned to 0 should work.

henryw37408:06:46

gottit thanks. for some reason it was on 80! no idea if I set that or not

manutter5117:06:24

In the preferences, under Editor > Code Style > Clojure, on the General tab, there’s an option for “Comment alignment column,” you might want to play with that.

❤️ 6
tony.kay17:06:08

I’m having troubles with dependency autocomplete again. Seems to die periodically as we go from version to version. I’m on latest everything. Is this known broken? I’ve tried invalidating caches and restarting. Maven remote repos has maven central and clojars, as does the remote jar repos. When I try autocompelte in a deps file I just get nothing:

cfleming21:06:44

Yeah, sorry, the underlying API changes a lot here, it’s being actively worked on and they seem to break the invariants around it a lot. Someone else reported this the other day, I’ll try to look at it today.

imre18:06:32

I'm finding lately that when hovering over failed test assertions with large diffs, the IDE freezes for a while, depending on the size of the diff.

3
imre18:06:33

this is rather limiting as currently the only way to check an assertion diff is to hover (or view->error description) and click the link at the bottom of the tooltip

cfleming21:06:31

You can also click the icon in the gutter as long as there’s only a single test result per line, but yes, this is not ideal and I plan to fix it soon.

imre21:06:38

Oh yeah, forgot the gutter as I have it hidden

imre21:06:43

that's a lot better when clicked from there

imre21:06:09

I just don't like the gutter really as it takes up a lot of screen real estate

cfleming00:06:19

Yeah, it’s not ideal and I have plans for a much better solution but I’m struggling to get to it 🙂