Hi Davide,
please tell us what output you expected.
Am 06.01.19 um 18:41 schrieb Malte Meyn:
Long answer: You can do almost anything in LilyPond. In your case you
could try changing the output (f. e. extra-offset) or the inpult (f. e.
use multiple voices). But you have to know what the output should look
like. LilyPond cannot guess that ;)
Apart from that: Please read http://lilypond.org/bug-reports.html
If you find a bug (or something that *might* be a bug) you should
contact the bug mailing list first and don’t create issues on
sourceforge yourself. If the problem is considered a bug by others too,
it will added to the tracker (and marked “Accepted” instead of “New”). A
simple „I haven’t got a satisfying answer on the user list for two days“
doesn’t qualify a problem to be a bug ;)
You set yourself as owner of the issues you created (5454, 5455, 5457,
5458). That field normally tells who is working on that issue. I see
that you proposed some changes in the comments. New developers are
always welcome! Please have a look at the Contributor’s Guide:
http://lilypond.org/doc/v2.19/Documentation/contributor/ There you’ll
find how to make patches using git. You can either ask for write access
to the issue tracker and use the tool git-cl to put your patches into
the regular review cycle or email them to the devel list, see
http://lilypond.org/doc/v2.19/Documentation/contributor/patches
Cheers,
Malte
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
