-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have buffrs init dir
use dir instead of the current working directory
#185
Comments
The behavior is inspired by |
Maybe we can implement buffrs new? |
Just to clarify the possible behaviors as we might want to distinguish package names from directory names. Right now:
First option is to go the
Now I read that the |
I was a bit surprised when
buffrs init --lib units
createdProto.ml
andproto/
in the current working directory instead of creating aunits/
directory, like Cargo would do.The second blog post actually uses
buffrs init --lib units
and suggests it works (or worked) like Cargo.The current behavior is a bit annoying, since it mean you need to
mkdir
andcd
into the directory before runninginit
. If that's okay, I would like forbuffrs init
to work as closely ascargo init
as possible, even initializing a git repository if there is none. It might not be very useful for implementations, but libraries could definitely use that.The text was updated successfully, but these errors were encountered: