@kenny Here’s the fix for your problem (and others) in the next build:

You can now resolve any macro as any other with a decent UI to select them.

That is awesome!!

The one other issue is how those customisations get shared across a team - I’ll check that’s working ok.

We aren't doing that right now but that seems quite valuable. Are you suggesting there is a way to do that right now?

No, I’m suggesting that there should be 🙂

Right now I think they’re IDE specific, and there’s no good way to make them project-specific.

In your case, these customisations are specific to the project you define your wrappers in, so that’s what you’d want.

But if you were defining that for something that came from a lib you use in many projects, it would be annoying to have to re-define it in each one.

Isn't it fair to say that namespaces should be global?

Therefore these resolve-as settings should also be global

Well, there are two sorts of global, or two things which are global in different ways. IDE settings are global to any project you open in your IDE. Project settings are global to anyone opening that project, assuming you’re checking the relevant config file in.

Things either have to be stored with your IDE or your project, they can’t be both.

Most config falls pretty clearly into one or the other, but sometimes things like this require both depending on how you use it.

Makes sense. What I was suggesting was is that this sort of setting is global to any project you open.

Yeah, I think there’s scope for something you configure in your IDE that gets copied to any project you open, but IntelliJ doesn’t have anything like that.

Default run configs would be another good candidate for that.

Agreed.

Don't the current symbol resolutions get copied to every project?

Or are somehow treated as global.

No. Because they’re associated with your IDE, you will see them in all projects, but your co-workers will not.

Ah I see. Because they are not stored in the .idea project folder?

The issue with an IDE config that got synced to projects you opened would be if you and a co-worker had different, say, indentation settings for a particular form. Then each time one of you checked in that setting would get overwritten for the other person.

Yes, that’s right. Because project config is stored in .idea, you can check it in and co-workers will see it, but then it won’t apply to any other projects you may have.

That would make sense if you’re customising a macro defined in that project, since anyone using the project will need that customisation and you’ll never need it in any other project.

Cursive bundles its own leiningen, yes?

@cap10morgan Not quite, but it does download it automatically to ~/.lein/self-installs on first use of a particular version.

oh, hmm. I'm trying to get it to use 2.8.1, but not quite seeing how.

So the only time that you might notice that is if you try to use it when not connected to the internet yet.

I found a version drop down list in the settings, but it maxes out at 2.7.1

Ugh, sorry, I forgot to add that to the latest EAP. I filed https://github.com/cursive-ide/cursive/issues/1882 and I’ll add it to the next one, hopefully in a couple of days.

ah, cool. thanks @cfleming!