Ugh, sorry, I’ve partially investigated this multiple times, but not got around to fixing it. I’ve moved this into the next release.

A workaround is to press right arrow, so the text is not selected, and the namespace prefix therefore doesn't get replaced in 2.

Yeah I noticed it too but wasn't sure whether it always worked like this or not 😅

have also noticed this, and mostly adapted to it w/the right arrow thing mentioned ^

Yes, I made this change recently, because the IntelliJ new package dialog does this. However, the fact that the text is selected initially is a pain, I’ll see if I can fix that.

Ok, there is absolutely no way to fix this without duplicating all the code involved - it’s all private and final. Would everyone prefer the old way this used to work?

While I'd prefer the old way, I think I'd rather get used to how it currently works and avoid some future breakage or maintenance issue arising from going against Jetbrains

> Would everyone prefer the old way this used to work? Haha, interesting to see if you'll be able to get a confirmation from all Cursive users here 😜. I'm fine with either or, hadn't noticed the change 😃

I liked that change. I used to create many app.core.app.core.new-ns

The improved visibility that comes with the change is nice indeed

oh, just found this, because Im having the same issue, making wrong namespaces because of the change: https://clojurians.slack.com/archives/C0744GXCJ/p1707233059463129?thread_ts=1707233059.463129

would be great if the cursor just started at the end instead of having the text selected

The fix for this is out now, in the latest EAP.

working great! thanks!

where would goto definition on a keyword take you?

A couple different places potentially. I use fulcro defattrs generally, so that would be nice for my own projects. I'm fairly certain that other projects have similar "def kwd" type calls too.

@U0567Q30W is this feature idea interesting / possible? I know next to nothing about IJ plugins and UI requirements so it could easily be technically infeasible for all I know... But if it's not that would be 🔥.

My apologies for this taking so long to get to. I’m not sure about making this pluggable, but Cursive does actually support this for some keyword use cases, e.g. spec:

(s/def :order/date inst?)
(s/def :deck/suit #{:club :diamond :heart :spade})

(s/valid? :order/date (Date.))
(s/conform :deck/suit :club)

Here, you can navigate to :order/deck, use find usages, etc. It requires me to add support for forms using this currently, I’d be interested to know if there are common cases that are missing.

There is https://plugins.jetbrains.com/plugin/18019-integrant which adds support for navigating to integrant component definitions. I use this and find it useful

Thanks, I’ll take a look and see what it’s doing.

I've recently retrofitted VSCode with kw-docs that I hand rolled for my work app for example. I've also added some goto-definition that goes to com.fulcrologic.rad.attributes/defattr definitions.

How does that work?

What I mean by that is, what’s the logic you’re using to populate that popup?

This is probably also a pain to implement, but using the NREPL support from calva and some custom relation

> What I mean by that is, what’s the logic you’re using to populate that popup? I have a function in my code that searches for defattr s, and populates the popup with generically relevant information of all related defattrs

currently this requires a running repl connection, but it may be possible to just create static dumps of this as edn, if that's workable

So, you have features for: navigation (going to definitions based on some logic), documentation (generated based on some custom logic) and… is that last one completion?

yep, this one is completion based on var attrlists

I see, that one I could potentially do generically in Cursive, which would be a nice addition.

The issue with a lot of this is that Cursive doesn’t use the REPL for any of that functionality. So that makes it harder to hook into.

How do you calculate the related kws in the case of defattrs? I’m not really sure how those work.

I'm contemplating hooking that up with guardrails, but I've not had time free to make that happen yet. Anyway, just some ideas I've been messing with that would be awesome for cursive as well.

sorry for the unrelated msg, my internet dropped out

Absolutely, I’d like to try to support some of these, but I’ll have to think about how to do it. It’s not as simple as just hooking into nREPL, sadly.

there's another, potentially nearer at hand solution - using clojure-lsp? It already has support for library-specific metadata collection, and it's hooked into IJ. I think the important metadata from stuff like fulcro can be dumped as edn for completion/gotodef/docs

I'd have to check, but I think clojure-lsp has pluggable versions of all of the above

Ok. I’m planning to integrate lsp into Cursive in some degree in the next release.

Here's an example of deffattr in use: https://github.com/fulcrologic/fulcro-rad-demo/blob/main/src/shared/com/example/model/address.cljc

Which metadata from fulcro do you use?

Primarily anything from a defattr

So in that case, I’m unsure what that’s doing. It looks like it’s defining a var and a keyword?

The var is a map... e.g.

(defattr state :address/state :enum
  {ao/enumerated-values (set (keys states))
   ao/identities        #{:address/id}
   ao/schema            :production
   ao/enumerated-labels states})

(def state {::attr/qualified-key :address/state ::attr/type :enum ao/enumerated-values ...})

And you’d want to be able to navigate from :address/state to that defattr?

Yup

Ok. That’s quite easy, I can add that.

This stuff will eventually be user-extensible, but it’s not yet.

I'm not sure all fulcro people would like that, since I know one or two that still use specs, though I'm not sure if they use gotodef on those specs

just FYI

Ok, I’ll check with Tony, he uses Cursive (or did, anyway).

still does to my knowledge

So from the defattr, which kws do you consider related?

There's typically an :something/id type keyword, and anything with ao/identities #{:something/id} is related, which may be across multiple files

e.g. in the address file, every property on an address has ao/identities #{:address/id}

Interesting, I see. That’s tricky.

A possible workaround is using this (which is supported by Cursive):

(println (str "Hello" \u001b "[1KWorld"))

Thanks, yes, Cursive does support that ANSI code.