This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
Is there a way of getting cursive to treat with def*
(e.g. om’s defui
) forms like def/defn
forms in terms of formatting and var declaration?
@lfn3: Not right now, sorry, but I’m going to add that soon, for simple cases at least.
Ok. Cool. That’s one of the only things that bugs me about cursive, is the occasional formatter fighting I have to do.
Yeah, that and the resolution can be annoying depending on the libraries you’re using.
Agreed. Is this: https://github.com/cursiveclojure/cursive/issues/147 the issue I should be paying attention to re this?
Globally, I think. That config will be the same for those forms in all projects I think, right?
Yeah. So long as the names are fully qualified to an upstream jar then you shouldn’t ever see stuff clashing. I presume that’s possible, of course.
Right. Cursive actually sends back some anonymous usage stats if you haven’t turned that off (basically Cursive version, IntelliJ version and OS). I’m planning to send these lists back as part of this, so I can prioritise which support needs adding based on actual usage, plus I can ship a combined list with Cursive.
No worries. I’m busy right now getting ready for the conj, but I’d like to do this right after that.
Cool. If you need anyone to dogfood it for you, I’m happy to take a swing at it. I spend most of my time in a codebase that features lots of custom def macros
Thanks, sounds good. So are these mostly (defwhatever <a symbol> …), or are there more complex things? Do they often allow docstrings, for example?
Ok, I won’t be able to handle that with this proposed change, that will require the extension API. I guess this is an in-house macro, not from a public project?
Would your planned solution use the symbol immediately following the function as the name?
The internal API allows you to do pretty much anything, but I still haven’t open sourced that, too busy unfortunately.