Unable to open ~/.atom with atom CLI tool

[thedaniel]

When I run atom ~/.atom, nothing happens. I can still open any other directory, and I can still open ~/.atom from the settings pane.

[kevinsawicki]

Are you still seeing this issue?

If so, can you try running atom -f ~/.atom and see if any errors appear in the console?

[thedaniel]

Still seeing this as of 3d494ed

[atom.io (master)⚡]> atom -f ~/.atom
2014-01-03 15:28:21.873 Atom[34935:507] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
2014-01-03 15:28:22.200 Atom[34935:507] "App load time: 257ms"
[atom.io (master)⚡]> 

App launches, no windows open.

[kevinsawicki]

Did you have any other windows open when you ran the command?

If you did, can you try completely quitting atom and re-running atom -f ~/.atom?

[thedaniel]

I did this, then attempted to quit Atom again, and was presented with this:

I force quit, and re-ran atom -f ~/.atom and got some helpful output:

[atom.io (master)⚡]> atom -f ~/.atom
2014-01-03 15:31:11.510 Atom[34974:507] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
2014-01-03 15:31:11.832 Atom[34974:507] "App load time: 264ms"
2014-01-03 15:31:11.880 Atom Helper[34975:507] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
[0103/153111:INFO:renderer_main.cc(212)] Renderer process started
[0103/153112:INFO:CONSOLE(76)] "Error parsing window state: /Users/daniel/git/dotfiles/atom/storage/editor-3dbe73ba6be9abbceb6cc029099dab43c6268601 SyntaxError: Unexpected end of input
    at Object.parse (native)
    at Function.module.exports.Atom.loadDocumentState (/Applications/Atom.app/Contents/Resources/app/src/atom.js:72:23)
    at Function.module.exports.Atom.loadOrCreate (/Applications/Atom.app/Contents/Resources/app/src/atom.js:49:32)
    at Object.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:15:22)
    at Object.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:25:4)
    at Module._compile (module.js:471:26)
    at Object.Module._extensions..js (module.js:489:10)
    at Module.load (/Applications/Atom.app/Contents/Resources/app/node_modules/coffee-script/lib/coffee-script/coffee-script.js:211:36)
    at Function.Module._load (module.js:327:12)
    at Module.require (module.js:379:17)
    at require (module.js:395:17)
    at window.onload (file:///Applications/Atom.app/Contents/Resources/app/static/index.html:12:9)", source: /Applications/Atom.app/Contents/Resources/app/src/atom.js (76)

[kevinsawicki]

@thedaniel are you still seeing this on 0.47.0?

[thedaniel]

Running on a6f9b6d i get the output below, and the editor is not opened to ~/.atom

[~]> atom -f ~/.atom
2014-01-21 11:11:05.796 Atom[6922:507] Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
[6922:0121/111105:WARNING:dns_config_service_posix.cc(188)] dns_config has unhandled options!
2014-01-21 11:11:06.581 Atom[6922:507] "App load time: 540ms"

[kevinsawicki]

Hmm, is ~/.atom a symlink or anything weird like that?

[thedaniel]

A HA!

lrwxr-xr-x    1 daniel  staff       31 Nov 14 16:38 .atom -> /Users/daniel/git/dotfiles/atom

[kevinsawicki]

Good to know, looking into this now.

[kevinsawicki]

And just to confirm, /Users/daniel/git/dotfiles/atom exists right?

[thedaniel]

yup

[~]> ls ~/.atom
config.cson packages    themes      user.cson
keymap.cson storage     user.coffee user.css
[~]> ls ~/git/dotfiles/atom/
config.cson packages    themes      user.cson
keymap.cson storage     user.coffee user.css

[kevinsawicki]

And atom ~/git/dotfiles/atom opens normally?

[thedaniel]

Yes.

[kevinsawicki]

I'm having trouble reproducing even when using a symlinked ~/.atom dir, let's pair on this when you are here this week if that is cool.

[kevinsawicki]

Fixed by cd41637 and atom/git-utils@3c4d0bc

[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!