PROS installed but not working on Atom

DISCLAIMER: I am a complete noob at PROS. I’ve never used it before.

So I’ve tried to install PROS on Atom before and found out I was installing the wrong version, so it showed me the error ‘PROS CLI not found on PATH’. So I deleted the PROS_bootstrapper and the old pros packages from Atom and restarted it. I then installed the PROS 3 package on atom and it worked just fine! But whenever I try to do anything with PROS, the same error message pops up:
’Could not determine which project to upload/use/build! Please open a file from a PROS project and try again.'

You can see this in the below photo:
2020-04-07 (2)

So this left me pretty confused, because how am I meant to have a PROS project when I can’t even build one?

This might just be me being a noob and/or being completely stupid, but any help?

In the programming world, “build” means compile, not create project.

I’m sure there’s an option somewhere in Atom to create a new project (perhaps in the PROS menu? I don’t remember — the last time I used Atom was years ago, and I uninstalled it promptly).

You can also create a new project via the CLI:

pros conduct new-project /path/to/your/project v5

Side note:

I would recommend against using Atom, especially since you’re just starting out and (presumably) not used to any one editor at this point.

Atom still, even though the issue was reported years ago, has a nasty habit of deleting code. If you decide to use Atom, Git/version control is absolutely imperative.

Also, in my opinion, a “hackable text editor” is no substitute for a proper IDE. VScode is a similar free and lightweight text editor, yet it features the same IntelliSense language server that powers Microsoft’s enterprise IDEs (Visual Studio). Atom’s language server simply does not compare.

I’m sure some will disagree; these are just my two cents. (And yes, it’s quite easy to integrate PROS with other IDEs.)


I would just generally suggest against spending time to even try to get the atom editor integration working with PROS. The CLI is far more powerful than the default GUI options you get in atom, and gives you the freedom to work in whatever text editor you’re most comfortable with.

VS Code lets you open poweshell terminals alongside your code, so the CLI is pretty easy to use from there. (I’m sure this is possible in atom as well, but I’ve never played around with that enough to know).


Even better, get clangd. Makes the experience in VSCode really nice.