There are mainly 2 ways to do this:
The first and recommended way is what @mortenpi showed in slack:
if you can easily access a terminal, you can set
ATOM_HOME to point somewhere other than
~/.atom before launching Atom, e.g.
I actually always put this script into my PATH: https://github.com/mortenpi/juno-debian/blob/master/src/juno so my main Atom environment is clean and if I want Juno, I just launch
The second is to use atomic-management, which enables kind of per-project config. Then you can create
.atom/config.cson for each project and enable/disable Juno via putting
*.core.disabledPacakges config. Note that this way may slow down your Atom’s activation, and that why I recommend the first way if you’re familiar with shell script.
Also it’s worth to note that for both ways, you can unload/disable
ink package, which may ease your activation time, but then any deserialization (restoring the previous window state) won’t anymore.