Re: Stockhausen example on the website is missing
"Werner LEMBERG" wrote in message news:20190924.123549.280351908689490651...@gnu.org... There are actually 2 files needed - the standard one and the -small one - and I don't remember how they're created - I don't have my "lilypond" PC on now, but perhaps make doc might make them? See https://github.com/gperciva/lilypond-extra/tree/master/ly-examples If you can get the 2 updated files to me, I can shepherd them through the system. I'll send them to you privately. Werner Now fixed. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stockhausen example on the website is missing
"Werner LEMBERG" wrote in message news:20190924.113502.353123979764742385...@gnu.org... It's a long time since I did this, but I think to update the example pictures, you have to create updated versions locally, push them to the lilypond-extra repo and then pull those on the website and copy them to the web directory. OK. However, my main question is why this happened at all. IMHO, the web site should *not* be automatically influenced by changes in the git repository! Am I wrong? OK, I'm wrong. I read that the HTML part of the website gets rebuilt hourly by a cronjob. Now I know, and sorry for the mess. Phil, could you fix this single image file easily? There are actually 2 files needed - the standard one and the -small one - and I don't remember how they're created - I don't have my "lilypond" PC on now, but perhaps make doc might make them? See https://github.com/gperciva/lilypond-extra/tree/master/ly-examples If you can get the 2 updated files to me, I can shepherd them through the system. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stockhausen example on the website is missing
"Werner LEMBERG" wrote in message news:20190924.105812.165533443397772451...@gnu.org... the example on http://lilypond.org/examples.html#Customized-Output is missing: http://lilypond.org/ly-examples/stockhausen-klavierstueckII.png is not found. Hmm, weird. I've renamed it in a recent commit for orthogonality with other examples. The old name is http://lilypond.org/ly-examples/Stockhausen_Klavierstueck2.png and this file is present. How comes that the HTML code from http://lilypond.org/examples.html is sensitive to recent changes in `staging' or `master' without updating the images? For example, the Schenker graph image is still the one coming with 2.19.83. This definitely looks like a bug. See http://lilypond.org/doc/v2.19/Documentation/contributor/uploading-and-security It's a long time since I did this, but I think to update the example pictures, you have to create updated versions locally, push them to the lilypond-extra repo and then pull those on the website and copy them to the web directory. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Stockhausen example on the website is missing
"Malte Meyn" wrote in message news:835588f6-996a-af2b-27cc-086ac559b...@maltemeyn.de... Hi list, the example on http://lilypond.org/examples.html#Customized-Output is missing: http://lilypond.org/ly-examples/stockhausen-klavierstueckII.png is not found. Cheers, Malte I think Werner must have changed the name with his recent update. It's now there as http://lilypond.org/ly-examples/Stockhausen_Klavierstueck2.png -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Broken URL / Documentation Help
"Ben L." wrote in message news:e8f7c2b9-171d-5077-a3fd-1e608c067...@gmail.com... Hello, I hope you all are doing well. May I ask for a little help with something? Could someone please assist me by changing a few URL links that I noticed are no longer functioning correctly? My website domain has changed and finally stabilized. I am unsure how to handle this kind of request, sorry I lack the experience with any sort of patch upload / review process here. I would be very appreciative of any help with this. I believe the links in the "Pondings" section of the LilyPond website as well as within the documentation are still pointing to the old domain for my resources. My current domain is now permanent and securely hosted. My website address is now: https://benl.xyz/lilypond/operation-lilypond Which replaces all instances of: http://benlemon.me/blog/music/lilypond/operation-lilypond */Documentation/web/text-input (Beginner Documentation) I think is one... - I have been so happy to hear from users who have discovered LilyPond and found their way to my introductory learning material, while finding it to be helpful to them. I only just realized now that the links were dead. Thank you for helping me with the URLs. And a big thank you to everyone who has helped and done so much for the LilyPond community! From development to maintaining the outstandingly comprehensive documentation, we appreciate you! :) Have a great day, Ben Anyone wanting to do this quickly will need to update Documentation/web/server/tweets.xml. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: rest + fermata
- Original Message - From: "Martin Tarenskeen" To: "lilypond-user mailinglist" ; "bug-lilypond mailinglist" Sent: Sunday, April 14, 2019 12:38 PM Subject: rest + fermata Hi, This is strange: %%% start of tiny example \version "2.19.83" { r1\fermata R1\fermata } %%% end of tiny example r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed. Is this a bug? -- MT See http://lilypond.org/doc/v2.19/Documentation/notation/expressive-marks-attached-to-notes \fermataMarkup -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Dispositioned notehead in chord when staffsize=14 and clef=bass
- Original Message - From: "Federico Bruni" To: "Martin Tarenskeen" Cc: "bug-lilypond mailinglist" ; "lilypond-user mailinglist" Sent: Sunday, March 24, 2019 5:14 PM Subject: Re: Dispositioned notehead in chord when staffsize=14 and clef=bass Il giorno dom 24 mar 2019 alle 14:22, Martin Tarenskeen ha scritto: Hi, A bumped into a strange bug with a dispositioned notehead. See attached example "staffsize14.ly" and "staffsize14.pdf" output. Using lilypond 2.19.82 on Linux Fedora. What's happening here? I confirm it. Same problem with a lilypond binary built from the translation branch. Version 2.18.2 works correctly. 2.18 doesn't scale the staff space, so there's a lot of room for the noteheads. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond 2.19.82 with multiple voices seems to fail
"DaveAtkinson" wrote in message news:1551630991699-0.p...@n5.nabble.com... Dear LilyPond folks Thanks so much for taking an interest. First, I forgot two important pieces of information - yes, I am using Windows... (hangs head in shame) and it has 16 Gb of memory.. The OS is 64 bit, but I don't suppose that matters to lilypond as compiled for windows..? So interesting... it is clear that overuse of the << \\ >> construct causes issues. I would welcome comments about how to re-write the score without it. If the correct way to do it is then an affirmation would be sufficient rather than a tutorial, which would be greatly appreciated otherwise ;-). I can't see your example, but I would do your first two bars like this: global = { \key f \major \time 3/4 } rhnotesupper = \relative c' { \clef treble \global \tempo 4=83 s4 s 16-.( -. -. -.) | \voiceOne -.( -. -. -.) \oneVoice 16-.( -. -. -.) -.( -. -. -.) | } rhnoteslower = \relative c' { \clef treble \global \tempo 4=83 s1*3/4 | \voiceTwo 4 s s | } lhnotesupper = \relative c { \clef bass \global \voiceOne 16-.( -. -. -.) -.( -. -. -.) \oneVoice 4 | s | } lhnoteslower = \relative c { \clef bass \global \voiceTwo f,,4\sustainOn | s1*3/4 | } \score { \new PianoStaff \with { instrumentName = #"Piano" } << \new Staff = "upper" << \new Voice = "top" \rhnotesupper \new Voice = "next" \rhnoteslower >> \new Staff = "lower" << \new Voice = "topLH" \lhnotesupper \new Voice = "nextLH" \lhnoteslower >> >> \layout { } \midi { } } The first, I confess to sometimes using lilypond to generate midi files from piano accompaniments so that I can practise the main part when I don't have the luxury of a pianist (which is almost all the time). I am therefore copying existing scores. In order to eliminate (!) mistakes, I do it a few bars at a time, as corrections are much easier for me to do in the last few bars. If I were to use two voices for the whole of a staff, once I'd written the first staff, going back and finding the places where two voices are required, and filing in all the spaces, is tedious and taxing for me... I create music (normally from renaissance polyphony) and simply have four voices and add a few bars to each at a time. I then compile, check and add a few more bars to each. My only other suggestion (which Kieren, a regular contributor and composer would agree with) is that you might find not using \relative means it's easier to keep track of which octave you're currently in. The second reason, if I were to write a staff as two lines, all the parts where there is effectively only a single voice look horrible, because all the rests and note stems look wrong. \oneVoice, \voiceOne, \voiceTwo etc. are your friends. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Re: Re: The Stem of Longa notes is short when Baroque Noteheadstyle is used
A mensural maxima might work for the OP. Before requesting a change to the baroque glyph, I would certainly want to see scans of example noteheads from the period. \override Staff.NoteHead.style = #'mensural b\maxima*1/2 -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF docs for 2.19.82 broken/missing fonts
"David Kastrup" wrote in message news:878t705hzo@fencepost.gnu.org... "Phil Holmes" writes: news:87d0wc5lzt@fencepost.gnu.org... Knut Petersen writes: Would you show us the GUB's whole lilypond-doc log file? If you preserve the 2.19.81 (Jan. 2018) lilypond-doc log file, I'd like to compare the 2.19.82 log file (broken PDFs) and the 2.19.81 log file (correct PDFs). Zipped versions of both log files are attached. Hope this helps. To me both logs prove that building of e.g. the english notation.pdf succeeded and that the survival of the original pdf generated by xetex is impossible. Unfortunately reality proves something different. Can it be verified whether or not the logs stem from a run actually producing the respective valid and/or invalid PDF files or not? They are the only make doc logs on my GUB machine from the dates when I built 19.81 and 19.82, so they must be. Ah ok, I wasn't aware that they were actual historic records. Seems like a puzzler. I'll take a look as well and see whether I have better luck inventing some theory of what may have transpired here. Do we have an idea whether this is reproducible? -- David Kastrup I've not re-run GUB since the uploaded version. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF docs for 2.19.82 broken/missing fonts
They are the only make doc logs on my GUB machine from the dates when I built 19.81 and 19.82, so they must be. -- Phil Holmes "David Kastrup" wrote in message news:87d0wc5lzt@fencepost.gnu.org... Knut Petersen writes: Would you show us the GUB's whole lilypond-doc log file? If you preserve the 2.19.81 (Jan. 2018) lilypond-doc log file, I'd like to compare the 2.19.82 log file (broken PDFs) and the 2.19.81 log file (correct PDFs). Zipped versions of both log files are attached. Hope this helps. To me both logs prove that building of e.g. the english notation.pdf succeeded and that the survival of the original pdf generated by xetex is impossible. Unfortunately reality proves something different. Can it be verified whether or not the logs stem from a run actually producing the respective valid and/or invalid PDF files or not? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF docs for 2.19.82 broken/missing fonts
The only reference to make doc in the logfile I produce as GUB output is: cd /home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/ && make DOCUMENTATION=yes dist -- Phil Holmes "Knut Petersen" wrote in message news:b056a50c-cd65-b797-572d-fb99592fa...@t-online.de... Would you show us the GUB's whole lilypond-doc log file? If you preserve the 2.19.81 (Jan. 2018) lilypond-doc log file, I'd like to compare the 2.19.82 log file (broken PDFs) and the 2.19.81 log file (correct PDFs). Zipped versions of both log files are attached. Hope this helps. To me both logs prove that building of e.g. the english notation.pdf succeeded and that the survival of the original pdf generated by xetex is impossible. Unfortunately reality proves something different. As gub does not run here: It would be nice to know the exact commands gub executes to build lilypond and its documentation. Knut ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF docs for 2.19.82 broken/missing fonts
- Original Message - From: "Knut Petersen" Yes. notation.pdf looks as if extractpdfmark/gs was not used. But the part of the build log Phil published clearly proves that extractpdfmark and ghostscript were used. @Phil: If you have a look at the notation.pdf in the build tree: is that file ok or is the same broken version as published on lilypond.org? Please see the attached outcome from piping find to ls -l. As you see the English notations vary in size, and the small ones lack the embedded fonts. -- Phil Holmes gub@gub-VirtualBox:~/NewGub/gub$ find . -name 'notation.pdf' -exec ls -lah {} \; -rw-r--r-- 1 gub vboxsf 4.3M Jun 24 13:43 ./uploads/localdoc/v2.19.82/Documentation/notation.pdf -rw-rw-r-- 1 gub lilypond 4.3M Jun 24 13:43 ./uploads/webdoc/v2.19.82/Documentation/notation.pdf -rw-r--r-- 2 gub vboxsf 4.3M Jun 24 13:43 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/out-www/online-root/Documentation/notation.pdf -rw-r--r-- 2 gub vboxsf 4.3M Jun 24 13:43 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/out-www/offline-root/Documentation/notation.pdf -rw-r--r-- 1 gub vboxsf 6.5M Jun 24 13:44 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/Documentation/out-www/notation.pdf -rw-r--r-- 1 gub vboxsf 7.0M Jun 24 13:50 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/Documentation/es/out-www/notation.pdf -rw-r--r-- 1 gub vboxsf 6.8M Jun 24 13:46 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/Documentation/ca/out-www/notation.pdf -rw-r--r-- 1 gub vboxsf 6.8M Jun 24 13:54 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/Documentation/it/out-www/notation.pdf -rw-r--r-- 1 gub vboxsf 7.0M Jun 24 13:52 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/Documentation/fr/out-www/notation.pdf -rw-r--r-- 1 gub vboxsf 6.4M Jun 24 13:48 ./target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/Documentation/de/out-www/notation.pdf gub@gub-VirtualBox:~/NewGub/gub$ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF docs for 2.19.82 broken/missing fonts
"Knut Petersen" wrote in message news:c0867765-18e7-9540-4843-a9f5470d7...@t-online.de... Hi everybody! The most interesting hint is that only the english version of notation*pdf in the broken GUB build is affected. *It would be very helpfull to know the answer to the following question:** **Which commands / scripts are used to build lilypond during the gub build? * I've grepped the make doc log for "notation.pdf" from the weekend GUB build and it's attached as a file. Not sure how this will work via a newsgroup so if you want the file directly please send an email to devel and I'll send it there as well. To my eye the build syntax for the UK and other language builds looks identical. -- Phil Holmes notationpdf.log Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: commit 12fe78825798191ecb7e5a4ee3064679773ae1ab is broken
"James Lowe" wrote in message news:E1fReNj-0003az-Ki@rmmprod07.runbox... [snip] I then ran through the diff files visually and only 2 files showed diffs; test-output-distance (obviously) and 'rest-dot-positions' (again I believe this is also expected at the moment) but not other files showed any diffs. Thanks again for your consideration. James James, What Knut is saying is that there is more than the expected variation in the test-output-distance test. Not only have the notes moved as expected, but also the staccato mark has been incorrectly changed. Have a detailed look at the last note of t-o-p and check whether it is a staccato. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond 2.19.80-1 hangs
"Paul Hodges" <p...@cassland.org> wrote in message news:AFDB7302AE99EAB9466F95A3@[192.168.1.74]... PS - The group of commented lines near the end are the version I changed it to for successful compilation; the three following lines are the version I restored to bring back the fault. Paul -- Paul Using exactly the version on the web, 2.19.80, Windows Vista (really..). No crash. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: crash during musicxml2ly
Please see http://lilypond.org/doc/v2.19/Documentation/contributor/patches -- Phil Holmes "Frédéric Gohier" <fgohie...@hotmail.com> wrote in message news:he1pr1001mb140284687c61080bd2d06ee9ba...@he1pr1001mb1402.eurprd10.prod.outlook.com... hello, I face a crash when run the command line : /usr/local/bin/musicxml2ly --nd --nrp --npl --no-beaming -m MusicXMLV2_from_sibelius7.xml the traceback is : Traceback (most recent call last): File "/usr/local/bin/musicxml2ly", line 3277, in main() File "/usr/local/bin/musicxml2ly", line 3271, in main voices = convert(filename, options) File "/usr/local/bin/musicxml2ly", line 3157, in convert update_score_setup(score, part_list, voices, parts) File "/usr/local/bin/musicxml2ly", line 3027, in update_score_setup score_structure.set_part_information(part_id, staves_info) File "/usr/local/share/lilypond/2.21.0/python/musicexp.py", line 2351, in set_part_information self.contents.set_part_information (part_id, staves_info) File "/usr/local/share/lilypond/2.21.0/python/musicexp.py", line 2135, in set_part_information c.set_part_information (part_name, staves_info) AttributeError: PartGroupInfo instance has no attribute 'set_part_information' I correct this issue by modifying * in file git/python/musicexp.py : * in class StaffGroup : * in function set_part_information : def set_part_information (self, part_name, staves_info): if part_name == self.id: self.part_information = staves_info else: for c in self.children: +if hasattr(c, 'set_part_information'): +c.set_part_information (part_name, staves_info) -c.set_part_information (part_name, staves_info) I don't know the process to validate and don't remember the process to push a modification on git server. please can you help me ? Cordialement, GOHIER Frédéric ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond Downloads broken?
- Original Message - From: "Urs Liska" <li...@openlilylib.org> To: "Han-Wen Nienhuys" <hanw...@gmail.com>; "Phil Holmes" <m...@philholmes.net> Cc: "lilypond-user" <lilypond-u...@gnu.org>; "bug-lilypond" <bug-lilypond@gnu.org>; "Jan Nieuwenhuizen" <jann...@gnu.org> Sent: Wednesday, March 14, 2018 10:21 AM Subject: Re: LilyPond Downloads broken? Am 14.03.2018 um 11:19 schrieb Han-Wen Nienhuys: You are correct on both counts. The SSH key wasn't copied over to the new server, and that's been a blessing since the account was compromised. Can you point the download link to lilypond.org directly? Bandwidth prices have gone down in the last 10 years, so I think we should be fine. Should there be an archive of all previous releases like on linuxaudio.org or do we have to limit this to the current stable and development releases? It's there as a part of the normal release process. Historically I have deleted some of the source files, etc., to clear some space from an overfull disk. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond Downloads broken?
a) Han-Wen b) Jan -- Phil Holmes - Original Message - From: Urs Liska To: Phil Holmes ; lilypond-u...@gnu.org ; bug-lilypond Cc: Han-Wen Nienhuys ; Jan Nieuwenhuizen Sent: Wednesday, March 07, 2018 3:22 PM Subject: Re: LilyPond Downloads broken? Am 07.03.2018 um 16:11 schrieb Phil Holmes: The lack of the latest files on the linuxaudio site isn't something I can fix. My understanding is that the situation used to be that lilypond.org used to run a cron job that scp'ed the binaries to linuxaudio. However, this stopped working when a) Han-Wen changed the hosting of lilypond.org or b) there was a problem with linuxaudio and it had to be rebuilt. I assume it was the latter. Somewhere I read a blog post about their server being hacked and completely rebuilt in a new infrastructure. Obviously our uploads don't work anymore since then. I assume that there is not the correct certificate on the new lilypond.org system. The cron job was set up by Jan, and the login I use has no access to it. The simplest solution might be to change to simply pointing all downloads to the lilypond.org server. I think we didn't do this in the past to lower the load on the server, but the new infrastructure might not see that as a problem. Well, at least currently it's the problem that the links point to a 404 error page. a) Who knows whether it is acceptable to permanently host the binaries on lilypond.org (somehow I doubt that is an option)? b) Who knows how much work it will be to get the hosting on linuxaudio.org to be working again? If either a) is the way to go or b) is suspect of taking more time (than say, a few days) we should temporarily update the links on the download page. Urs Copied to Jan and Han-Wen for their thoughts. -- Phil Holmes - Original Message - From: Urs Liska To: lilypond-u...@gnu.org ; bug-lilypond Sent: Wednesday, March 07, 2018 3:00 PM Subject: Re: LilyPond Downloads broken? (Cross-posting to bug-lilypond) Am 07.02.2018 um 16:22 schrieb Phil Holmes: Available from http://lilypond.org/downloads/binaries/ currently. Any information on how long this situation will last? I think we should consider updating the website, even if it's temporary. Urs -- ___ lilypond-user mailing list lilypond-u...@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond Downloads broken?
The lack of the latest files on the linuxaudio site isn't something I can fix. My understanding is that the situation used to be that lilypond.org used to run a cron job that scp'ed the binaries to linuxaudio. However, this stopped working when a) Han-Wen changed the hosting of lilypond.org or b) there was a problem with linuxaudio and it had to be rebuilt. I assume that there is not the correct certificate on the new lilypond.org system. The cron job was set up by Jan, and the login I use has no access to it. The simplest solution might be to change to simply pointing all downloads to the lilypond.org server. I think we didn't do this in the past to lower the load on the server, but the new infrastructure might not see that as a problem. Copied to Jan and Han-Wen for their thoughts. -- Phil Holmes - Original Message - From: Urs Liska To: lilypond-u...@gnu.org ; bug-lilypond Sent: Wednesday, March 07, 2018 3:00 PM Subject: Re: LilyPond Downloads broken? (Cross-posting to bug-lilypond) Am 07.02.2018 um 16:22 schrieb Phil Holmes: Available from http://lilypond.org/downloads/binaries/ currently. Any information on how long this situation will last? I think we should consider updating the website, even if it's temporary. Urs -- ___ lilypond-user mailing list lilypond-u...@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond Download does not work!
"Andrew Bernard" <andrew.bern...@gmail.com> wrote in message news:cak5qfnuzugylitkjjzt5esd+oohr6nygbqtb8arypdmkl1s...@mail.gmail.com... Hi Phil, This is what I keep exhorting people to do - use the latest version. This is probably a Frequently Issued Response :-) on the list by now! I know 2.20 has not come out yet, and when it does 2.18.2 will be obsolete, but at the risk of inflaming controversy, isn't about time we started recommending people to go to the 2.19 series? Again, I am sure the unnecessarily self-deprecating open source humility of referring to development versions as 'unstable' puts people off needlessly. List helpers effectively have to support two streams. I don't have a 2.18.2 installation so I generally ignore questions about that version. I know this is all problematical, but it would appear that 2.20 is not coming out in the forseeable future (tell me it will be soon!), so let's admit that the 2.91.81 and so on are pretty good and very trouble free, and let new users know on the website. Andrew As you say, LilyPond "unstable" is generally pretty stable. However, we have had issues with unstable releases that do make them pretty near unusable, so I generally would not recommend new users to start with an unstable version. In this case, I recommended 2.19.81 since it is a pre-release for a new stable release. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond Download does not work!
"Gunda Hagmüller" <gu...@gundahagmueller.info> wrote in message news:f6e6780485a1ba8f22c0a76290bc6...@gundahagmueller.info... Hi! I wanted to download LilyPond 2.18.2 for Windows, but the link http://download.linuxaudio.org/lilypond/binaries/mingw/lilypond-2.18.2-1.mingw.exe can not be found! Kind regards Gunda Try http://lilypond.org/downloads/binaries/mingw/ Note that this is quite an old version, and 2.19.81 is quite stable. You may benefit from using that instead. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make top-doc fails: could not open out/NEWS.texi: No such fileordirectory
There were changed made to the way news is handled in https://sourceforge.net/p/testlilyissues/issues/4962/. Perhaps this broke top-doc?? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: repeatTie and staff-position
"Malte Meyn" <lilyp...@maltemeyn.de> wrote in message news:91fbce53-6cc1-9f42-7819-52a50ad96...@maltemeyn.de... Hi list, someone on the german forum asked whether the following is a bug (https://lilypondforum.de/index.php/topic,216.0.html): RepeatTies are longer if the NoteHead lies between two staff lines, but not always. As I found out, they seem to be longer IFF both the NoteHead and the RepeatTie lie inside the staff. For example code see below (same output in 2.18.2 and earlier stable versions). But shouldn’t all RepeatTies either have the same length or be longer also if only one of RepeatTie and NoteHead are inside the staff (f. e. g'' and f' with \stemUp in 5-line treble clef)? I don't see a problem here. There's lots of stuff about tie size and placing in Gould, but she says (amongst other stuff) "Where there is plenty of space the tie starts and finishes at the centre of the notehead." "Where the tie needs to be brought closer to the notehead ... the ends of the tie align with the edge of the notehead." -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make top-doc fails: could not open out/NEWS.texi: No such file ordirectory
"Karl Lindén" <karl.j.lin...@gmail.com> wrote in message news:cdb1d874-77b5-00f8-8fd0-183081015...@gmail.com... On current master (8d889e9837) "make top-doc" fails. I found this downstream in Gentoo because the package build script tries to install README.txt which does not get built due to the "make top-doc" failure. I've never tried to run make top-doc. How is this different from make doc? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: a contribution
- Original Message - From: "James Lowe" <james.l...@runbox.com> To: "Phil Holmes" <m...@philholmes.net> Cc: "bug-lilypond" <bug-lilypond@gnu.org> Sent: Friday, November 24, 2017 7:07 PM Subject: Re: a contribution Phil, On Wed, 15 Nov 2017 11:04:17 -, "Phil Holmes" <m...@philholmes.net> wrote: > Betreff: a contribution > Datum: Tue, 14 Nov 2017 10:28:15 -0800 > Von: Bill Palmer <w...@mac.com> > An: u...@openlilylib.org > > The music sample shown on the page http://lilypond.org/text-input.html > does not correspond with the source code shown on that page! > Specifically, > the bassoon notes have a g in the code but a c in the output. d f gis g > is > what is written, but the music shown is produced by d f gis c. This is unlikely to be terribly trivial to fix, since most of the contributions on that page are custom images. Does anyone know whether this is real music or just made up? Actually the source files are SVG and those are trivial to edit with Inkscape. Then one can export them as PNG files. However what I *have* noticed is that this example (text-input-parts-both-annotate.svg) has all the 'main' languages and their corresponding PNG file except the 'ca' one (Catalan), this has a PNG but no source. My limited knowledge of Spanish, I wondered if the same SVG file had been used and just renamed with the 'ca' extentsion, but looking at the two PNG files I can see the accents on one letter slope in different directions. That doesn't mean it wasn't still taken from the 'es' SVG file but anyway, it seems a trivial patch. Is it enough to edit the SVG files or do I also have to include the PNGs (i.e. are the PNGs autogenerated?) and finally, do I need to make copies of the PNGs in the lilypond-extras dir? I get confused with this part and images. Thanks James = Sorry for the massive delay in replying. I'm not certain of the workflow for this, but would very strongly expect that the PNG files have to be created manually and uploaded to lilypond-extra. That's normally the case with pictures, and I can't see any evidence of them being built in the makefiles. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: a contribution
Betreff: a contribution Datum: Tue, 14 Nov 2017 10:28:15 -0800 Von: Bill Palmer <w...@mac.com> An: u...@openlilylib.org The music sample shown on the page http://lilypond.org/text-input.html does not correspond with the source code shown on that page! Specifically, the bassoon notes have a g in the code but a c in the output. d f gis g is what is written, but the music shown is produced by d f gis c. This is unlikely to be terribly trivial to fix, since most of the contributions on that page are custom images. Does anyone know whether this is real music or just made up? One other point - this snippet has \set Score.skipBars = ##t. That construct is used frequently in the manuals but never explicitly explained. The NR uses \compressMMRests. Any idea why the two constructs and the mixed usage? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: tabs with lyrics
"bb" <bb-543...@telecolumbus.net> wrote in message news:054ad4b5-cd65-9e9e-74bf-1e554376b...@telecolumbus.net... One more silly question, tabs with lyrics. I did not find any help in the archives. I tried it this way: \version "2.19.2" tune = {\clef "treble_8" a b c d e f g } \score { << \new Staff { \tune } \new TabStaff = tab \relative c'' { \tune } \new Lyrics { \lyricsto "tab" { Here are the words } } >> } Did you look at the error message this produces? warning: cannot find Voice `tab' \new Lyrics { \lyricsto "tab" { Here are the words } } A good hint that lyrics work with voices: \new TabStaff { \new TabVoice = tab { \relative c'' { \tune } } } -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \lyricsto ruins sequential lyrics
"Dan Eble" <d...@faithful.be> wrote in message news:c474df11-0db5-41ec-8e4b-abc890c5b...@faithful.be... [copying the bug list this time—sorry] David wrote: Putting different lyrics in sequence to each other does not make a lot of sense, Isn’t it fundamental to performing a multi-stanza song? This is how I do multi-stanza songs: music = \relative c'' { c2 c c c } \new Staff << \new Voice = "4" \music \new Lyrics \lyricsto "4" { Aa Bb Cc Dd } \new Lyrics \lyricsto "4" { Ee Ff Gg Hh } It works exactly as I would expect. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: partcombine does not work with tremolo repeats
"Ulrik Serges" <ul...@serges.dk> wrote in message news:6fdb4c7d-1f9c-3dea-59dd-fc5293e1c...@serges.dk... Hello, I have problems using tremolo repeats with partcombine. The following code returns errors and doesn't produce the correct output: \version "2.19.65" \new Staff << \partcombine \relative c' { \time 3/4 \repeat tremolo 6 {e16 g16} e2. } \relative c' { \time 3/4 c2. c2. } >> Tested with versions 2.18.2 and 2.19.65. Can you look into it or is there any workaround? With kind regards, Ulrik Serges I'm guessing it's a problem with autobeaming, as hinted in the note to http://lilypond.org/doc/v2.19/Documentation/notation/beams A workaround (albeit with errors in the log file) would be: \new Staff { \set Staff.autoBeaming = ##f \partcombine \relative c' { \time 3/4 \repeat tremolo 6 {e16 [ g16 ]} e2. } \relative c' { \time 3/4 c2. c2. } } -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: intent bug on line start
"David Kastrup" <d...@gnu.org> wrote in message news:87r2w9t1q1@fencepost.gnu.org... bb <bb-543...@telecolumbus.net> writes: With indent = 0\mm activated the first bar will be wrong, as the first notes of voice one and two align. They should not becauser of r8 (\voiceOne ) and r16 (\voiceTwo ) in front. Without, say % indent = 0\mm commented out the layout is correct. Cannot see the described effect. However: Looks like a bug in 2.18 (possibly shows because setting the indent compresses the music more) which has been fixed in 2.19.xx (where xx is 47 when I tried this). -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: accidentals on merged notes
"Hauke Rehr" <homo_la...@yahoo.de> wrote in message news:598f1941.7090...@yahoo.de... Hello, searching for this bug on sf using terms “accidentals + merged”, I found only #546 said to have been solved for ages. Still, the output doesn’t match at least /my/ expectations: notes should either not be merged at all, or there should be stacked accidentals indicating which one applies to which Voice. find attached a minimal example If I add a ! to the note on the third beat in the upper voice, I get at least both a natural and a sharp sign, leaving it to the reader which belongs to which Voice, but it still doesn’t help with the case on the second beat. regards, Hauke Rehr (from Germany) Looks the same as https://sourceforge.net/p/testlilyissues/issues/1134/ ? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unofficial MusicXML test suite access problem
- Original Message - From: "Thomas Morley" <thomasmorle...@gmail.com> To: "Phil Holmes" <m...@philholmes.net> Cc: "bug-lilypond" <bug-lilypond@gnu.org> Sent: Friday, May 26, 2017 11:01 AM Subject: Re: Unofficial MusicXML test suite access problem Clicking on p.e. the first file-name i.e. ‘01a-Pitches-Pitches.xml’ I get The requested URL /doc/v2.19/input/regression/musicxml/42/lily-db220724.xml was not found on this server. Apache/1.3.34 Server at lilypond.org Port 80 for both: Firefox and Chromium Cheers, Harm I agree with that - it's been like that for a _long_ time, but I can't find a bug report. It's nothing to do with the OP's report, though. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: XML to .ly and Lilypond, again
- Original Message - From: "Urs Liska" <u...@openlilylib.org> To: <lilypond-u...@gnu.org>; <bug-lilypond@gnu.org> Sent: Friday, May 12, 2017 11:00 AM Subject: Re: XML to .ly and Lilypond, again Am 12.05.2017 um 11:26 schrieb Jan-Peter Voigt: Dear Leszek, when I look with hexdump, I see a lot of NUL-bytes inside the file. And it seems to me that the strings are in UTF-16 and the rest in latin-1 or the like. At least it seems like a mixture of encodings. I think this is exactly what was discussed in the mentioned recent thread. So it seems this is an issue in musicxml2ly that has recently been introduced. Does anyone know or can anyone find out when this happened (by trying musicxml2ly from different LilyPond versions)? Urs See https://sourceforge.net/p/testlilyissues/issues/4751/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in web documentation
"Giulio Agostini" <giulio.agost...@gmail.com> wrote in message news:cafkm-5gpr+qwjrp1ubc8t2fiods4re9a7excdgk5bcw0csn...@mail.gmail.com... Hi there, Thanks for this wonderful application. Just a quick note to flag a typo in the web download instructions for Windows http://lilypond.org/windows.html " *Note:* DIR will generally be C:\Program Files (x86) for 64 bit or C:\Program Files for 32 bit systems. " It should be the other way round. Cheers, Giulio Don't think so. For old 32 bit versions of Windows, there was no distinction between 64 and 32 bit applications - they all went in C:\Program Files. For 64 bit versions, 64 bit applications go in C:\Program Files but 32 bit ones go in C:\Program Files (x86). -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Color of lyric hyphen
"Urs Liska" <u...@openlilylib.org> wrote in message news:c9cf8325-f7c8-6ca1-853b-b28119f31...@openlilylib.org... Am 29.03.2017 um 14:45 schrieb David Kastrup: Urs Liska <u...@openlilylib.org> writes: Am 29.03.2017 um 12:53 schrieb David Kastrup: Urs Liska <u...@openlilylib.org> writes: But as you can see in the attached image it remains black, while the extender and the text itself are correctly colored. Did I misinterpret what LyricHyphen is or is this a bug? This is a regression due to commit 2dc76513c4edb8e18e6170069677eb0dd9b54209 Author: Knut Petersen <knut_peter...@t-online.de> Date: Sat Mar 4 18:10:19 2017 + LyricHyphen whiteout Issue 5033 Thanks for the info. Can I expect this to be fixed in 2.19.58 or do I have to go back to 2.19.54 for this project? 2.19.58 is already out and the regression is present in current master. At the current point, no issue is recorded for the problem, no work is in progress for fixing it, and I don't see that the "whiteout" issue has a color model other than black and white considered yet. OK, thanks. The above commit appears first in 2.19.57. Sorry, that was a typo, I meant going back to 2.19.56. Could the bug squad please open an issue for this? https://sourceforge.net/p/testlilyissues/issues/5110/ -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \tempo should accept floats
"Urs Liska" <u...@openlilylib.org> wrote in message news:cc89b397-6b28-9130-e263-8ad4a7a4e...@openlilylib.org... As discussion on https://github.com/wbsoft/python-ly/pull/90 shows floating point metronome numbers are surely something LilyPond should provide. \tempo 8 = 60.0 => error: syntax error, unexpected REAL I don't see how this is different from using accepted notation of \tempo 8 = 60. What would be the use case? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Copyright
"Urs Liska" <u...@openlilylib.org> wrote in message news:bbe7ead5-ea04-abcf-e08c-9a2ae3dce...@openlilylib.org... lilypond --version GNU LilyPond 2.19.57 Copyright (c) 1996--2015 by Han-Wen Nienhuys <han...@xs4all.nl> Jan Nieuwenhuizen <jann...@gnu.org> and others. This program is free software. It is covered by the GNU General Public License and you are welcome to change it and/or distribute copies of it under certain conditions. Invoke as `lilypond --warranty' for more information. Spot the error? The copyright notice gives 2015 instead of 2017. I did a git grep on Copyright but it seems there's much more to that than simply replacing one occurence, as (varying) copyright statements are scattered throughout the code. So, what's the procedure to update the copyright notice(s)? Urs I think this is the last time it was done: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=47db9a3883d726ca53e2133a3b2298f78dd6a32e -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Problem with make website
- Original Message - From: "Masamichi Hosoda" <truer...@trueroad.jp> To: <m...@philholmes.net> Cc: <bug-lilypond@gnu.org> Sent: Wednesday, March 15, 2017 1:58 PM Subject: Re: Problem with make website After a period of processing, I got this error: BSTINPUTS=/home/graham/lilypond/lilypond-git//Documentation/web \ python /home/graham/lilypond/trusted-scripts/bib2texi.py -s web \ -s /home/graham/lilypond/lilypond-git//Documentation/lily-bib \ -o out-website/others-did.itexi \ -q \ /home/graham/lilypond/lilypond-git//Documentation/web/others-did.bib sh: bibtex: command not found Bibtex exited with nonzero exit status!website.make:225: recipe for target 'out-website/others-did.itexi' failed make: *** [out-website/others-did.itexi] Error 1 I'm now assuming there's something on the server that's needed but not there but a full build has only been done so long ago that it's not been needed for a long time. Does that sound possible? Further suggestions? Your GUB environment is Ubuntu 14.04 LTS 32 bit, right? Would you show me the results of the following command? $ update-alternatives --display bibtex $ ls -l /usr/bin/bibtex $ ls -l /etc/alternatives/bibtex $ ls -l /usr/bin/bibtex.original $ dpkg -l | grep "texlive-binaries" It is a problem with the website server, rather than my GUB environment. GUB is building properly for me at present, but the server itself runs make website, and it seems the server admins may have not installed texinfo since upgrading it. Graham is investigating workarounds. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Problem with make website
"Federico Bruni" <f...@inventati.org> wrote in message news:1489420610.2197...@smtp.autistici.org... Il giorno lun 13 mar 2017 alle 16:32, Phil Holmes <m...@philholmes.net> ha scritto: "Federico Bruni" <f...@inventati.org> wrote in message news:1489416450.2197...@smtp.autistici.org... Il giorno lun 13 mar 2017 alle 14:52, Phil Holmes <m...@philholmes.net> ha scritto: I've sent this to -devel a few hours ago, but it's not appeared there - I frequently get problems getting mail started there. It's not something we test with patchy, so not impossible - make website is now failing so the new release is not showing on the home page. make: *** No rule to make target '/home/graham/lilypond/lilypond-git//Documentation/web/news-front.itexi', needed by 'out-website/web.xref-map'. Stop. Not sure I understand this - I think news-front has been deleted? Perhaps a remnant pointer to it in another file? I could reproduce your issue. Then I deleted the out-website dir and re-run 'make website'. And the build completed successfully. Thanks for your help. I renamed out-website and then ran this command: make -f website.make WEBSITE_ONLY_BUILD=1 website After a period of processing, I got this error: BSTINPUTS=/home/graham/lilypond/lilypond-git//Documentation/web \ python /home/graham/lilypond/trusted-scripts/bib2texi.py -s web \ -s /home/graham/lilypond/lilypond-git//Documentation/lily-bib \ -o out-website/others-did.itexi \ -q \ /home/graham/lilypond/lilypond-git//Documentation/web/others-did.bib sh: bibtex: command not found Bibtex exited with nonzero exit status!website.make:225: recipe for target 'out-website/others-did.itexi' failed make: *** [out-website/others-did.itexi] Error 1 I'm now assuming there's something on the server that's needed but not there but a full build has only been done so long ago that it's not been needed for a long time. Does that sound possible? Further suggestions? What you get from: which bibtex No output at all. In Debian testing I see that bibtex is a symlink which ultimately ends up in bibtex.original: # ls -l /usr/bin/bibtex lrwxrwxrwx 1 root root 24 feb 28 17:40 /usr/bin/bibtex -> /etc/alternatives/bibtex # ls -l /etc/alternatives/bibtex lrwxrwxrwx 1 root root 24 feb 28 17:40 /etc/alternatives/bibtex -> /usr/bin/bibtex.original # ls -l /usr/bin/bibtex.original -rwxr-xr-x 1 root root 128704 gen 11 14:45 /usr/bin/bibtex.original The package you need is: # dpkg -S /usr/bin/bibtex.original texlive-binaries: /usr/bin/bibtex.original but I would wait for Graham's comments... +1 -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Problem with make website
"Federico Bruni" <f...@inventati.org> wrote in message news:1489416450.2197...@smtp.autistici.org... Il giorno lun 13 mar 2017 alle 14:52, Phil Holmes <m...@philholmes.net> ha scritto: I've sent this to -devel a few hours ago, but it's not appeared there - I frequently get problems getting mail started there. It's not something we test with patchy, so not impossible - make website is now failing so the new release is not showing on the home page. make: *** No rule to make target '/home/graham/lilypond/lilypond-git//Documentation/web/news-front.itexi', needed by 'out-website/web.xref-map'. Stop. Not sure I understand this - I think news-front has been deleted? Perhaps a remnant pointer to it in another file? I could reproduce your issue. Then I deleted the out-website dir and re-run 'make website'. And the build completed successfully. Thanks for your help. I renamed out-website and then ran this command: make -f website.make WEBSITE_ONLY_BUILD=1 website After a period of processing, I got this error: BSTINPUTS=/home/graham/lilypond/lilypond-git//Documentation/web \ python /home/graham/lilypond/trusted-scripts/bib2texi.py -s web \ -s /home/graham/lilypond/lilypond-git//Documentation/lily-bib \ -o out-website/others-did.itexi \ -q \ /home/graham/lilypond/lilypond-git//Documentation/web/others-did.bib sh: bibtex: command not found Bibtex exited with nonzero exit status!website.make:225: recipe for target 'out-website/others-did.itexi' failed make: *** [out-website/others-did.itexi] Error 1 I'm now assuming there's something on the server that's needed but not there but a full build has only been done so long ago that it's not been needed for a long time. Does that sound possible? Further suggestions? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Problem with make website
I've sent this to -devel a few hours ago, but it's not appeared there - I frequently get problems getting mail started there. It's not something we test with patchy, so not impossible - make website is now failing so the new release is not showing on the home page. make: *** No rule to make target '/home/graham/lilypond/lilypond-git//Documentation/web/news-front.itexi', needed by 'out-website/web.xref-map'. Stop. Not sure I understand this - I think news-front has been deleted? Perhaps a remnant pointer to it in another file? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Setting rehearsal mark value in non=default context
"Timothy Lanfear" <timo...@lanfear.me> wrote in message news:77070572-ed1b-720d-553d-d6e1fcac8...@lanfear.me... An integer argument to \mark is not respected if the mark engraver is moved from the Score context. The example creates rehearsal marks "A", "B", not "A", "C". \version "2.19.49" \layout { \context { \Score \remove "Mark_engraver" \remove "Staff_collecting_engraver" } \context { \Staff \consists "Mark_engraver" \consists "Staff_collecting_engraver" } } << \new Staff { R1 R1 R1 } \new Staff { R1 \mark \default R1 \mark #3 R1 } >> -- Timothy Lanfear, Bristol, UK. Please see http://lilypond.1069038.n5.nabble.com/Mark-numbering-incorrect-at-staff-level-td195296.html for exactly the same situation. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Mark numbering incorrect at staff level
"Thomas Morley" <thomasmorle...@gmail.com> wrote in message news:CABsfGyWZNStwtsKbot4xkjfromJuP9+NpPP7=8m+7qubmi3...@mail.gmail.com... 2016-10-12 15:45 GMT+02:00 Phil Holmes <m...@philholmes.net>: (Tried to send this to -devel, but nothing arrived). See the attached ME: music = { c''1 \mark \default c''1 \mark #6 c''1 c''1 \mark \default c''1 \mark \default c''1 \mark \default c''1 } \new Score \with { \remove "Mark_engraver" \remove "Staff_collecting_engraver" } { \new Staff \with { \consists "Mark_engraver" \consists "Staff_collecting_engraver" } { \music } } \new Score \with { } { \new Staff { \music } } As the attached image shows, the mark numbering is incorrect in the first score. Anyone know why? -- Phil Holmes Hi Phil, you wrote two Scores, the first moves the relevant engravers to Staff level. In the first Score the RehearsalMarks appear on top of the Staff (which is also the top-Staff of Score) In the second they appear on top of the top-Staff of the Score. All as it should be. But no visible diference, because each Score has only one Staff. But see a difference here: music = { c''1 \mark \default c''1 \mark #6 c''1 c''1 \mark \default c''1 \mark \default c''1 \mark \default c''1 } %% first Score \new Score \with { \remove "Mark_engraver" \remove "Staff_collecting_engraver" } { << \new Staff { \music } \new Staff \with { \consists "Mark_engraver" \consists "Staff_collecting_engraver" } { \music } } %% second Score \new Score \with { } { << \new Staff { \music } \new Staff { \music } } Maybe best you tell what you really want to achieve. The second score is "numbered" A F G H J, in line with the \mark #6 in the music. The first score is "numbered" A B C D E using the same input. I would have expected it to be A F G H J? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Mark numbering incorrect at staff level
(Tried to send this to -devel, but nothing arrived). See the attached ME: music = { c''1 \mark \default c''1 \mark #6 c''1 c''1 \mark \default c''1 \mark \default c''1 \mark \default c''1 } \new Score \with { \remove "Mark_engraver" \remove "Staff_collecting_engraver" } { \new Staff \with { \consists "Mark_engraver" \consists "Staff_collecting_engraver" } { \music } } \new Score \with { } { \new Staff { \music } } As the attached image shows, the mark numbering is incorrect in the first score. Anyone know why? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Tags and chord repetition
"Peter Crighton" <petecrigh...@gmail.com> wrote in message news:CAFGY_6LcWc2SgH-tojVECa_=kq92gy8-ml_8lzrbe-4imbn...@mail.gmail.com... Hello all, as posted on the User list, I came upon some unexpected behaviour, probably a bug, when using a tag on, for example, a markup that is attached to a chord repetition symbol. In the third measure the chord repetition symbol seems to get tagged as well, although only the markup should: \version "2.19.47" x = \tag #'tabstaff ^x music = \relative c { c4 c c c\x \x q q q q\x } \new StaffGroup << \new Staff \keepWithTag #'staff << \clef "treble_8" \music >> \new TabStaff \keepWithTag #'tabstaff << \tabFullNotation \music >> Cheers, Peter Added as https://sourceforge.net/p/testlilyissues/issues/4972/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Augmentation dot positioning
"Chris Yate" <chrisy...@gmail.com> wrote in message news:CAHHKLrSDrG=JSZEo2FyF3gAq0K39XyJ5-B4+DhDskOqJYF7=v...@mail.gmail.com... Hi, I've recently been discussing the issue of augementation dot positioning on the user mailing list with Werner Lemberg and others, and I think we've established that there's a bug. In many easy to reproduce situations, augmentation dots are placed incorrectly on chords. In general, too many dots are used, which is pretty confusing in the output (and can look ridiculous in especially busy, clustered chords). Werner pointed me towards the "chord-dots-limit" setting, which can help. But this is set by default to "3", which doesn't seem to make sense. It would seem more sensible to have a default of Zero, but then required dots tend to go missing. I've prepared a (hopefully comprehensive) set of test cases with four and five-note chords that demonstrate the issue, and each rendered with 'chord-dots-limit' values from 0 to 3. Please find attached. Regards, Chris P.S. There is a related problem where dotted chords in two voices get all the dots all placed after the note. A chord such as { << 4.. \\ b d c e>2. >> } is especially bad. But I think if the dot positioning is fixed, this is a question of horizontal spacing which is covered by another bug. Added as https://sourceforge.net/p/testlilyissues/issues/4971/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange Windows crash
"ChrisYate" <chrisy...@gmail.com> wrote in message news:1473934539099-194566.p...@n5.nabble.com... I'm not top posting. I'm having a strange problem with the latest LilyPond in Frescobaldi crashing with a nonsense return code (-1073741819). Unfortunately it only happens on a rather large file and I haven't been able to produce a tiny example. Is there any way I can get more data on this? Hi Mark, "Me too!". This is really a annoying bug because it apparently pops up for me only when a source file becomes a certain size. It's inconvenient for me not to work in Windows, partly because I like to use the IDE 'Frescobaldi'. I assume given the lack of further discussion here you weren't able to find a tiny example? I raised what I think is this same issue some time back, and had difficulty getting a dev to reproduce the problem -- apparently many of them run *nix systems rather than Windows. Chris It's _possible_ you're running out of memory. Can you watch what's happening with memory in Task Manager? I use Windows mainly, but note that the use of Frescobaldi is not a reason for only using Windows. It runs on Mac and Linux as well. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Behavior on Errors; Separate Run Output
"Christopher Heckman" <christopher.heck...@asu.edu> wrote in message news:caa_flenhqe+i9tvhwhsvcdjyfhvuadgqf_3gwej0k2wj69y...@mail.gmail.com... These would probably count as "annoying" bugs. (1) When I compile a Lilypond file that contains an error, Lilypond should not open up the previous .pdf file: An error means I have to go back to the file, which means closing the .pdf file first. (This could be added in the form of a preferences menu with items like "behavior upon error" and "behavior upon warning". Default would be "compile and open output file".) (2) When I compile a Lilypond file, make some changes, compile it again, and so on, the various compilations in the log file are continuous. Some sort of a separator (even if it's just hyphens) should be put between compilings. --- Christopher Heckman As far as I'm aware, LilyPond itself does neither of these things. Are you using a program such as Frescobaldi, and confusing what it does with what LilyPond does? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing warning about clashing note columns in 2.19
Weitergeleitete Nachricht Betreff: Missing warning about clashing note columns in 2.19 Datum: Sat, 16 Jul 2016 18:27:09 +0200 Von: Malte Meyn <lilyp...@maltemeyn.de> An: lilypond-user <lilypond-u...@gnu.org> Is this a bug/regression? 2.18.2 warns about clashing note columns, 2.19.44 does not. \version "2.19.44" << c''4 \\ \stemUp a'2 >> This changed between 19.12 and 19.14. It seems to me a retrograde step, since in a complex score it's possible to miss clashing columns. Does anyone know whether current devel ever outputs this warning? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: DOC: Essay, 1.4 Building software
"Pierre Perol-Schneider" <pierre.schneider.pa...@gmail.com> wrote in message news:caphotuwtxrmr97w5m2ajkt4sudvqdbd93tqudk0vfuogxh0...@mail.gmail.com... I clearly understand what you mean. Thing is that <> does not show what's on the picture (actually the link says: \relative c' { \new Voice { <> } } ) So I think it is not clear. Maybe this line should simply be deleted and the next example should be: \relative { f' <> } (or simply { << g'2 \\ { f'4 <<c'4 d'4 e'4>> } >> } face to what the 'Music representation' starts with). Cheers, Pierre 2016-07-22 15:40 GMT+02:00 James <p...@gnu.org>: Pierre, On 22/07/16 14:18, Pierre Perol-Schneider wrote: Hi James, Sorry for the misunderstanding. Have you tried the snippet ? Have you seen the result ? No but the online help is built using LilyPond (these are not static images). So the result should be the same as what is shown in that link. It should be written : { <c' d' e'>4 } and not: <> Examples that follow should also be corrected. Are you sure? http://lilypond.org/doc/v2.19/Documentation/notation/single-voice#simultaneous-expressions James I think very early versions of LilyPond used << notes >> for chords, not < notes >. The earliest manual I can find online (1.6) has the latter notation, but it may be that the essay uses the early notation? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly writes UTF16 BE in header texts
"Tobias Kretschmar" <tobias.kretsch...@gmx.de> wrote in message news:loom.20160714t222848-...@post.gmane.org... musicxml2ly 2.19.45 writes any header text (and some more) as UTF16 BE in the ly file. This will lead to errors when running lilypond with this file. error: EOF found inside string error: syntax error, unexpected end of input, ... Regards, Tobias Thanks. This is known about - see https://sourceforge.net/p/testlilyissues/issues/4751/?page=1 If you are able to do so, upgrading Python to 2.7 should fix the issue for you. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrongly combined note heads
"Simon Albrecht" <simon.albre...@mail.de> wrote in message news:576b8928.6040...@mail.de... On 23.06.2016 03:16, Andrew Bernard wrote: I think the behaviour you show is normal lilypond semantics - although it is not usually what one wants with different accidentals on the same pitch. I believe this is not a bug as it is up to the individual engraver to resolve this according to their own taste and style, e.g. which note comes first if shifted? I strongly disagree. With the current behaviour, it’s impossible to discern that there are two different pitches to be played. Of course, it’s not a trivial question how it should be written, but what Lily does now is definitely wrong. I thought we already had a tracker issue for this, but I can’t find it right now… Best, Simon == This may have been my first bug report: https://sourceforge.net/p/testlilyissues/issues/1134/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Can't download Lilypond(!)
"Mike" <terremotoetrage...@gmail.com> wrote in message news:loom.20160604t155324-...@post.gmane.org... See http://www.downforeveryoneorjustme.com/http://download.linuxaudio.org Thanks, good to know it's not just me... but then who do I report this to please? I'd like to download Lilypond. Cheers, Mike It's not a site we maintain: we're just non-paying customers. I'm sure they're aware. In the meantime I'll send you a private email that should help. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange Windows crash
"Mark Green" <drmoos...@gmail.com> wrote in message news:loom.20160531t005701-...@post.gmane.org... I'm not top posting. I'm having a strange problem with the latest LilyPond in Frescobaldi crashing with a nonsense return code (-1073741819). Unfortunately it only happens on a rather large file and I haven't been able to produce a tiny example. Is there any way I can get more data on this? It's not a nonsense code - it's hex for C005, which is an access violation. It's possible that Lily is asking for more memory than your system can provide: I would get Task Manager running while processing the file and see how much memory is being used. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: addlyrics does not work with an ossia staff
"David Kastrup" <d...@gnu.org> wrote in message news:87iny2shdo@fencepost.gnu.org... Simon Albrecht <simon.albre...@mail.de> writes: Hello Ansgar, this is a bug which was fixed in the 2.19 development series, I think quite early. Anyway, it’s often recommendable to upgrade to current development versions – a great many advantages have been added since the last stable release. Maybe we should bite the bullet and just go for 2.20 now. It's been long enough, and I fear that Guile 2.0 compatibility is not in a state where we could hope to get 2.20 out with it within a narrow time frame. Not least of all because Guile 2.0.12 (containing LilyPond-relevant fixes) has not yet been released. -- David Kastrup I think the current issue Knut and James have with compiling the docs would prevent 2.20, but I don't see any other reason for not proposing a new stable. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: patch labels in CG manual
"James" <p...@gnu.org> wrote in message news:57433776.4010...@gnu.org... Carl, On 23/05/16 16:43, Carl Sorensen wrote: James, On 5/20/16 10:15 AM, "James" <p...@gnu.org> wrote: One thing to realise and I think people have forgotten is that the Patchy-testing scripts (rather than Patchy-merge scripts) no longer work as they were written to scrape the old Google tracker and don't work with Allura. So Patch testing is 100% manually done - i.e. lots of clicking and typing commands - and that includes me having to download the raw *diff file from Rietveld via my browser and then running the commands, albeit serially, in a CMD window completely unscripted. Then making sure I manually clean my out of tree build and the tree in its current state after a patch test. I certainly had forgotten this. I'm amazed that you've continued this long with manual patch application. You're an all-star! I will commit to helping get the Patchy-testing scripts working, so this manual procedure is no longer needed, or is at least simplified. I've found the Patchy scripts at github as shown in the CG. Are changes made by sending a pull request to Graham? Or do we have push permission on the Patchy repo? I really don't know. Phil will if no one else does. James I can accept a pull request to Graham's repo at github, so a pull request and a mail I'll see will do the job. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-2.19.41-1.documentation.tar.bz2 file missing
"Federico Bruni" <f...@inventati.org> wrote in message news:1463392715.777...@smtp.autistici.org... Il giorno lun 16 mag 2016 alle 10:57, Thomas Morley <thomasmorle...@gmail.com> ha scritto: Got my git-repository finally updated. The mentioned patch is in master, but the link on the website is indeed broken. Federico may I ask you to have a look? It's broken because Phil didn't make the 2.19.42 release yet. As soon as he uploads it, it should be ok. Related but different issue: http://lilypond.org/download (without trailing slash) should serve already (before the 2.19.42 release) the HTML page in the preferred language. There might be an issue with the browser cache though, which may add the trailing slash automatically. If you use Firefox, go to the History>Show all history, search lilypond.org, right-click on it and click on "Forget this site". I tried to make the release but it failed. I've tried to post to .devel with details of the failure, but nothing appeared there. If this makes it through, could someone forward it to .devel, please? I'm trying to build a Gub release, but failing very quickly. In the logs, I get: invoking cd /home/gub/NewGub/gub/downloads/lilypond/git && git fetch git://git.sv.gnu.org/lilypond.git release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable fatal: The remote end hung up unexpectedly Command barfed: cd /home/gub/NewGub/gub/downloads/lilypond/git && git fetch git://git.sv.gnu.org/lilypond.git release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable (extra line breaks added for Gmane posting) If I try the command manually, not surprisingly the cd works, but I again get a failure from git: git fetch git://git.sv.gnu.org/lilypond.git release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable fatal: Invalid refspec 'release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable' I'm wondering whether it's to do with the changes at Savannah, but does anyone have a better idea or a fix? Ta. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: incorrect skyline (beam, \changeStaff)
"Malte Meyn" <lilyp...@maltemeyn.de> wrote in message news:57249a62.50...@maltemeyn.de... Hi list, the following code produces an incorrect skyline for the "rh" staff. It includes the noteheads but not the stems and beam. This happens only with certain rhythms (for example, 8. 16 in the "lh" staff produces a correct skyline in the "rh" staff). \version "2.19.40" % also 2.18.2, 2.16.2, 2.14.2 #(ly:set-option 'debug-skylines #t) << \new Staff = "rh" s2. \new Staff = "lh" { d'8 f'' \change Staff = "rh" d'8. f''16 \change Staff = "lh" d'4 } >> Added as https://sourceforge.net/p/testlilyissues/issues/4839/ -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \omit dynamic occupies space
"Carl Sorensen" <c_soren...@byu.edu> wrote in message news:d3461c8e.75660%c_soren...@byu.edu... On 4/27/16 7:09 AM, "Graham King" <graham.k...@tremagi.org.uk> wrote: meanwhile, Harm has kindly shown me a work-round. It is in the first two bars of this example, which also serves to illustrate the partial effect of \omit. I haven't looked at the code, but it appears to me that without the dynamics, the hairpin is bound from the left edge of the first note column to the right edge of the last note column. With the omitted dynamics, the hairpin appears to be bound to the right edge of the first note column and the left edge of the last note column. Hazarding a guess that the dynamic text is bound to the note column, and thus the hairpin moves out of the columns into the inter-column space. And if the dynamic text overflows the column, the hairpin is shortened. When the text is omitted, the hairpin can only move to the edge of the column. Carl Tracker added as https://sourceforge.net/p/testlilyissues/issues/4837/ -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: long dynamic strings displace low notes
"Phil Holmes" <m...@philholmes.net> wrote in message news:nfnceh$ob7$1...@ger.gmane.org... "David Kastrup" <d...@gnu.org> wrote in message news:87mvog3f7z@fencepost.gnu.org... Thomas Morley <thomasmorle...@gmail.com> writes: 2016-04-26 10:53 GMT+02:00 Phil Holmes <m...@philholmes.net>: Why do you say that expected behaviour is to force the dynamic down? Moving the note is potentially equally valid behavior, depending on the typesetter's preference. It's clearly a bug. See this small (not tiny) example plus comments from my earlier post at http://lilypond.1069038.n5.nabble.com/Dynamics-placement-td188833.html#a188851 %% Following note is moved away by DynamicText %% %% Bad behaviour goes away if the second note has no Accidental %% or \voiceTwo is used %% or if \new StaffGroup is deleted or replaced by \new ChoirStaff %% \new GrandStaff does not work as well, though %% %% Worked fine with "2.18.2" \version "2.19.38" Is the cause known or should I try to bisect it to a particular commit? -- David Kastrup The behaviour changed between 18.2 and 19.2 -- Phil Holmes Added as https://sourceforge.net/p/testlilyissues/issues/4838/ -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: long dynamic strings displace low notes
"David Kastrup" <d...@gnu.org> wrote in message news:87mvog3f7z@fencepost.gnu.org... Thomas Morley <thomasmorle...@gmail.com> writes: 2016-04-26 10:53 GMT+02:00 Phil Holmes <m...@philholmes.net>: Why do you say that expected behaviour is to force the dynamic down? Moving the note is potentially equally valid behavior, depending on the typesetter's preference. It's clearly a bug. See this small (not tiny) example plus comments from my earlier post at http://lilypond.1069038.n5.nabble.com/Dynamics-placement-td188833.html#a188851 %% Following note is moved away by DynamicText %% %% Bad behaviour goes away if the second note has no Accidental %% or \voiceTwo is used %% or if \new StaffGroup is deleted or replaced by \new ChoirStaff %% \new GrandStaff does not work as well, though %% %% Worked fine with "2.18.2" \version "2.19.38" Is the cause known or should I try to bisect it to a particular commit? -- David Kastrup The behaviour changed between 18.2 and 19.2 -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: long dynamic strings displace low notes
Why do you say that expected behaviour is to force the dynamic down? Moving the note is potentially equally valid behavior, depending on the typesetter's preference. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond.org/download: website page and directory
"Federico Bruni" <f...@inventati.org> wrote in message news:1461329597.724...@smtp.autistici.org... Il giorno ven 22 apr 2016 alle 13:46, Phil Holmes <m...@philholmes.net> ha scritto: "Federico Bruni" <f...@inventati.org> wrote in message news:1461320015.724...@smtp.autistici.org... Hi folks At the moment, the URL lilypond.org/download lists the contents of a directory: http://lilypond.org/download I think having a directory list is convenient if you want to grab an earlier version? But it would be also a nice URL for language negotiation for the website, as for example: http://lilypond.org/manuals I think that lilypond.org/download should serve the website page which is currently available only for specific languages (that is, with the .html extension): http://lilypond.org/download.html http://lilypond.org/download.fr.html etc. This implies that we should rename the download/ directory and change all the references to it in Documentation (and scripts?). What do you think about it? I assume this would require changes to GUB? I always get a bit nervous about that. I understand, but this simple change should not cause any problem. I can send a pull request to gpercival/gub with a patch which renames all occurrences of lilypond.org/download with lilypond.org/tarballs (or lilypond.org/downloads, or whatever you think is best). I think lilypond.org/downloads Then someone should rename the directory on the server before running gub. Let me know when you want this doing. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond.org/download: website page and directory
"Federico Bruni" <f...@inventati.org> wrote in message news:1461320015.724...@smtp.autistici.org... Hi folks At the moment, the URL lilypond.org/download lists the contents of a directory: http://lilypond.org/download I think having a directory list is convenient if you want to grab an earlier version? But it would be also a nice URL for language negotiation for the website, as for example: http://lilypond.org/manuals I think that lilypond.org/download should serve the website page which is currently available only for specific languages (that is, with the .html extension): http://lilypond.org/download.html http://lilypond.org/download.fr.html etc. This implies that we should rename the download/ directory and change all the references to it in Documentation (and scripts?). What do you think about it? I assume this would require changes to GUB? I always get a bit nervous about that. By the way, these are duplicates? http://lilypond.org/download/ http://download.linuxaudio.org/lilypond/ The linuxaudio site is rsynched to the lilypond site with a cron job. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: dodecaphonic-no-repeat and mid bar breaks
"Simon Albrecht" <simon.albre...@mail.de> wrote in message news:5716a647.7070...@mail.de... On 19.04.2016 15:02, Phil Holmes wrote: "Gilberto Agostinho" <gilbertohasn...@googlemail.com> wrote in message news:57161fa5.7000...@gmail.com... Hello bug squad, When using the accidental style dodecaphonic-no-repeat, the accidental of repeated notes aren't restated unless there is a bar line in between them. The problem I found is that when using a mid bar break (by using the command \bar "" \break in the middle of a bar), the accidental is not restated between repeated notes that happen to be around the break. See: \version "2.19.37" \relative c' { \accidentalStyle dodecaphonic-no-repeat cis d e cis | \break cis d e cis | } \relative c' { \accidentalStyle dodecaphonic-no-repeat \time 8/4 cis d e cis \bar "" \break cis d e cis | } Producing: http://s17.postimg.org/f6s6k96zz/accidental.jpg Best, Gilberto That seems perfectly correct. There is no bar line in your second example, so why should the accidental be restated? Perhaps because it demands really much from the performer to remember accidentals across line breaks, in such complicated music as will likely use the dodecaphonic-no-repeat accidental style. Making this rather an enhancement request. Best, Simon I would have said that if the typesetter has gone to the lengths of adding a manual blank barline and a break, forcing an accidental with ! would not be a problem. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: dodecaphonic-no-repeat and mid bar breaks
"Gilberto Agostinho" <gilbertohasn...@googlemail.com> wrote in message news:57161fa5.7000...@gmail.com... Hello bug squad, When using the accidental style dodecaphonic-no-repeat, the accidental of repeated notes aren't restated unless there is a bar line in between them. The problem I found is that when using a mid bar break (by using the command \bar "" \break in the middle of a bar), the accidental is not restated between repeated notes that happen to be around the break. See: \version "2.19.37" \relative c' { \accidentalStyle dodecaphonic-no-repeat cis d e cis | \break cis d e cis | } \relative c' { \accidentalStyle dodecaphonic-no-repeat \time 8/4 cis d e cis \bar "" \break cis d e cis | } Producing: http://s17.postimg.org/f6s6k96zz/accidental.jpg Best, Gilberto That seems perfectly correct. There is no bar line in your second example, so why should the accidental be restated? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: removing old stuff
"Jan Nieuwenhuizen" <jann...@gnu.org> wrote in message news:87d1qb6hpe.fsf@drakenvlieg.flower... Federico Bruni writes: Don't know if one of these should be kept (not updated since 2009): http://lilypond.org/blog/janneke/ http://lilypond.org/blog/jan/ Wow, that's old. And all links are dead. OK to remove. Greetings, Jan Symlinks deleted. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: removing old stuff
"Federico Bruni" <f...@inventati.org> wrote in message news:1459345122.3275...@smtp.autistici.org... Hi all If you search "lilypond blog site:lilypond.org", you'll find these old pages. I think that this should be removed from the server: http://lilypond.org/blog/ +1 Don't know if one of these should be kept (not updated since 2009): http://lilypond.org/blog/janneke/ http://lilypond.org/blog/jan/ Jan? I _might_ not have the permissions to do anything with these, but if I do, then I think it would be best to move them out of the web directory. Looking at the file info, it looks like they are created via symlinks, so just deleting the symlinks should do this, I think. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LSR snippets wanting an upstream update
"David Kastrup" <d...@gnu.org> wrote in message news:87shzio87z@fencepost.gnu.org... Hi, I thought that the LSR was at 2.18 now, so the following seem to warrant an update in the LSR: dak@lola:/usr/local/tmp/lilypond$ git grep '\\version "2.1[0-8]' Documentation/snippets/new Documentation/snippets/new/arranging-separate-lyrics-on-a-single-line.ly:\version "2.18.0" Documentation/snippets/new/changing-stanza-fonts.ly:\version "2.18.0" Documentation/snippets/new/changing-the-default-text-font-family.ly:\version "2.18.0" Documentation/snippets/new/modifying-the-ottava-spanner-slope.ly:\version "2.18.0" Documentation/snippets/new/staff-headword.ly:\version "2.17.6" Well, some are due to me apparently. for i in $(git grep -l '\\version "2.1[0-8]' Documentation/snippets/new);do git log -1 --stat $i;done commit 7291ef21ff869752b58d839bc4514a5d2c41db51 Author: David Kastrup <d...@gnu.org> Date: Mon Mar 14 21:45:25 2016 +0100 arranging-separate-lyrics-on-a-single-line snippet: 2.18 override syntax .../arranging-separate-lyrics-on-a-single-line.ly | 65 ++ 1 file changed, 65 insertions(+) commit 3bd039bb1bb0ed2820458f957debbaa75511ca4e Author: Phil Holmes <m...@philholmes.net> Date: Tue Dec 29 12:08:13 2015 + Further LSR tidying Documentation/snippets/new/changing-stanza-fonts.ly | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 3bd039bb1bb0ed2820458f957debbaa75511ca4e Author: Phil Holmes <m...@philholmes.net> Date: Tue Dec 29 12:08:13 2015 + Further LSR tidying Documentation/snippets/new/changing-the-default-text-font-family.ly | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit a1c9c3d285a2f3e59cf79a375b67cfb58ceca7ba Author: James Lowe <pkx1...@gmail.com> Date: Thu Jun 26 22:37:04 2014 +0100 Doc: NR Pitches.itely - Clef - updated snippets and text Issue 3976 Added 2 new snippets: 1 snippet added to NR 1 snippet added just to Snippets Modified 1 existing snippet: This was already (and still is) included in the NR Deleted 2 snippets (and incorporated them in the main text in @lilyponds) Added new @lilypond example that was originally described (but not show)n in the 'Tweaking Clef Properties' snippet to show how to remove the clef glyph from the end of a line. As this 'tweak' is relatively simple (a single \set and \unset) and more than likely to be used (IMHO) by the general user than the listed items in the snippet, I thought it better to be in the NR than another example in either an already long snippet or by creating yet another snippet. Some minor linelength formatting as per CG. .../new/modifying-the-ottava-spanner-slope.ly | 31 ++ 1 file changed, 31 insertions(+) commit b570097f37f1aa89e81da7b48e3a9827d9f7184c Author: David Kastrup <d...@gnu.org> Date: Thu Nov 7 20:16:57 2013 +0100 Issue 3648/7: Give several examples of durations without explicit pitches Documentation/snippets/new/staff-headword.ly | 24 +++- 1 file changed, 7 insertions(+), 17 deletions(-) Could you put an issue in the tracker and assign it to me and I'll fix these when I have a spare hour or so? (Possibly tomorrow) Thanks. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: default configurations in latest git-cl
"Federico Bruni" <f...@inventati.org> wrote in message news:1458210193.1533...@smtp.autistici.org... As you can see below, there are two default configuration options that are missing ([] is empty): 1. Allura server 2. CC list Adding the Allura server would be convenient. I'm not sure what the CC list is for, as the email to the dev list is sent when the rietveld issue is published on the web interface. $ git-cl config Rietveld server (host[:port]) [codereview.appspot.com]: Allura server []: https://sourceforge.net/p/testlilyissues/issues/ Allura bearer token (see https://sourceforge.net/auth/oauth/) []: xx CC list: I've added this to https://sourceforge.net/p/testlilyissues/issues/4755/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: www.lilypond.org webserver not responding
It often comes back of its own accord (or, more accurately, the providers fix it). If it's down tomorrow I'll have a look see what can be done. -- Phil Holmes - Original Message - From: "James" <p...@gnu.org> To: "bug-lilypond" <bug-lilypond@gnu.org>; "lilypond-devel" <lilypond-de...@gnu.org> Cc: "Graham King" <graham.k...@tremagi.org.uk> Sent: Thursday, March 10, 2016 5:55 PM Subject: Re: www.lilypond.org webserver not responding This still seems to be a problem as of 17:55 GMT James On 10/03/16 10:56, Graham King wrote: www.lilypond.org is not responding this morning. I can ping it at 82.94.241.173 so, unless there's a problem with DNS, it looks like the webserver has a problem. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond ___ lilypond-devel mailing list lilypond-de...@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Two distinct pitches of same letter need explicit accidentals
"Jon Arnold" <jonarnoldsem...@gmail.com> wrote in message news:loom.20160307t202842-...@post.gmane.org... I'm not top posting. Hi- Pretty sure this is a bug or could be handled better. Hopefully it hasn't been reported already Snippet: %b-flat disappears {\key f \major << {c'' b'} \\ {a' bes'} >> } This produces (ignoring stem direction): b (as in b natural) Image: http://imgur.com/1FwQyzm In fact, has a similar effect. The b-flat is effectively missing. Hope this is helpful. Please CC me in replies. This looks very much like https://sourceforge.net/p/testlilyissues/issues/1134/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: when adding \new Staff to a StaffGroup, ledger lines not rendered if clef is specified.
"Andy Deitrich" <adeitr...@gmail.com> wrote in message news:loom.20160129t162423-...@post.gmane.org... % The example here renders perfectly if \clef bass is removed % but as is, the ledger lines in the new staff are not rendered. \version "2.18.2" \new StaffGroup \relative c { \time 6/8 \new Staff c''2. | c2. << {2.~ | } \new Staff \clef bass {ges,,2. | f} >> } I've no idea what you're trying to do here, but if you sort out your << >> and { } groups, the music starts to look like I'd guess it should: \version "2.18.2" \new StaffGroup \relative c { \time 6/8 << \new Staff { c''2. | c2. 2.~ | } \new Staff { \clef bass ges,,2. | f } } -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: git-cl traceback (timeout?)
"Urs Liska" <u...@openlilylib.org> wrote in message news:569e2322.7030...@openlilylib.org... Am 19.01.2016 um 12:29 schrieb Trevor Daniels: Hi Urs What did you enter in response to the query? I pressed ENTER (to create a new issue item) Urs Trevor - Original Message - From: "Urs Liska" <u...@openlilylib.org> To: <bug-lilypond@gnu.org>; "Phil Holmes" <m...@philholmes.net> Sent: Tuesday, January 19, 2016 9:49 AM Subject: git-cl traceback (timeout?) When uploading a patch git-cl failed with the transcript below: I'm not sure if that's caused by git cl (I had just pulled the newest version) or if it's a simple time-out on my side, but: a) If it's a git-cl issue it should be fixed b) If it's a time-out such an error should be handled by git-cl c) This left me unclear of whether the issue had been created on Allura (I can see that it did through the website but see b) ) Best Urs uliska@uliska-lmde-laptop:~/git/lilypond/source$ git cl upload master scm/lily.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Upload server: codereview.appspot.com (change with -s/--server) Your browser has been opened to visit: https://codereview.appspot.com/get-access-token?port=8001 If your browser is on a different machine then exit and re-run upload.py with the command-line parameter --no_oauth2_webbrowser Issue created. URL: http://codereview.appspot.com/286820043 Uploading base file for scm/lily.scm We were not able to associate this patch with a tracker issue. Please enter a valid tracker issue number (or enter nothing to create a new issue): Traceback (most recent call last): File "/home/uliska/git/lilypond/git-cl/git-cl", line 628, in sys.exit(main(sys.argv)) File "/home/uliska/git/lilypond/git-cl/git-cl", line 622, in main return func(argv[2:]) File "/home/uliska/git/lilypond/git-cl/git-cl", line 341, in CmdUpload issueId = projecthosting_upload.upload(issue, patchset, subject, desc, issueId) File "/home/uliska/git/lilypond/git-cl/projecthosting_upload.py", line 182, in upload status = patchy.upload(issue, patchset, subject, description, issue_id) File "/home/uliska/git/lilypond/git-cl/projecthosting_upload.py", line 175, in upload issue_id = allura_issues.create_issue(subject, description) File "/home/uliska/git/lilypond/git-cl/allura_issues.py", line 25, in create_issue allura_result = urllib.urlopen (allura_api + "/new", data_encoded) File "/usr/lib/python2.7/urllib.py", line 89, in urlopen return opener.open(url, data) File "/usr/lib/python2.7/urllib.py", line 215, in open return getattr(self, name)(url, data) File "/usr/lib/python2.7/urllib.py", line 460, in open_https data) File "/usr/lib/python2.7/urllib.py", line 379, in http_error result = method(url, fp, errcode, errmsg, headers, data) File "/usr/lib/python2.7/urllib.py", line 641, in http_error_302 data) File "/usr/lib/python2.7/urllib.py", line 667, in redirect_internal return self.open(newurl) File "/usr/lib/python2.7/urllib.py", line 213, in open return getattr(self, name)(url) File "/usr/lib/python2.7/urllib.py", line 443, in open_https h.endheaders(data) File "/usr/lib/python2.7/httplib.py", line 997, in endheaders self._send_output(message_body) File "/usr/lib/python2.7/httplib.py", line 850, in _send_output self.send(msg) File "/usr/lib/python2.7/httplib.py", line 812, in send self.connect() File "/usr/lib/python2.7/httplib.py", line 1204, in connect HTTPConnection.connect(self) File "/usr/lib/python2.7/httplib.py", line 793, in connect self.timeout, self.source_address) File "/usr/lib/python2.7/socket.py", line 571, in create_connection raise err IOError: [Errno socket error] [Errno 110] Connection timed out https://sourceforge.net/p/testlilyissues/issues/4755/ -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: CG 8.2.2 - Regular maintenance, verifying issues
"Federico Bruni" <f...@inventati.org> wrote in message news:1447173066.1886...@smtp.autistici.org... Hi I think that this page should be updated (there are links to google code tracker): http://lilypond.org/doc/v2.19/Documentation/contributor/bug-squad-checklists I'll have a look today. The most important part is the way an issue is verified. Let's take this issue: https://sourceforge.net/p/testlilyissues/issues/4639/ The committish is: 0f3099177a2a23347b0a8c0895adbebc87d416be The doc recommends two ways to verify it: http://git.savannah.gnu.org/gitweb/?p=lilypond.git http://philholmes.net/lilypond/git but, for some reason, both fail in searching that committish. Same for gitk on my local copy. The search on Savannah works now. Perhaps it was behind in its indexing of commitishes??? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Tweak on Clef’s X-extent influences on Beam’s vertical position
"Simon Albrecht" <simon.albre...@mail.de> wrote in message news:56536880.1060...@mail.de... \version "2.19.31" { a'8 \once\override Staff.Clef.X-extent = #'(0 . .8) \clef bass a, b, c \clef treble a'8 \once\override Staff.Clef.X-extent = #'(0 . 0) \clef bass a, b, c } %% Yours, Simon I presume that this is because you've set it's width to zero and there is therefore nothing for the beam to avoid. Set its extent to a small positive value (e.g. 0.001) and the beam is back where it was. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Big in repeat bar
"George Podkolzin" <egorp1...@gmail.com> wrote in message news:loom.20151114t081543-...@post.gmane.org... \version "2.18.2" \relative c' { c e c e \repeat volta 2 { \bar "[|:" c e g c } \alternative { % If I use \bar ":|]" instead of default repeat bar, there is no space between volta brackets. { c e, g2 \bar ":|]" } { c4 g c,2 } } \bar "|." } This has been fixed in the 2.19 development version. You might consider moving to the latest version - it is likely to be completely stable. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: French beams over rests cause segfault
"Jean Menezes da Rocha" <j...@menezesdarocha.info> wrote in message news:CALRb6h+_gWgeU1=6wruogawua7hsddya8zx0vsy97is7tci...@mail.gmail.com... I have seen, according to this <https://codereview.appspot.com/274280043/> [1], that Kastrup created a patch to address this issue. Is there any way I can apply this patch by now, or should I wait for a new development release containing a definitive solution? If this is not the right place/time to ask this question, feel free to dismiss my request (but pointing me to the right place to ask will be appreciated). In order to apply the patch to your own system, you will need to be able to compile LilyPond yourself: see http://lilypond.org/doc/v2.19/Documentation/contributor/overview-of-compiling This is likely to be fairly onerous. You may find it better to wait for a pre-compiled version - all other things being equal this should be available next Monday (the 9th). -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slur_proto_engraver segfault
- Original Message - From: "David Kastrup" <d...@gnu.org> Phil, this is absolutely serious stuff, likely causing crashes for large scores on most platforms. Too bad we did not catch this (no idea why) in time. I wonder whether we have a chance to actually _retract_ 2.19.29, but short of that, we really need to create 2.19.30 as soon as possible rather than waiting for the full 2-week turnaround. I'll create and upload 19.30 tomorrow. Sorry for messing this up. -- David Kastrup No worries. It's supposed to be an unstable release anyway... -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unable to italicize lyrics in 2.18, 2.19
"Paul Schmitz" <seasca...@yahoo.com> wrote in message news:loom.20151021t040718-...@post.gmane.org... I'm not top posting. Hi, For many years I have used the documented instructions to italicize lyrics, e.g. \score { << \new Lyrics \with { \override LyricText.font-shape = #'italic \override LyricText.self-alignment-X = #LEFT } { \dialogue } \new Staff { \new Voice { \music } } (example from 2.18 notation reference) However, font-shape is no longer listed as an interface for LyricText and this instruction appears to be ignored. If it's been removed intentionally, is there a replacement or workaround? Thanks, Paul This code: music = \relative { { a'4 a a a } } dialogue = \lyricmode {la la la la } } \score { << \new Lyrics \with { \override LyricText.font-shape = #'italic \override LyricText.self-alignment-X = #LEFT } { \dialogue } \new Staff { \new Voice { \music } } } Gives the attached italicised lyrics. Also, since the examples in the NR are italicised, it means the command must work. Perhaps your installed fonts have changed? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: mistake in german user manual "Benutzerhandbuch"
-- Phil Holmes "Trommel" <baroquece...@gmail.com> wrote in message news:loom.20151021t123127-...@post.gmane.org... In the german user manual (I assume in other languages too), the following seems incorrect to me: chapter 1.4.1 Lange wiederholungen "Eine einfache Wiederholung mit einer Alternative: \repeat volta 2 { c4 d e f | } \alternative { { c2 e | } { f2 g | } } c1 [image of music]" In the image it shows the c1 as the last note. However, if this code is copied into Lilypond, an error is reported, and no c1 is engraved at all. I had to change the code to: " Eine einfache Wiederholung mit einer Alternative: \repeat volta 2 { c4 d e f | } \alternative { { c2 e | } { f2 g | c1} } [image of music]" in order to get the result shown in the picture. As a beginner, it took quite some time to figure that out... Please have a look at section 1.4.1 (interesting - the same section) in the Learning Manual. As you will see, this say that all examples are likely to need surrounding with {} or \relative{}. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [LSR] Ready-to-use LilyPond macros: advanced layout and titles, using a special stylesheet
"David Kastrup" <d...@gnu.org> wrote in message news:87twpt4rx3@fencepost.gnu.org... The LSR version of vspace (when was this ever a good idea?) by now has markedly diverged from the built-in variant, so it really should get removed and its effect compensated. So it might make sense to run convert-ly -f 2.17.18 -t 2.17.19 on the LSR snippet (though it's possible that this has already been done once and should not be repeated) before throwing out its own vspace definition. Or simply delete the snippet? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LM Orchestral template
"James Lowe" <p...@gnu.org> wrote in message news:5601bfb2.6010...@gnu.org... On 22/09/15 20:51, Simon Albrecht wrote: On 22.09.2015 21:42, Trevor Daniels wrote: Simon Albrecht wrote Tuesday, September 22, 2015 7:35 PM I just came across the Orchestral template in LM A.6.I, and noticed two flaws, one minor and one serious: – Double basses usually aren’t notated in a \clef "bass_8", but as transposing instruments (originating from the time when they were sharing a staff with the violoncelli). All the scores I have here, from Beethoven through Mendelssohn, Bruckner and Mahler to Hindemith, confirm this. I attach a version of the template where this is changed. Thanks – The image rendition in the docs is extremely compressed, with overlapping stuff, staves touching one another This is a really bad example and needs to be changed; how is this done? I don’t know the framework in lilypond-book-preamble.ly; certainly there will be someone who can quickly say how to allow the score more space. I think for this example all that is needed is to reduce the global staff size, which is set (unusually) in this file to 17. I’m afraid it won’t be as easy. I also thought that way, but I tried it (loading the complete source file for the image with \include "lilypond-book-preamble.ly" etc.) and it doesn’t make a difference: everything gets smaller, but is compressed and cut the same. Yes I verified this too. Well I tried to fiddle about the 'Flexible Vertical Spacing' (NR 4.4.1) http://lilypond.org/doc/v2.19/Documentation/notation-big-page#flexible-vertical-spacing-within-systems I think a combination of these will help, the problem I have is that I cannot work out which. :( I've never got my head around these settings. James If you use the template locally, the spacings are fine. So it's something to do with the way snippets are compiled: perhaps a default paper-size setting? The version on the LSR is also badly spaced, so it may be possible to experiment with that to correct the version in the docs. http://lsr.di.unimi.it/LSR/Item?id=719 -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Allura at SF is ready
- Original Message - From: "josiah oberholtzer" <josiah.oberholt...@gmail.com> To: "Federico Bruni" <f...@inventati.org>; "Trevor Daniels" <t.dani...@treda.co.uk> Cc: "Lilypond bug list" <bug-lilypond@gnu.org>; "lilypond-devel" <lilypond-de...@gnu.org> Sent: Wednesday, September 02, 2015 5:19 AM Subject: Re: Allura at SF is ready Hi all, Sorry for being out of touch - other obligations caught up with me. I'm not sure how to proceed on the bugs.lilypond.org side. The Allura server there is operational (visit the site to see), but - as Federico points out - we don't have working HTTPS connections. It looks like the GNU certificate only covers *.gnu.org domains, which bugs.lilypond.org isn't. I believe someone suggested renaming the site something like "bugs-lilypond.gnu.org" or "lilypond-bugs.gnu.org", which would allow wildcard coverage from the certificate. I don't believe the change can be made on our end (but I couldn't say for sure). More advanced Apache-wrangling than what I've managed to get the Allura application online is outside my knowledge. I see no reason why "lilypond-bugs.gnu.org" should not be perfectly acceptable. We've been using code.google.com for goodness-knows how long, so another tracker without a lilypond.org domain name should be no problem. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Fw: 2.19.26 regtests
Could someone create a bug on the new issue tracker to track this bug, please? -- Phil Holmes - Original Message - From: "Masamichi HOSODA" <truer...@sea.plala.or.jp> To: <d...@gnu.org> Cc: <lilypond-de...@gnu.org> Sent: Monday, August 31, 2015 3:17 PM Subject: Re: 2.19.26 regtests There's lots of differences, presumably down to font changes, Also sans \bold and \italic do not seem to work in font-family-override.ly Well, I call uh-oh. It will probably take a few more unstable releases to shake out the problems from the font setup changes. Probably, it caused by URW fonts problem and/or Pango version. In my experiment, with newest URW fonts release (commit date is 2015-08-28) and newest Pango (version 1.36.8, 2014-09), there is no problem. Attached file is the result. First, the previous URW fonts release (commit date is 2015-08-25) seems broken. It has "Nimbus Sans Regular", "Nimbus Sans L Bold", "Nimbus Sans L Regular Italic", "Nimbus Sans L Bold Italic". Only "Regular" font's family name is "Nimbus Sans" but others are "Nimbus Sans L". http://bugs.ghostscript.com/show_bug.cgi?id=696089 http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commitdiff;h=ee2beed6 The newest URW fonts release has no "Nimbus Sans" but "Nimbus Sans L". http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=c983ed400dc278dcf20bdff68252fad6d9db7af9 Next, we use old Pango (version 1.28.3, 2010-09) in GUB. In four years, many bugs would have been fixed. So I'll make a GUB's patch that updates URW fonts and Pango. Would I create an Issue on tracker? How can I do so? Or, would someone create it? ___ lilypond-devel mailing list lilypond-de...@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bad LSR snippet.
David Kastrup d...@gnu.org wrote in message news:87io7x87q9@fencepost.gnu.org... commit 8ffecf6be17c6ec2ff87cf31873121a8cce29b09 Author: Phil Holmes m...@philholmes.net Date: Thu Jul 24 15:17:57 2014 +0100 Import snippets from LSR and delete initial batch in snippets/new breaks Documentation/snippets/automatically-changing-the-stem-direction-of-the-middle-note-based-on-the-melody.ly by replacing \override Stem.neutral-direction = #'() with \stemNeutral which is absolutely not the same and does not work. Do people not actually test their changes? So at any rate, this should be fixed in the LSR. It would appear to be snippet 751 URL:http://lsr.di.unimi.it/LSR/Item?id=751. -- David Kastrup Fixed in the LSR: will be fixed in master with an LSR import. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: autoBeaming and \set measurePosition
Simon Albrecht simon.albre...@mail.de wrote in message news:55d51b39.2010...@mail.de... I don’t quite know what I’m supposed to think of this: With 3/4, there is no beam between the third and fourth quavers. It doesn’t happen with -1/4, 0, 1/4, or 2/4. Doesn’t seem like this is going to appear in any realistic scenario. Just ignore it? Yours, Simon Simon, What are you trying to do with this example? Also, for trivially small examples (like this is) I think most people find it far easier to comment if you post the code in line, rather than as an attachment. I certainly do. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: BreathingSign and NoteHead collide
Simon Albrecht simon.albre...@mail.de wrote in message news:20150731131049.39c0687...@smtp04.mail.de... \paper { line-width = 10 } { f'' \breathe \bar | } The collision occurs with both 2.18.2 and 2.19.23. Thank you, Simon FWIW, there was no collision in 2.15.18 (the breath sign moves to the right). The collision does occur in 2.15.21. However, it does appear an artifact of an artificially small line width? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Dynamics attached to spacers sometimes aligned incorrectly
Simon Albrecht simon.albre...@mail.de wrote in message news:55a754e0.7050...@mail.de... Am 16.07.2015 um 06:39 schrieb Keith OHara: Simon Albrecht simon.albrecht at mail.de writes: Am 12.07.2015 um 13:20 schrieb Greg: I'm not top posting. This may be related to issue 3299 but I don't have the technical knowledge to confirm this. I think this is issue 1861 https://code.google.com/p/lilypond/issues/detail?id=1861, which has been claimed fixed already, but erroneously, it appears. I reopened it and added your example. Thanks for a very well-written bug report. I'm unable to reproduce on either Windows or Linux Interesting. I can, with Ubuntu 14.04 and Lily 2.18.2. What else might make a difference? Using your code, I see badly positioned dynamics on Windows 2.18, but good positioning on Windows with 2.19.21. Looks like the problem has been fixed. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Simultaneous spacer affects note positioning
Greg gre...@fastmail.co.uk wrote in message news:loom.20150712t13222...@post.gmane.org... I'm not top posting. \version 2.18.2 \score { \new Staff \relative g' { g1 s1^s1 g1 s1^s1 g1 s4^s4 % note appears closer to barline g1 s1^s1 } } TBH, I'm a bit confused about why you're using the constructs to combine notes and spacers: what are you trying to achieve with this? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: barNumberCheck broken in LilyPond 2.19.22
David Kastrup d...@gnu.org wrote in message news:871tgott5d@fencepost.gnu.org... I have to admit that I'm leaning towards the last solution. However, we have had a few regressions in 2.19.22. If Phil was thinking about rolling 2.19.23 this weekend, I'd probably roll in your local fix (and see whether we have similar cases elsewhere) and leave the more invasive change for proper review/discussion for later. -- David Kastrup Was planning on next week (the 12th). -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Squad
Simon Albrecht simon.albre...@mail.de wrote in message news:556f59d4.20...@mail.de... Hello Bug squad, is the list in http://lilypond.org/doc/v2.19/Documentation/contributor/bug-squad-checklists anywhere near up-to-date? It seems we don’t have a really prompt squad at hand, and I should be able to take over one or two days, except for Monday and Thursday. Yours, Simon It's not at all up-to-date, and any offers of help would be gratefully accepted. Do you have a Google account so we can add you to the tracker as a contributor? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond 2.19.20 on fedora gs bug
alexei vajniy.ale...@yandex.ru wrote in message news:loom.20150527t181108-...@post.gmane.org... I'm not top posting. % can't compile anything due to gs error % warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./n.pdf -c.setpdfwrite -fn.ps)' failed (256) % gs command itself gives Error: /undefinedresult in --glyphshow-- % generated ps files can't be read by gv or zathura-ps viewers % it worked normally on fedora 21 and lilypond 2.18.2 \version 2.19.20 \relative c {a} Could you try with the -v (verbose) switch for LilyPond, and let us know which version of GhostScript is reported? -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hairpins ending on key changes
Connor Harris connor...@gmail.com wrote in message news:loom.20150520t071924-...@post.gmane.org... In Lilypond 2.18.2 and possibly later versions, hairpins that end at the beginning a measure are engraved with their right ends slightly left of the barline. This looks bad if the note follows a key change, as there may be considerable space (depending on how many accidentals are notated in the key change) between the barline and the note on which the hairpin properly ends. In this fragment, I'd prefer the hairpin to continue all the way to the dynamic marking under the second note. { \key ces \major bes'1\ \key cis \major bis'\f } You can make the hairpin continue to the next note with \override Hairpin.to-barline = ##f -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement: more logical ambitus placement
Noeck noeck.marb...@gmx.de wrote in message news:555736b6.8020...@gmx.de... Hi Simon, I understand your point and it makes more sense after the key signature. But do you have any real life examples for that position (I hear people complaining about the “wrong” ambitus placement in LP)? I encountered only about 3 ambitus examples in my life and all where before the clef. I don't know if there are any rules, so I am just asking whether there is a reference? After all it is the aim to reproduce best standards (not to invent them), or not? I would find it even clearer if it would always show the accidental independent from the key signature (like having two e-flats with accidentals here: ambitus: es es', \key bes \major. Btw, it seems to be quite complicated to create an ambitus in Sibelius: http://www.rpmseattle.com/of_note/how-to-create-an-ambitus-in-sibelius-7-part-1/ It needs a whole tutorial. Cheers, Joram I cite 2 examples in the bug report. I found none written as lily does it. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Enhancement: more logical ambitus placement
Simon Albrecht simon.albre...@mail.de wrote in message news:55566a0f.50...@mail.de... Hello, currently, ambitus are placed at the very beginning of the first system, before clef and key signature. However, its meaning depends on both: without a clef, the pitches are unspecified, and it’s confusing that accidentals are set based on a key which has not yet been ‘announced’ (See also https://code.google.com/p/lilypond/issues/detail?id=762; there used to be a workaround with \set Staff.keySignature = #'() which doesn’t work anymore). I suggest to place the ambitus between key and time signatures, as seen in the attachment. The values in the space-alists are more or less wild guesses, as I don’t have much experience with this kind of settings. Do we really need an entry for ambitus in break-align-orders except for beginning of line? Yours, Simon ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Agreed: I've just looked at the Oxford Madrigals and Partsongs and this is how it is written there. The JOED Byrd music even puts the ambit after the time signature. I've added this to the tracker as http://code.google.com/p/lilypond/issues/detail?id=4396 -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: English note names generate errors
David Kastrup d...@gnu.org wrote in message news:87iobz9etr@fencepost.gnu.org... Federico Bruni f...@inventati.org writes: Il giorno lun 11 mag 2015 alle 17:15, David Kastrup d...@gnu.org ha scritto: Your bug summission page is very rude and annoying. We don't have a bug submission page: users are advised to mail problem reports to this bug list. I have no idea what page you used. In his message headers I read: X-Injected-Via-Gmane: http://gmane.org/ So he probably used this page: http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs Huh. I still don't have a good idea which part of the system would complain about lines longer than 80 characters though: frequently submissions contain code that clearly exceeds such sizes. -- David Kastrup The gmane interface itself complains. When you type characters into the web form, it breaks them to form lines shorter than 80 characters. When you paste, it doesn't, and then complains the line is too long so you have to break them yourself. It's _nowhere_ near as hard as the rather grumpy OP was claiming, though. I've done it frequently. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing 'crossStaff' warning?
Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote in message news:caphotuvp5-j7slwzeeepnqs1beh_ovkszksojo0hhtnq7ul...@mail.gmail.com... Hi Bug Squad, This thread follows a discussion on the French forum: http://lilypond-french-users.1298960.n2.nabble.com/Curieux-bogue-sur-un-croisement-de-portees-td7582841.html If I slightly modify this example: http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems and put the last d8 in the 'crossStaff' bloc: \layout { \context { \PianoStaff \consists #Span_stem_engraver } } { \new PianoStaff \new Staff { b d'4 r d'16\ e'8. g8 r\! e'8 f' g'4 e'2 } \new Staff { \clef bass \voiceOne \autoBeamOff \crossStaff { e g4 e, g16 a8. c8 d } \autoBeamOn g8 f g4 c2 } } its flag disappears (which is normal) but LP does not give any warning regarding this misplacement. Cheers, Pierre PS. I wonder if this could be related to https://code.google.com/p/lilypond/issues/detail?id=3025 I guess the issue is related, but it seems to be user error to me: why would you write a cross-staff chord when the note to be connected is not a note, but a rest? Just put the d outside the braces. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ugly output from \accidentalStyle piano
Rob Tuley rob.tu...@btinternet.com wrote in message news:loom.20150421t125453...@post.gmane.org... I'm not top posting. \version 2.18.2 \new PianoStaff % Output is consistent with the documentation, but the number of cautionary accidentals is ugly. \accidentalStyle piano \new Staff { c''4 c'' c'' c'' } \new Staff { d'8 cis' d' cis' d' cis' d' cis' } Elaine Gould would say it is correct. When returning to a pitch after alteration at a different octave, confirm the original pitch with an accidental, to avoid ambiguity. (Page 82). There are alternative accidental styles if you particularly don't want these cross-hand accidentals. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond