-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Add --mode option to built in target task #537
Conversation
bb89a54
to
4775109
Compare
Has anyone tried this on Windows? |
Good point, I implemented it this way, because tmp files already are created with |
@ekroon cool, thank you. I haven't checked myself, so it may very well work. I just wanted to make sure someone has tried it. |
In https://github.com/asciidoctor/atom-language-asciidoc they use www.appveyor.com for Windows testing. Would that be an option for boot? |
Can you please add arities to Then the arity change is backward compatible. Thanks 🤘 |
It looks like the earlier |
@ekroon I don't have experience with appveyor but am certainly open to it. |
4775109
to
508b0d2
Compare
For situations where the default 'rw-------' file modes are not enough, a (posix) mode string can be given to target. All files will get the mode written. When an invalid mode is given, a warning is printed and standard permissions will be used.
508b0d2
to
743aa67
Compare
@alandipert took the liberty to also fix #541 on this branch as it is closely related. |
For situations where the default 'rw-------' file modes are not enough,
a (posix) mode string can be given to target. All files will get the
mode written.
When an invalid mode is given, a warning is printed and standard
permissions will be used.