Closed kwhitaker closed 8 years ago
Thanks for the report!
I'm wondering if the bug here is that we don't show a helpful message for permission errors, or if we're creating files wrong in some way. Are you able to create the directory manually with the same user that was running Atom?
@Osmose that I am. Also, once I manually created a file in the src
directory, I was able to use AOF to create other files just fine.
wat
Oh, I see that it tried to make /src
. Hmm, were you using relative paths when you hit the failure? I could totally see a bug where we forget to absolutify the path before passing it to mkdirp.
Honestly I can't recall offhand - it's been a few hours. I'll keep an eye on it and update if it happens in the future.
Same issue here. Yes, it happens when trying to use a relative path.
Same issue here. Yes, it happens when trying to use a relative path.
Cool, thanks for the info!
Should be fixed in master
now. I'll do another release before I drop off tonight, and if one of you could verify that the new release is working for you I'd appreciate it. :D
project/src/some-new-file.js
)Atom Version: 1.1.0 System: Mac OS X 10.11.1 Thrown From: advanced-open-file package, v0.12.0
Stack Trace
Uncaught Error: EACCES: permission denied, mkdir '/src'
Commands
Config
Installed Packages