Just wondering why there isn't an option to run stack new on the current directory? Sometimes I have created a project directory already, and i want to fill it up with files. I guess the main problem is what to do if the directory already contains files that exists. To be safe, you can report that such a file already exists, and you didn't replace it (rerun the command while removing the old file to replace the file).
I think that stack new --bare does what you want. Not sure if I like the flag name --bare. I guess it comes from git init --bare, but the analogy falls apart a bit.
What flag name would be clearer? stack new --current-dir?
Why not just make stack new support directories that already exists. So you can then use . or ./somedirthatalreadyexists?
Because it doesn't take a directory name as an argument, it takes a package
name.
On Sat, Feb 24, 2018 at 7:50 PM, Roger Qiu notifications@github.com wrote:
Why not just make stack new support directories that already exists. So
you can then use . or ./somedirthatalreadyexists?—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/commercialhaskell/stack/issues/3882#issuecomment-368280915,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABYKsuf2boYEv51YyzmPUG4GE8XXDUlks5tYNifgaJpZM4SNFjo
.
Answers provided, closing
Most helpful comment
I think that
stack new --baredoes what you want. Not sure if I like the flag name--bare. I guess it comes fromgit init --bare, but the analogy falls apart a bit.What flag name would be clearer?
stack new --current-dir?