title: How does conda-env list / conda info --envs find environments?
body: <p>I've been experimenting with anaconda/miniconda because my users use structural biology programs installed with miniconda and none of the authors A) take into account that there might be other miniconda applications B) that their programs will be used in a multi-user environment.</p>
  
  <p>So, using Arch linux, first I installed anaconda (version 4.5.12) , and then using my own account, created a couple of test environments:</p>
  
  <pre><code>conda create -n snakes
  conda create -n sharks
  </code></pre>
  
  <p>I then (completely) uninstalled anaconda and installed miniconda (also version 4.5.12) and then created another environment in a non-standard location as root:</p>
  
  <pre><code># conda create -p /usr/local/miniconda/pyem
  </code></pre>
  
  <p>Here's where things get weird.  When I list the environments as the root user, I see not only the default and the one I just created, but also the ones I created previously using my user account!</p>
  
  <pre><code>[root@lizard /]# conda info --envs
  # conda environments:
  #
                           /home/cnsit/.conda/envs/sharks
                           /home/cnsit/.conda/envs/snakes
  base                  *  /opt/miniconda3
                           /usr/local/miniconda/pyem
  </code></pre>
  
  <p>(The <code>conda-env list</code> command gives the same output.)</p>
  
  <p>So, question: <strong>how is conda finding environments created by a different user?</strong> Moreover, when the entire parent directory of the original instance of conda has been removed and replaced by one in an entirely different location (so no local <em>environments.txt</em> file could be cataloging this.</p>