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

five-note neume does not display #284

Closed
chonak opened this issue Apr 16, 2015 · 6 comments
Closed

five-note neume does not display #284

chonak opened this issue Apr 16, 2015 · 6 comments
Assignees
Labels

Comments

@chonak
Copy link

chonak commented Apr 16, 2015

If there are five notes in a row, with no specification of neume type, the first four notes do not appear in the output, and only the last note is displayed. If I add a separator ("!" or "/") to the input, the neume is formed correctly.

Here is a minimal example:
%%
(c4)A(g!hgfg) (::)
a(ghgfg) (::)

When I process this, the first series of notes appears in full; but the second group of notes doesn't: only the last note of the series appears.

snapshot18

I found this behavior in v.3.0.0-rc1 (on Linux, with TeXLive2013). Another user confirms it with v.3.0.0-rc2 on Mac.

@henryso
Copy link
Contributor

henryso commented Apr 16, 2015

If you need a short-term work around, use ghg/fg.

@henryso henryso self-assigned this Apr 16, 2015
@henryso
Copy link
Contributor

henryso commented Apr 16, 2015

Team, should I target develop or release-3.0 ? This bug was introduced with the so-called "torculus liquescens" (ghgf~)

henryso added a commit to henryso/gregorio that referenced this issue Apr 17, 2015
actually liquescent. Fixes gregorio-project#284.
(grafted from ac1f7ee02d7909944af493c5794dbd70fb7b53a1)
henryso added a commit to henryso/gregorio that referenced this issue Apr 17, 2015
henryso added a commit to henryso/gregorio that referenced this issue Apr 17, 2015
@henryso
Copy link
Contributor

henryso commented Apr 17, 2015

I decided to just target both. If we decide not to include in release-3.0, close #285.

@eschwab
Copy link
Contributor

eschwab commented Apr 17, 2015

If it passes all the tests, then it would be good for release-3.0.

@henryso
Copy link
Contributor

henryso commented Apr 17, 2015

Yes, it passes all the tests I expect it to pass. There are some tests which are known different in develop because of bug fixes and new features. I don't expect release-3.0 to pass them.

@eroux
Copy link
Contributor

eroux commented Apr 17, 2015

I'd be in favor of both develop and release-3.0 too, thanx for the fix!

henryso added a commit that referenced this issue Apr 17, 2015
Corrected to use "torculus liquescens" only if the last note is actually liquescent. Fixes #284.
henryso added a commit that referenced this issue Apr 17, 2015
Corrected to use "torculus liquescens" only if the last note is actually liquescent. Fixes #284.
@henryso henryso closed this as completed Apr 17, 2015
henryso added a commit to henryso/gregorio that referenced this issue Apr 17, 2015
henryso added a commit that referenced this issue Apr 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants