Closed thibmaek closed 8 years ago
@thibmaek That's odd 😕
Are you on Windows?
Can you run cd "${ATOM_HOME:-~/.atom}" && mkdir -p snippets
directly on the command line without error?
Nope, on OS X. Running that command without the mkdir outputs:
→ cd "${ATOM_HOME:-~/.atom}"
-bash: cd: ~/.atom: No such file or directory
Your issue is most likely due to wrapping it in quotes. Running without the quotes work just fine, let me PR this to fix it.
Ah of course; the tilde ~
won't be expanded inside quotes. There should be a :facepalm:
emoji…
The quotes are necessary though in case of spaces in the file path, for example I have ATOM_HOME
set to ~/Library/Application Support/Atom
.
So the solution is mkdir -p "${ATOM_HOME:-$HOME/.atom}/snippets"
.
@thibmaek Looks like I beat you to it 😄. Cheers though… should work now?
This problem is basically not solved. Sorry, waiting for the updates for Windows
I guess that is not generated "ATOM_HOME"
It's about 50% solved since it won't support Windows, but should work for everything else. Shouldn't be too hard finding the equivalent command for mkdir for Windows and submitting a PR though. Problem is that that $ATOM_HOME env var is not available on the Windows shell, since it's a UNIX bash one (I think)
@thibmaek , Thanks for the feedback. To me very important file organization of the snippets. Had to go back to sublimeText. Sadness. :(
However,
cd ~/.atom
works. Also works when exporting an env to the shell first withexport ATOM_HOME=~/.atom