The error console pops up sometimes because I run Atom as a user who isn't in the admin group (so I

[eric]

The error console pops up sometimes because I run Atom as a user who isn't in the admin group (so I don't have write access to /Applications/Atom.app).

http://cl.ly/image/2o2y2z0H1T1h

Atom Version: 1
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Atom/0.45.0 Atom-Shell/0.7.6 Safari/537.36

[probablycorey]

This may be fixed when #1464 lands (if not fixed then the error should at least be more clear)

[eric]

Instead of just an error, I would like for Atom to use the Mac OS authentication UI to do that operation.

[probablycorey]

We should probably use authopen to handle the creation of the cli tools.

[probablycorey]

@zcbenz: you mentioned in #1529 that authopen won't work because of symlinks. We get around this limitation by using authopen to write a shell script that calls the atom.sh and apm/node_modules/.bin/apm files, correct?

But we would still have the problem that /usr/local/bin doesn't exist by default on OS X and authopen doesn't create directories. But runas won't be able to help with this directly, correct?

[probablycorey]

I looked into how Textmate 2 does it https://github.com/textmate/textmate/blob/274f73b7de3e7fd9ed67490cfc82cf6d22f9c44e/Frameworks/Preferences/src/TerminalPreferences.mm#L34.

They use the Authorization Services API.

[zcbenz]

Textmate does it by calling the mkdir command with root privilege when current user doesn't have enough permission, after runas has been implemented with the Authorization Services API, we could repeat this behavior on OS X.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!