afrog icon indicating copy to clipboard operation
afrog copied to clipboard

Atom won't open path on command line

Open trinaryouroboros opened this issue 2 years ago • 5 comments

I was formerly using Fedora 32 and an older version of atom, and when running in konsole terminal:

atom ./

It would open atom to the local path and show all files/folders in it.

I upgraded to Fedora 35 recently and am using the latest atom, and this doesn't work anymore.

It just opens to a blank atom with "Add Folders" on the left.

I tried wiping ~/.atom but it had no effect.

trinaryouroboros avatar Mar 01 '22 20:03 trinaryouroboros

Does running atom only launch the editor?

darangi avatar Mar 03 '22 18:03 darangi

Yes, and it only shows whatever path was opened last, not the current directory.

trinaryouroboros avatar Mar 03 '22 18:03 trinaryouroboros

Can you try launching it with atom . instead of atom ./?

jnuernberg avatar Apr 06 '22 13:04 jnuernberg

Strange it's not working at all now, maybe something unique to my OS, I'm ending up using vscode so this is no rush anymore.

expr: syntax error: missing argument after ‘8’
/usr/bin/atom: line 195: 16544 Illegal instruction     (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
54.161.241.46, 18.205.222.128, 54.237.133.81, ...
Connecting to atom.io (atom.io)|54.161.241.46|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-06 10:36:10 (0.00 B/s) - ‘/dev/fd/4’ saved [0]


Unexpected crash report id length
Failed to get crash dump id.
Report Id: 
--2022-04-06 10:36:10--  https://atom.io/crash_reports
Resolving atom.io (atom.io)... 54.237.133.81, 18.205.222.128, 54.161.241.46, ...
Connecting to atom.io (atom.io)|54.237.133.81|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-06 10:36:10 (0.00 B/s) - ‘/dev/fd/4’ saved [0]


Unexpected crash report id length
Failed to get crash dump id.
Report Id:```

trinaryouroboros avatar Apr 06 '22 14:04 trinaryouroboros

Experiencing a similar issue on Windows 11 Home using Git Bash as my command line.

atom . only opens up a new window where the Project folder is where atom is installed (C:\Users\marct\AppData\Local\atom\app-1.60.0).

atom opens up the last open Project folder.

A workaround I've done to open up atom with respect to my command line's current directory is atom $(pwd), which presumably works with any bash CLI, but I'm not sure how to make atom . work again. It used to, and I'm not sure what I did to change that behavior.

castillo-marc avatar Sep 28 '22 19:09 castillo-marc