-
Notifications
You must be signed in to change notification settings - Fork 1
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
Output formatting #2
Comments
Hi, sorry for the delay - it's better to mention me if you open any further issues. (Tips on how to get notified somehow on new issues even without being mentioned are most welcome. Despite of quite a long history here, I can't call myself Github poweruser.)
I'm OK with this. Later there should also be an option to specify the output filename if needed.
Sounds reasonable.
There is a simple logging solution in the Ruby standard library. And there are, of course, plenty of third-party libraries. |
Also, before eventually receiving the first pull-request for ordodo ever, I should finally pick a license. I have planned for some time to place this piece of software under the MIT license. Do you like/hate the idea? |
Puh, finally. Please have a look at my pull-request. Regarding the license: I like the idea of copyleft, but if you want to pick the easier MIT license I would be ok with it. |
Thanks. MIT license adopted. I will comment on the PR shortly. |
This need not be handled in the PR in progress, but is related to this issue, so I will note it here rather than there: I think the "ordodo's main user interface is it's configuration file" philosophy (cf. README) should apply for specifying the output directory, too. It would make sense to support configuring path with placeholder(s), like |
Hi,
I run ordodo for the first time and have some minor suggestions, which I will try to implement as a first exercise to get to know the code (and Ruby, I'm a Pythonist).
The text was updated successfully, but these errors were encountered: