@cfleming namespaced keywords aren't being highlighted everywhere they appear in the editor, unlike regular keywords where every occurrence is highlighted. (images to follow)

@lgouger Right, there’s an issue in the new declared keywords functionality where the declaration is not highlighted (all usages are).

ok, matches what I'm seeing

In your example, the non-namespaced keyword “works” because only namespaced keywords are eligible to be treated as declarations - doing it for non-namespaced ones would change the semantics of that keyword everywhere, which seems dangerous.

So you won’t be able to navigate to the first example from the usage, and it won’t show up in File Structure.

ok, "works" because all occurrences are usages, none is a declaration

Right, and Cursive doesn’t treat it as a declaration at all, it’s just a normal keyword.

got it, thanks

In your case, the keyword is long enough that it’s probably unambiguous, but for shorter keywords it could be very confusing. So even if it’s purely for Cursive support, I recommend using namespaced keywords for all re-frame declarations. spec already enforces that.

thanks, yeah, transitioning that direction

Cool - it’s a good idea even apart from Cursive support, of course.

I also find the lack of namespaced kw highlighting frustrating 🙂

but GoTo and Find Occurrences are cool

@gphilipp Nice solution, but you’re right that it really needs a solution within the IDE, if only so it works correctly on Windows. I’ll investigate that.

@holyjak Yes, that would be nice to support.

How do I find an unmatched ']' delimiter in my project? boot repl won't start because it complains about an unmatched delimiter, but I can't find it. Probably caused by Parinfer after switching to it.

Yes it does. We use

:username [:gpg :env/artifactory_user]
:password [:gpg :env/artifactory_password]