opened
kripken
username_0
This came up as possibly useful for emsdk users that want to set up their own .emscripten file, so they need to know which dir the code is under. With the emscripten-releases system, currently each download gets its own directory, so it changes over time. (It's a new dir each time to make it easy to switch between builds back and forth, and also it lets us not unzip a download that was already downloaded.)

Example output:
```
$./emsdk show-activated-paths
/home/.../sdk/upstream/c7784483727437237472347/emscripten
/home/../sdk/node/../bin
```

By default the emsdk downloads node.js as well, so there are two activated tools, and so two paths.

Alternatively, perhaps we can fix this by reusing the same directory.  That might be better, come to think of it, as otherwise each update creates a new one and they aren't small, so if a user isn't careful over a year there can be a lot of disk usage that accumulates?
Add a show-activated-paths option, which prints out the activated paths
issue
created
kripken
username_0
We probably don't need this since #248 landed. However, maybe a tool like this is still useful, given the other stuff discussed in there like how to find the various paths? cc @username_1
comment
created
floooh
username_1
...see my reply here: https://github.com/emscripten-core/emsdk/pull/248#issuecomment-496856784
comment