Skip to content
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

fixes #891 #892

Merged
merged 9 commits into from
Feb 9, 2016
Merged

fixes #891 #892

merged 9 commits into from
Feb 9, 2016

Conversation

eroux
Copy link
Contributor

@eroux eroux commented Feb 9, 2016

All tests pass. Please review my broken English

@eroux
Copy link
Contributor Author

eroux commented Feb 9, 2016

I've pushed a few changes

@henryso
Copy link
Contributor

henryso commented Feb 9, 2016

I'm done with my review.

\t-v verbose mode\n\
\t-W displays all warnings\n\
printf(_("Usage: %s [OPTION]... [-s | INPUT_FILE]\n\
\nEngrave Gregorian chant scores, convert a gabc file in GregorioTeX.\n\n\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I just noticed this... "in" should be "to".

\n"));
See <%s> for general documentation,\n\
GregorioRef-%s.pdf and GregorioNabcRef-%s.pdf for full documentation.\
\n"), PACKAGE_URL, VERSION, VERSION);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since these are #define, they can be inserted directly: "...GregorioRef-" VERSION ".pdf..."

@eroux
Copy link
Contributor Author

eroux commented Feb 9, 2016

more comments addressed, please review

@henryso
Copy link
Contributor

henryso commented Feb 9, 2016

Looks good to me.

@rpspringuel
Copy link
Contributor

Do we have tests for this output? If not, should we?

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ

On Feb 9, 2016, at 9:08 AM, Henry So [email protected] wrote:

Looks good to me.


Reply to this email directly or view it on GitHub.

@eroux
Copy link
Contributor Author

eroux commented Feb 9, 2016

All tests pass, I don't think it's necessary to have many tests for that... and even if some could be done, I think we should focus more on the features and bug requests for 4.1 (I have a big bug under Windows, but I didn't understand it enough yet).

@rpspringuel
Copy link
Contributor

Shouldn't the short usage info message print the command syntax? I.e. What is the first line of the help message.

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ

On Feb 9, 2016, at 9:08 AM, Henry So [email protected] wrote:

Looks good to me.


Reply to this email directly or view it on GitHub.

@eroux
Copy link
Contributor Author

eroux commented Feb 9, 2016

good idea, done

@henryso
Copy link
Contributor

henryso commented Feb 9, 2016

We have tests for all the options, but they are pass/fail (return code) only and don't check the message content.

@eroux
Copy link
Contributor Author

eroux commented Feb 9, 2016

I've transfered a few messages to stderr, and added a message for non-blocking case, please review, I think I'm done with changes (I thought I was for a few hours actually)...

@henryso
Copy link
Contributor

henryso commented Feb 9, 2016

I think this is OK to merge.

eroux added a commit that referenced this pull request Feb 9, 2016
@eroux eroux merged commit 1344625 into develop Feb 9, 2016
@eroux eroux changed the title first attempt to fix #891 fixes #891 Feb 9, 2016
@henryso henryso deleted the fix-891 branch February 9, 2016 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants