Re: First task for a new Frog (LilyPond bug-hunter)
Hi Carl, If this is something I'd be able to do on a Windows system then I'd like to sign up as a Tadpole (apprentice Frog). :-) Cheers. Ian Carl D. Sorensen wrote: Dear LilyPond users, You may have seen Graham's request for LilyPond Frogs, who will fix LilyPond bugs (trying to fix bugs at an average rate of one per month). For some of you who are anticipating getting involved in bug-hunting, I have a simple task to get you involved in modifying the LilyPond source code. Although I could give this task to one person, I'd prefer to split it among half-a-dozen Frogs or so. The task is to add documentation strings for all of the undocumented music functions shown in Notation Reference 6.1.7. There are approximately 35 undocumented functions. That leaves about 6 per Frog who chooses to get involve. This task will be an easy way to get started. It involves editing scheme files which are available in the binary distribution. No compiling will need to be done. You will become familiar with the tools for searching through the source code to find particular music functions. You will also become familiar with editing scheme code and creating patches from the edited scheme code. For convenience, you may choose to use git, which simplifies the creation of patches. You will not need to worry about breaking LilyPond; I will take the responsibility for reviewing, obtaining approval for, and applying your patches. If you're interested in signing up as a Frog for this task or for any other bug you'd like to chase, please let me know. Thanks, and Happy New Year! Carl Sorensen ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- View this message in context: http://www.nabble.com/First-task-for-a-new-Frog-%28LilyPond-bug-hunter%29-tp21243859p21246179.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: insert blanc first page with page-turn-breaking
Hi Toine, Print it out in two stages from Adobe reader. 1. Print just the first page (numbered page 2). If you are printing with duplex on, the printer shouldf spit out the blank page to complete the job. 2. Print the rest of the pages (numbered 3 to nn) by setting the page range box in the print print dialogue. Your page turns should now be right. in the printed output. HTH Cheers, Ian Hulin Toine Schreurs wrote: The page-turn-breaking does a marvellous job. If necessary, the output starts at page 2. Is it possible to insert a blanc first page in that case? I want to print the results with a duplex printer, and without the first blanc page, all page turns turn out to be wrong. Toine Schreurs ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- View this message in context: http://www.nabble.com/insert-blanc-first-page-with-page-turn-breaking-tp19686792p19699566.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: renaming Program {usage, reference}
I hope this contribution isn't too late, but here goes. I'm commenting here before I have a look closely at the PDFs and possibly get bogged down in detail. Isn't the purpose of the Internals Reference to show Lilypond users how to customize/interpreter the compiler to produce source code which will represent and produce music notation in a way that is convenient and comprehensible to them? Don't they then have the option of doing this by programming at either one of two levels, i.e. using the Lilypond language (variables, accessing Lilypond 'objects', 'attributes ' or 'methods'), or if needed, dropping into Lilypond's internal macro language, Scheme. If I understand correctly your Internals Reference needs to cover both these levels of usage, and maybe a good title may be Customization and Internals Reference Manual (CIR)? Or have I missed several points in taking my helicopter view of the GPD green fields site :-)? Cheers, Ian Hulin (Now off to have a look at the PDFs). Graham Percival-2 wrote: The strong editorial decision from a few months ago is this: Notation Reference: defines the lilypond input syntax. Application Usage: how to compile the syntax, how to convert to/from the syntax (including old versions), including the syntax in other programs, etc. Internals Reference: defines the under the hood lilypond stuff. Learning Manual: prepares users for those other manuals. (this is explained at the top of policy.txt -- if it's not clear, please suggest a rewrite) For people who like to print out PDFs, I expect them to print out the LM, NR, and AU. If they want to save paper, by all means pick and choose -- for example, I wouldn't print out any of NR chapter 2, since I've never used any of the notation in it. But there is certainly no the NR is the only manual you should print out thing. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- View this message in context: http://www.nabble.com/GDP%3A-renaming-Program-%7Busage%2C-reference%7D-tf4742154.html#a13665226 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Scheme Problem
Hi Brett, Just a thought - the normal syntax for \repeat is \repeat unfold 9 { music statements } in your declaration you've put the keyword in quotes. Does it help if you remove them? E.g. compFor = #(define-music-function (parser location beats) (number?) #{ \override Rest #'stencil = #ly:percent-repeat-item-interface::beat-slash \override Rest #'thickness = #'0.48 \override Rest #'slope = #'1.7 \repeat unfold $beats { r4 } \revert Rest #'stencil #}) I don't know any of the Lilypond or Scheme internals but there's a chance that this could be confusing a parser or lexical analyzer somewhere along the line. Software diagnostic messages are sometimes just an opener for negotiation... Cheers, Ian Brett Duncan-2 wrote: The following function is an attempt on my part to learn how to create such functions, based on what appears in the User Manual. The function itself is not really important, just a problem I set for myself. It's supposed to take a number as its argument and produce the equivalent number of slashes, the idea being to use the slash as a comping symbol, and substituting the slash for the normal appearance of a quarter rest. compFor = #(define-music-function (parser location beats) (number?) #{ \override Rest #'stencil = #ly:percent-repeat-item-interface::beat-slash \override Rest #'thickness = #'0.48 \override Rest #'slope = #'1.7 \repeat unfold $beats { r4 } \revert Rest #'stencil #}) But when I put \compFor #16 into my .ly file, the following error occurs: syntax error, unexpected NUMBER_IDENTIFIER, expecting DIGIT or UNSIGNED \repeat unfold \lilyvartmpb { r4 } Can someone point out to me where I'm going wrong? Thanks, Brett -- Brett Duncan [EMAIL PROTECTED] Always do right - this will gratify some and astonish the rest. Mark Twain ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- View this message in context: http://www.nabble.com/Scheme-Problem-tf2900758.html#a8107195 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lilytool - using crescendo/descrescendo tags crashes with beanshelll error
Apologies to the list if there's a separate place for reporting Lilypond Tool for JEdit Errors, but . . . Hi Bert, I selected a small area of music e.g. a4 b cs d and then used the Lilypond | Tags | Crescendo menu option in Jedit. This then crashes with a beanshell alert box stating] Parse error at line 1, column 48. Encountered : ! lots of Java traceback. Unfortunately I can't insert the full traceback here. Please e-mail if you need it and I'll send it to you. Cheers, Ian Hulin -- View this message in context: http://www.nabble.com/Lilytool---using-crescendo-descrescendo-tags-crashes-with-beanshelll-error-tf2726703.html#a7604345 Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
How to generate a counter for repeated bars
Please forgive me if this is an obvious case of RTFM, but how do you get to disply a counter over a section of repeated bars. I am using using unfold as I don't want any actual ||: . . . :|| sections in the part. I know there are counters available for things like percent repeats and suchlike. I there any property or variable I can set to get the desired result? For example I want to get \repeat unfold 4 {c4 d e f |} to generate 1 23 4 | c d e f |c d e f|c d e f|c d e f| I'm still learning the music notation syntax and haven't tried the delights of customizing Lilypond with scheme yet. Thanks in advance for any advice on cracking this one. Cheers, Ian Hulin -- View this message in context: http://www.nabble.com/How-to-generate-a-counter-for-repeated-bars-tf2204902.html#a6106399 Sent from the Gnu - Lilypond - User forum at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user