Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Updates: Status: Verified Comment #10 on issue 1058 by brownian.box: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 (No comment was entered for this change.) -- You received this message because you are listed in the own

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Updates: Status: Fixed Labels: fixed_2_13_18 Comment #9 on issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 I added 1.3 Dealing with errors. The subsections are small, but I like th

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #8 on issue 1058 by percival.music.ca: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 Yes, please do so. Links are never a problem. ... oh wait, I'm not wild about adding a 1.4. I kind-of wanted "how to read the manu

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #7 on issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 So now I have a new proposal. What if I add a section LM 1.4 Compilation Errors that simply introduces the fact that errors can occur

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #6 on issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 Hey, I've closed three issues in the last two days, and I have a patches being reviewed that will close two more. I'm with you, thoug

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #5 on issue 1058 by percival.music.ca: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 A rewrite of Usage has been planned for some time; it could well happen during GDP 2. But we seriously need to stop starting projec

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Updates: Labels: -Priority-Medium Priority-Postponed Comment #4 on issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 Ok -- I'll mark it postponed, and we'll see what happens after 2.14. But I

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #3 on issue 1058 by percival.music.ca: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 Yes, but how many of those people were looking at the new website, which gives much more prominence to the other manuals? To be cle

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #2 on issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 How many questions have we received on the user list in the last six months about a staff running off the page? That question is answ

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Comment #1 on issue 1058 by percival.music.ca: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 I disagree; this is reference-style info, and thus doesn't belong in Learning. -- You received this message because you are listed

Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning

Status: Accepted Owner: Labels: Type-Documentation Priority-Medium Frog New issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning http://code.google.com/p/lilypond/issues/detail?id=1058 The Usage manual has a section on Frequent Errors (Section 1.4) These