Open danielbayley opened 8 years ago
I was unable to reproduce this using Atom v1.2.0-dev-d2fdc41 on Mac OS X 10.11.1. Here's what I tried:
~/.atom/packages
(I picked sort-lines)apm link --dev
ls -l ~/.atom/dev/packages
to verify the link existsapm uninstall sort-lines
ls -l ~/.atom/packages
to verify sort-lines was uninstalledls -l ~/.atom/dev/packages
to verify the link still existsls -l ~/Source/sort-lines
to ensure that the cloned repository still existsDid you do something different? If so, what? What did you expect to happen? And what did happen exactly?
(Also please include which version of Atom you were running and what OS and version you are on.)
This happens if I do apm develop
on an existing [installed] package (since I want to contribute to it), and so then have duplicate packages under $ATOM_HOME/packages
and $ATOM_HOME/dev/packages
.
If I then uninstall the original package from within Atom they both get erased. I would expect that the $ATOM_HOME/dev/packages/
package would be left in tact.
OS X 10.11.1 El Capitan Atom 1.0.19
$ apm -v
apm 1.0.5
npm 2.13.3
node 0.10.40
python 2.7.10
$ env | egrep 'ATOM|NPM'
ATOM_DEV_RESOURCE_PATH=/Users/Dan/Library/Application Support/Atom/dev/packages
ATOM_HOME=/Users/Dan/Library/Application Support/Atom
ATOM_ACCESS_TOKEN=βββββββββββββββββββββββ
ATOM_REPOS_HOME=/Users/Dan/Library/Application Support/Atom/dev/packages
NPM_CONFIG_PREFIX=/Users/Dan/Library/Scripts/Libraries/js
atom.config.get('core.projectHome')
= ~/Library/Application Support/Atom/dev/packages
β¦and removes it completely; not even just to the trash.