Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not open atom from command line #5222

Closed
bhoskins opened this issue Jan 22, 2015 · 8 comments

Comments

@bhoskins
Copy link

commented Jan 22, 2015

When I try to open atom from the command line using: atom .
I get this error
FSPathMakeRef(/Applications/Atom.app) failed with error -43.

I reinstalled the shell commands, closed and opened Atom, closed and opened the command prompt and the error still persists.

@50Wliu 50Wliu added bug mac labels Jan 22, 2015
@mnquintana

This comment has been minimized.

Copy link
Member

commented Jan 23, 2015

Can you post:

  • your Atom version number
  • your installed packages
    ?

Do you still get this error if you try opening it with atom --safe .?

@bhoskins

This comment has been minimized.

Copy link
Author

commented Jan 23, 2015

Atom version: 0.175.0(0.175.0)

packages:
emmet
linter
linter-htmlhint
linter-scss-lint
tag
And Core Packages

does not open in command with: atom --safe .

Hope ths helps,
B. Hoskins

On Fri, Jan 23, 2015 at 7:46 AM, Machiste N. Quintana <
notifications@github.com> wrote:

Can you post:

  • your Atom version number
  • your installed packages ?

Do you still get this error if you try opening it with atom --safe .?


Reply to this email directly or view it on GitHub
#5222 (comment).

@postcasio

This comment has been minimized.

Copy link
Contributor

commented Jan 23, 2015

How did you install Atom? Was it using Homebrew? Could be related to #3224

@GingerBear

This comment has been minimized.

Copy link

commented Feb 1, 2015

I get the same issue after I unzip the official atom-mac.zip file and move to /Applications, where there is actually already a old atom existing. The new app is renamed to Atom 2. I didn't aware that and thought it maybe the some version name. Then I remove the original Atom. After that I get the same error in terminal.

After I remove the Atom 2, move the unzip file to /Applications and run Install Shell Command again, everything works fine.

I guess the Install Shell Command is installing the shell script that based on assumption that atom is installed at /Applications/Atom (atom/atom.sh). Otherwise it will fail.

@bhoskins

This comment has been minimized.

Copy link
Author

commented Feb 2, 2015

Thanks, I think you are right. I uninstalled all atoms and reinstalled it
and its working now. I had forgotten that I had installed it and installed
it twice. Thanks for the info.
Peace,
Beth H.

On Sun, Feb 1, 2015 at 1:45 AM, Neil Ding notifications@github.com wrote:

I get the same issue after I unzip the official atom-mac.zip file and
move to /Applications, where there is actually already a old atom existing.
The new app is renamed to Atom 2. I didn't aware that and thought it
maybe the some version name. Then I remove the original Atom. After that
I get the same error in terminal.

After I remove the Atom 2, move the unzip file to /Applications and run Install
Shell Command again, everything works fine.

I guess the Install Shell Command is installing the shell script that
based on assumption that atom is installed at /Applications/Atom (
atom/atom.sh

atom/atom.sh

Line 48 in cbc8ad1

ATOM_APP_NAME=Atom.app
).
Otherwise it will fail.


Reply to this email directly or view it on GitHub
#5222 (comment).

@piyushbajaj0704

This comment has been minimized.

Copy link

commented Apr 1, 2017

On Windows 7 and above, add the %LOCALAPPDATA%\Atom\bin to your user PATH variable. You test it out from the command line by running the following command:
SET PATH=%PATH%;%LOCALAPPDATA%\Atom\bin
Then you should be able to run Atom directly from the command line.

@wd990

This comment has been minimized.

Copy link

commented Dec 2, 2017

@piyushbajaj0704 works great. Thanks mate

@lock

This comment has been minimized.

Copy link

commented May 31, 2018

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!

@lock lock bot locked as resolved and limited conversation to collaborators May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
7 participants
You can’t perform that action at this time.