another annoyance with `Dynamics' context
Thanks to Neil, TextSpanner items are now displayed in `Dynamics' contexts. However, this exhibits another serious annoyance, as shown in bug issue #928. This time, I've tagged my bug report with `medium'... Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: can't compile docs
John Mandereau wrote 10 Dec 2009 Trevor Daniels wrote 9 Dec2009 Traceback (most recent call last): File "/home/trevor/lilypond-git/scripts/build/out/www_post", line 67, in map (os.mkdir, [os.path.join (out_root, d) for d in dirs]) OSError: [Errno 2] No such file or directory: 'out-www/offline-root/Documentation/automated-engraving' I doubt I understand why this happens. Could you insert the following in www_post.py at line 60 (just after dirs.sort()), run 'make doc' again (I don't care whether you make doc-clean first, it shouldn't matter) and send us build stdout/stderr starting from www_post.py invocation? print dirs John, many thanks for your reply, but thankfully the problem appears to have gone away. I modified www_post.py as you suggested, and then made a clean start by running ./autogen.sh, make doc-clean and then make doc in my master branch. This successfully built all the docs. I think I must have accidentally deleted some critical file while I was making space on my disk, as the only thing I did differently this time was to run ./autogen.sh. I'll now get back to trying to build the docs in my development branch. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
extract_texi_filenames fail for contributor.xref-map out-of-tree build
Doing an out-of-tree build: mkdir ../lily-out make distclean cd ../lily-out ../lilypond/configure make make doc produces a 0-byte contributor.xref-map and AAA-intro-reression.xref-map. It looks fine for INTALL, internals, snippets, usage, and web. (I'm surprised that it worked for web and not contributor) I'm still building in order to find out if anything else breaks, but so far I suspect that this breakage is causing GUB to fail. Recall that building contributor doesn't produce any .texi files in out-www/. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can't compile docs
Graham Percival wrote Thursday, December 10, 2009 1:40 AM On Wed, Dec 09, 2009 at 10:59:09PM +, Trevor Daniels wrote: Traceback (most recent call last): File "/home/trevor/lilypond-git/scripts/build/out/www_post", line 67, in map (os.mkdir, [os.path.join (out_root, d) for d in dirs]) OSError: [Errno 2] No such file or directory: 'out-www/offline-root/Documentation/automated-engraving' make[1]: *** [WWW-post] Error 1 make[1]: Leaving directory `/home/trevor/lilypond-git' make: *** [doc] Error 2 That _might_ be my fault, since I commented it out from essay.tely. However, it's still listed in the GNUmakefile, so I figured it would build anyway. I suspect that the *actual* error (i.e. the thing that's making automated-engraving fail to compile) was anywhere from 100 to 5000 lines (no joke) above this. Well, I never did get to the bottom of the problem. Clearing everything and starting again with ./autogen.sh in my master branch successfully built the docs. Looks like I accidently deleted something while trying to make space on my (virtual) hard drive. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: extract_texi_filenames fail for contributor.xref-map out-of-tree build
Le vendredi 11 décembre 2009 à 09:10 +, Graham Percival a écrit : > Doing an out-of-tree build: > mkdir ../lily-out > make distclean > cd ../lily-out > ../lilypond/configure > make > make doc > > produces a 0-byte contributor.xref-map I guess the problem might come from the lack of '-I $(src-dir)' flag, I'm trying to compile with this change. > AAA-intro-reression.xref-map. I get this too, this shouldn't matter. > I'm still building in order to find out if anything else breaks, but > so far I suspect that this breakage is causing GUB to fail. Recall > that building contributor doesn't produce any .texi files in out-www/. Yes, it does: it copies contributor.texi, but not the .itexis. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: accent and marcato shouldn't be quantized
On Thu, Dec 10, 2009 at 08:52:03PM -0800, Mark Polesky wrote:
> Graham Percival wrote:
> > It was added as a short-cut hack for
> > << c1 {s4\< s s\> s\!} >>
>
> So then I assume you're okay with me de-quantizing the
> espressivo as well.
I have no objection to this. I confess that my vague recollection
was that accents *could* be placed within the staff, but Kurt
Stone is certainly a better reference than me.
I'll let somebody else deal with the patch.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: can't compile docs
Le vendredi 11 décembre 2009 à 08:39 +, Trevor Daniels a écrit : > John, many thanks for your reply, but thankfully the problem > appears to have gone away. > > I modified www_post.py as you suggested, and then made a > clean start by running ./autogen.sh, make doc-clean and then > make doc in my master branch. This successfully built all > the docs. I think I must have accidentally deleted some critical > file while I was making space on my disk, as the only thing I > did differently this time was to run ./autogen.sh. If you delete a directory while 'make doc' (and more specifically www_post.py) was running, then I can understand the error you got, though there is little chance you manage to delete out-www/offline-root[/Documentation] between the time it's created and the time www_post tries to create out-www/offline-root/Documentation[/automated-engraving]. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Build failure on OS X: "error: template class without a name"
> Have you tried the suggested fix from the second thread? > > Something like > > sed -i 's|__vector|lily_vector|g' flower/include/std-vector.hh > > might be worth a try. > > Regards, > Neil You are right, according to http://www.mail-archive.com/fink-us...@lists.sourceforge.net/msg29281.html perl -pi -e 's|__vector|lily_vector|g' flower/include/std-vector.hh helped. Thanks! Now, the build proceeds, but after a while, I get the following error: flex -Cfe -p -p -oout/lexer.cc lexer.ll lexer.ll:605: multiple <> rules for start condition longcomment flex: fatal internal error, exec failed make[1]: *** [out/lexer.cc] Broken pipe make[1]: *** Deleting file `out/lexer.cc' make: *** [all] Error 2 What could this be? thSoft ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
2.13.9 out
2.13.9 has been uploaded and should be visible now. Could people give it a quick spin? NB: it is not visible on the main "download" page; you need to go directly to the "download site" link under "ancient versions". Alternately, go to the 2.13 docs -> (web) Community -> Download. Those links work just fine. :) Quick poll: I promised to announce 2.13.9 on the info list (after waiting 12-24 hours for tests to avoid any huge embarassment), but it seems that the website still only displays 2.13.7. Who thinks I should announce 2.13.9 with the website in the current state (i.e. telling people to look for the download site link under ancient versions), and who thinks I should wait until the website is fixed? Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix Tracker 918, Add extra RemoveEmpty*StaffContext functions to support "Frenched" scores (issue165096)
Hi Neil,
n.putt...@gmail.com wrote:
Hi Ian,
LGTM, apart from some formatting issues and a few incorrect \version
numbers.
Can you sort out the naming of the new regression tests? For
consistency with the existing test, I'd advise amending them as follows:
hara-kiri-drumstaff.ly
hara-kiri-rhythmicstaff.ly
hara-kiri-tabstaff.ly
Cheers,
Neil
Just info for fellow Frogs.
You can do this by using (for example)
$ cd
$ git mv input/regression/hara-kiri-drums.ly
input/regression/hara-kiri-drumstaff.ly
$ git mv input/regression/hara-kiri-tabs.ly
input/regression/hara-kiri-tabstaff.ly
$ git mv input/regression/hara-kiri-rhythmicstaves.ly
input/regression/hara-kiri-rhythmicstaff.ly
Using git mv updates your file system and the git info at the same time.
You can use
$ git mv -n
to test what you are about to do before actually doing the rename.
I'll do the other changes once I've renamed files and put up an amended
patch set on Rietveld.
Cheers,
Ian
http://codereview.appspot.com/165096/diff/1/2
File input/regression/hara-kiri-drums.ly (right):
http://codereview.appspot.com/165096/diff/1/2#newcode1
input/regression/hara-kiri-drums.ly:1: \version "2.13.8"
2.13.9
http://codereview.appspot.com/165096/diff/1/2#newcode2
input/regression/hara-kiri-drums.ly:2: \header { texidoc =
I know you've just copied the existing example, but it is a bit messy;
it would be preferable to tidy things up here:
\header {
texidoc = "Hara-kiri ...
http://codereview.appspot.com/165096/diff/1/2#newcode14
input/regression/hara-kiri-drums.ly:14:
trailing whitespace
http://codereview.appspot.com/165096/diff/1/2#newcode18
input/regression/hara-kiri-drums.ly:18: ragged-right= ##t
ragged-right =
http://codereview.appspot.com/165096/diff/1/2#newcode26
input/regression/hara-kiri-drums.ly:26: \new DrumStaff \drummode { sn4
sn sn sn \break s1 \break sn4 sn sn sn \break sn sn sn sn}
\drummode {
sn4 sn sn sn \break
s1 break
sn4 sn sn sn \break
sn4 sn sn sn
}
etc.
http://codereview.appspot.com/165096/diff/1/3
File input/regression/hara-kiri-percent-repeat.ly (left):
http://codereview.appspot.com/165096/diff/1/3#oldcode8
input/regression/hara-kiri-percent-repeat.ly:8: \new Staff { c''1 c''
\break c'' c'' }
<<
\new Staff
etc.
http://codereview.appspot.com/165096/diff/1/3
File input/regression/hara-kiri-percent-repeat.ly (right):
http://codereview.appspot.com/165096/diff/1/3#newcode1
input/regression/hara-kiri-percent-repeat.ly:1: \version "2.13.8"
2.13.9
http://codereview.appspot.com/165096/diff/1/3#newcode4
input/regression/hara-kiri-percent-repeat.ly:4: texidoc = "Staves,
RhythmicStaves, TabStaves and DrumStaves with percent repeats are not
suppressed."
line too long
http://codereview.appspot.com/165096/diff/1/3#newcode10
input/regression/hara-kiri-percent-repeat.ly:10: \new TabStaff \repeat
percent 4 {c1}
\repeat percent 4 { c1 }
http://codereview.appspot.com/165096/diff/1/3#newcode11
input/regression/hara-kiri-percent-repeat.ly:11: \new DrumStaff
\drummode { \repeat percent 4 {hh1} }
{ hh1 }
http://codereview.appspot.com/165096/diff/1/3#newcode16
input/regression/hara-kiri-percent-repeat.ly:16: \context {
\RemoveEmptyStaffContext }
indent two spaces only:
\layout {
\context { \RemoveEmptyStaffContext }
http://codereview.appspot.com/165096/diff/1/4
File input/regression/hara-kiri-rhythmicstaves.ly (right):
http://codereview.appspot.com/165096/diff/1/4#newcode1
input/regression/hara-kiri-rhythmicstaves.ly:1: \version "2.13.5"
2.13.9
http://codereview.appspot.com/165096/diff/1/4#newcode2
input/regression/hara-kiri-rhythmicstaves.ly:2: \header { texidoc =
same formatting nitpicks as hara-kiri-percent-repeat.ly
http://codereview.appspot.com/165096/diff/1/4#newcode14
input/regression/hara-kiri-rhythmicstaves.ly:14:
trailing whitespace
http://codereview.appspot.com/165096/diff/1/5
File input/regression/hara-kiri-tabs.ly (right):
http://codereview.appspot.com/165096/diff/1/5#newcode1
input/regression/hara-kiri-tabs.ly:1: \version "2.13.5"
2.13.9
http://codereview.appspot.com/165096/diff/1/5#newcode3
input/regression/hara-kiri-tabs.ly:3: \header { texidoc =
same formatting nitpicks as hara-kiri-percent-repeat.ly
http://codereview.appspot.com/165096/diff/1/5#newcode15
input/regression/hara-kiri-tabs.ly:15: This example was done with a
pianostaff, which has fixed distance
This can be removed, since it's not true (and hasn't been for a long
time)
http://codereview.appspot.com/165096/diff/1/5#newcode18
input/regression/hara-kiri-tabs.ly:18:
trailing whitespace
http://codereview.appspot.com/165096/diff/1/6
File ly/engraver-init.ly (left):
http://codereview.appspot.com/165096/diff/1/6#oldcode1013
ly/engraver-init.ly:1013: RemoveEmptyRhythmicStaffContext= \context {
RemoveEmptyRhythmicStaffContext = \context {
http://codereview.appspot.com/165096/diff/1/6
File ly/engraver-init.ly (right):
http://codereview.appspot.com/165096/diff/1/6#newcode1012
ly/engraver-init.ly:1012: % Add RemoveEmpty*StaffCont
Re: 2.13.9 out
Le vendredi 11 décembre 2009 à 14:24 +, Graham Percival a écrit : > Quick poll: I promised to announce 2.13.9 on the info list (after > waiting 12-24 hours for tests to avoid any huge embarassment), but > it seems that the website still only displays 2.13.7. Who thinks > I should announce 2.13.9 with the website in the current state > (i.e. telling people to look for the download site link under > ancient versions), and who thinks I should wait until the website > is fixed? I don't understand, is "make update-versions" and/or make broken on lilypond.org? On my box, make builds the site perfectly, except that it idiotly recalls update-versions for each language. Are you sure the last change in GNUmakefile has be updated in the appropriate trusted-scripts/ directory on lilypond.org? Best, John PS: I sent you the Hungarian announce which could be included in the email notification. signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Add option to indicate frets by letters in tablature
I've just posted patch set 3 to Reitveld, after quite some struggles with juggling regression-testing and doc-building in a too-small virtual ubuntu system. See http://codereview.appspot.com/164063 The main change from patch set 2 is to generalise the input format of the context property fretLabels to permit markup, and changing the property's name from the previous fretLetters. Thanks to Carl and Neil for help with this. I've added two news items, and dealt with the other minor comments. Reviews requested. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.13.9 out
Graham Percival wrote Friday, December 11, 2009 2:24 PM 2.13.9 has been uploaded and should be visible now. Could people give it a quick spin? Downloaded mingw and installed fine in Vista. Tested lilypond-book and lily by compiling notation/pitches.itely - fine convert-ly - fine Dropped a couple of files onto desktop icon - not so good A log file was produced which stopped at Drawing systems... but no .ps or .pfd appeared. The same files compiled fine from command line. I don't know what the problem is, but as I never do this normally maybe it's always been that way on my system ?? Perhaps it's because I don't run with administrator priviledges which means I can't write to the desktop ?? Quick poll: I promised to announce 2.13.9 on the info list (after waiting 12-24 hours for tests to avoid any huge embarassment), but it seems that the website still only displays 2.13.7. Who thinks I should announce 2.13.9 with the website in the current state (i.e. telling people to look for the download site link under ancient versions), and who thinks I should wait until the website is fixed? Fix the website. It's important. It gives a very bad impression at the moment. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.13.9 out
On Fri, Dec 11, 2009 at 6:24 AM, Graham Percival wrote: > > Quick poll: I promised to announce 2.13.9 on the info list (after > waiting 12-24 hours for tests to avoid any huge embarassment), but > it seems that the website still only displays 2.13.7. Who thinks > I should announce 2.13.9 with the website in the current state > (i.e. telling people to look for the download site link under > ancient versions), and who thinks I should wait until the website > is fixed? Do we know what's wrong with the website? Is this something I can help fix? -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.13.9 out
Le vendredi 11 décembre 2009 à 13:35 -0800, Patrick McCarty a écrit : > Do we know what's wrong with the website? Is this something I can help fix? No, as my previous reply probably shows, only somebody with a login on lilypond.org (and possibly privileges to update the makefiles and scripts in the trsuted scripts dir) can fix it. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: UTF-8 support needs implementing to fix all bidi/rtl/ltr issues
Thank you for filing that bug issue! How are things progressing? Also, can I make a $100 donation in gratitude to the person implementing the fix? Who is the responsible party to send the money to? Ted On Tue, Dec 08, 2009 at 03:14:43PM -0800, Patrick McCarty wrote: On Tue, Dec 8, 2009 at 5:04 AM, Valentin Villenave wrote: On Tue, Dec 8, 2009 at 1:13 AM, Patrick McCarty wrote: I'll add this to the issue tracker tomorrow sometime, hopefully, unless someone else beats me to it. I certainly won't, since you have a better understanding of these things than I do. Just remember to post the link in this thread for achival purposes :) Okay, reported here: http://code.google.com/p/lilypond/issues/detail?id=927 Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel -- There's a party in your skull. And you're invited! Name:Ted Walther Phone: 208-310-7032 Skype: tederific Email: t...@reactor-core.org Address: #225 17700 58 Ave, Surrey, BC V3S1L6 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: UTF-8 support needs implementing to fix all bidi/rtl/ltr issues
On Fri, Dec 11, 2009 at 11:44 PM, Ted Walther wrote: > Thank you for filing that bug issue! How are things progressing? Also, > can I make a $100 donation in gratitude to the person implementing the > fix? Who is the responsible party to send the money to? I've added your bounty offer on the tracker page. Patrick is officially in charge of this issue (and he's probably the most likely to fix it). That being said, I'd wait until the feature is released and verified to work before sending the money ;-) Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: accent and marcato shouldn't be quantized
2009/12/11 Mark Polesky :
> Graham Percival wrote:
>> It was added as a short-cut hack for
>> << c1 {s4\< s s\> s\!} >>
>
> So then I assume you're okay with me de-quantizing the
> espressivo as well. Is the attached patch okay to apply,
LGTM.
> do I need to do anything described in CG 8.7 "Adding or
> modifying features"? Should I add a @item to changes.tely?
No and no. :)
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix Tracker 918, Add extra RemoveEmpty*StaffContext functions to support "Frenched" scores (issue165096)
Hi,
I've implemented Neil's comments, re-run regression tests locally and
uploaded amended patches to Rietveld.
I think this should be ready to push now.
Cheers,
Ian
http://codereview.appspot.com/165096/diff/1/2
File input/regression/hara-kiri-drums.ly (right):
http://codereview.appspot.com/165096/diff/1/2#newcode1
input/regression/hara-kiri-drums.ly:1: \version "2.13.8"
On 2009/12/10 23:43:35, Neil Puttock wrote:
2.13.9
Done.
http://codereview.appspot.com/165096/diff/1/2#newcode14
input/regression/hara-kiri-drums.ly:14:
On 2009/12/10 23:43:35, Neil Puttock wrote:
trailing whitespace
Done.
http://codereview.appspot.com/165096/diff/1/2#newcode18
input/regression/hara-kiri-drums.ly:18: ragged-right= ##t
On 2009/12/10 23:43:35, Neil Puttock wrote:
ragged-right =
Done.
http://codereview.appspot.com/165096/diff/1/2#newcode26
input/regression/hara-kiri-drums.ly:26: \new DrumStaff \drummode { sn4
sn sn sn \break s1 \break sn4 sn sn sn \break sn sn sn sn}
On 2009/12/10 23:43:35, Neil Puttock wrote:
\drummode {
sn4 sn sn sn \break
s1 break
sn4 sn sn sn \break
sn4 sn sn sn
}
etc.
Done.
http://codereview.appspot.com/165096/diff/1/3
File input/regression/hara-kiri-percent-repeat.ly (left):
http://codereview.appspot.com/165096/diff/1/3#oldcode8
input/regression/hara-kiri-percent-repeat.ly:8: \new Staff { c''1 c''
\break c'' c'' }
On 2009/12/10 23:43:35, Neil Puttock wrote:
<<
\new Staff
etc.
Done.
http://codereview.appspot.com/165096/diff/1/3
File input/regression/hara-kiri-percent-repeat.ly (right):
http://codereview.appspot.com/165096/diff/1/3#newcode4
input/regression/hara-kiri-percent-repeat.ly:4: texidoc = "Staves,
RhythmicStaves, TabStaves and DrumStaves with percent repeats are not
suppressed."
On 2009/12/10 23:43:35, Neil Puttock wrote:
line too long
Doc comment split into two shorter lines.
Done.
http://codereview.appspot.com/165096/diff/1/3#newcode11
input/regression/hara-kiri-percent-repeat.ly:11: \new DrumStaff
\drummode { \repeat percent 4 {hh1} }
On 2009/12/10 23:43:35, Neil Puttock wrote:
{ hh1 }
Done.
http://codereview.appspot.com/165096/diff/1/3#newcode16
input/regression/hara-kiri-percent-repeat.ly:16: \context {
\RemoveEmptyStaffContext }
On 2009/12/10 23:43:35, Neil Puttock wrote:
indent two spaces only:
\layout {
\context { \RemoveEmptyStaffContext }
Done.
http://codereview.appspot.com/165096/diff/1/4
File input/regression/hara-kiri-rhythmicstaves.ly (right):
http://codereview.appspot.com/165096/diff/1/4#newcode2
input/regression/hara-kiri-rhythmicstaves.ly:2: \header { texidoc =
On 2009/12/10 23:43:35, Neil Puttock wrote:
same formatting nitpicks as hara-kiri-percent-repeat
Done.
http://codereview.appspot.com/165096/diff/1/4#newcode4
input/regression/hara-kiri-rhythmicstaves.ly:4: " Hara-kiri staves kill
themselves if they are empty. This
"kill themselves" > "are suppressed" (fewer characters, better style)
http://codereview.appspot.com/165096/diff/1/4#newcode5
input/regression/hara-kiri-rhythmicstaves.ly:5: example really contains
three rhythmic staves, but as they progress, empty ones
"they progress" > "it progresses" (fewer characters, clearer meaning)
http://codereview.appspot.com/165096/diff/1/4#newcode14
input/regression/hara-kiri-rhythmicstaves.ly:14:
On 2009/12/10 23:43:35, Neil Puttock wrote:
trailing whitespace
Done.
http://codereview.appspot.com/165096/diff/1/5
File input/regression/hara-kiri-tabs.ly (right):
http://codereview.appspot.com/165096/diff/1/5#newcode1
input/regression/hara-kiri-tabs.ly:1: \version "2.13.5"
On 2009/12/10 23:43:35, Neil Puttock wrote:
2.13.9
Done.
http://codereview.appspot.com/165096/diff/1/5#newcode1
input/regression/hara-kiri-tabs.ly:1: \version "2.13.5"
File now renamed hara-kiri-tabstaff.ly
http://codereview.appspot.com/165096/diff/1/5#newcode3
input/regression/hara-kiri-tabs.ly:3: \header { texidoc =
On 2009/12/10 23:43:35, Neil Puttock wrote:
same formatting nitpicks as hara-kiri-percent-repeat.ly
Done.
http://codereview.appspot.com/165096/diff/1/5#newcode5
input/regression/hara-kiri-tabs.ly:5: " Hara-kiri staves kill themselves
if they are empty. This
"kill themselves" > "are suppressed"
http://codereview.appspot.com/165096/diff/1/5#newcode6
input/regression/hara-kiri-tabs.ly:6: example really contains three tab
staves, but as they progress, empty ones
"they progress" > "it progresses"
http://codereview.appspot.com/165096/diff/1/5#newcode15
input/regression/hara-kiri-tabs.ly:15: This example was done with a
pianostaff, which has fixed distance
On 2009/12/10 23:43:35, Neil Puttock wrote:
This can be removed, since it's not true (and hasn't been for a long
time)
Done.
http://codereview.appspot.com/165096/diff/1/5#newcode18
input/regression/hara-kiri-tabs.ly:18:
On 2009/12/10 23:43:35, Neil Puttock wrote:
trailing whitespace
Done.
http://codereview.appspot.com/165096/diff/1/6
File ly/engraver-init.ly (left):
http://codereview.appspot.com/165096/diff/1/6#o
Re: UTF-8 support needs implementing to fix all bidi/rtl/ltr issues
On Fri, Dec 11, 2009 at 3:32 PM, Valentin Villenave wrote: > On Fri, Dec 11, 2009 at 11:44 PM, Ted Walther wrote: >> Thank you for filing that bug issue! How are things progressing? Also, >> can I make a $100 donation in gratitude to the person implementing the >> fix? Who is the responsible party to send the money to? > > I've added your bounty offer on the tracker page. Patrick is > officially in charge of this issue (and he's probably the most likely > to fix it). That being said, I'd wait until the feature is released > and verified to work before sending the money ;-) Great! Yes, I've started investigating the issue, but I'm running into some snags that I will be taking up on the Pango mailing list hopefully within the next day or two. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.13.9 out
On Fri, Dec 11, 2009 at 08:47:47PM -, Trevor Daniels wrote: > > Graham Percival wrote Friday, December 11, 2009 2:24 PM > >> 2.13.9 has been uploaded and should be visible now. Could people >> give it a quick spin? > > Dropped a couple of files onto desktop icon - not so good > A log file was produced which stopped at Drawing systems... > but no .ps or .pfd appeared. > The same files compiled fine from command line. > I don't know what the problem is, but as I never do this > normally maybe it's always been that way on my system ?? > Perhaps it's because I don't run with administrator priviledges > which means I can't write to the desktop ?? Hmm. If a log file was created, then I think you have permission to write a new file to the desktop (assuming that's where the log file was). Can anybody on windows clarify this? Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.13.9 out
On Fri, Dec 11, 2009 at 01:35:24PM -0800, Patrick McCarty wrote: > On Fri, Dec 11, 2009 at 6:24 AM, Graham Percival > wrote: > > > > Quick poll: I promised to announce 2.13.9 on the info list (after > > waiting 12-24 hours for tests to avoid any huge embarassment), but > > it seems that the website still only displays 2.13.7. Who thinks > > I should announce 2.13.9 with the website in the current state > > (i.e. telling people to look for the download site link under > > ancient versions), and who thinks I should wait until the website > > is fixed? > > Do we know what's wrong with the website? Is this something I can help fix? No, I don't know yet. You can help by taking care of Valentin's CSS patch, since I always prioritize dealing with patches over my own new work. I'll deal with James Lowe's recent contribution, then start looking at the website. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Catching up on bugs
With the release of 2.13.9, we now believe that all bugs are either fixed, or have been added to the issue tracker. If you have reported a bug and it is not in the tracker, please check the bug reporting guidelines and re-submit it. http://lilypond.org/doc/v2.13/Documentation/web/bug-reports Valentin, James: I think it's time for the annual "checking the regression tests". Instructions are in the Contributor's Guide 6.4 Checking and verifying issues. I'll let you two decide who does what. It would be nice if this was done within a week or so; it's not a huge job. After that, we'll have 2.13.10, and then you two can start checking all issues. There will be more specific guidelines about tagging and priorities. I'm going to collect my thoughts into specific proposals, and begin discussions later today or tomorrow. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.13.9 out
On Fri, Dec 11, 2009 at 06:02:45PM +0100, John Mandereau wrote: > Are you sure the last change in GNUmakefile has be updated in > the appropriate trusted-scripts/ directory on lilypond.org? Updating the GNUmakefile seems to have done it; apparently we forgot to do this. > PS: I sent you the Hungarian announce which could be included in the > email notification. Yes, included. I'm not touching the web branch, so somebody else can handle updating that. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
releases plans for Dec and 2010
Just so that people know what's planned... - another beta for 2.12.3 will happen as soon as I can build the tests and docs. Jan and I will continue to work on this; hopefully it'll be out in a few days. This will be the last 2.12 release. - 2.13.10 will happen fairly soon thereafter; the main goal of this release will be to test the release plans. - the first beta release of 2.14 will happen as soon as either 1) we have no Regression or High-priority items in the tracker, or 2) all the issues in the tracker have been re-categorized with the upcoming new guidelines. - after 2.14, we'll begin having much shorter unstable development phases. I know I said this last year and it didn't happen, so I have pretty low credibility on this score, but the difference is that *now* I can build GUB. To assist in this, in the near future I'll set up a daily out-of-tree building system for lilypond (I've done it before for marsyas). If any build fails, it will send rude messages to lilypond-devel with a list of the names of everybody who committed things since the last successful build. :) For the latter part of the year... GLISS will start shortly after 2.14 is out, and will probably run for 6 - 12 months. We'll save up all the gliss syntax changes during that time. Once we know what we want to do, we'll release one more 2.x version, apply all the syntax changes, then release 3.0 a week or two later. Some people will still complain about the syntax changes, but I think this is the best compromise we can have: if anybody wants to maintain the old 2.x branch, at least they know that 2.18.0 is the same (modulo syntax changes) as 3.0.0. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
has issue #774 worked with a stable release?
Could someone please check issue #774 with a stable release (either 2.10 or 2.12) so that I can probably set the regression flag? At the time of my report, I only had 2.11.13 for comparison, which is a developer's version, and I still don't have any stable releases installed. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: releases plans for Dec and 2010
On Sat, 2009-12-12 at 07:00 +, Graham Percival wrote: > Just so that people know what's planned... > - another beta for 2.12.3 will happen as soon as I can build the tests > and docs. Jan and I will continue to work on this; hopefully it'll be > out in a few days. This will be the last 2.12 release. > > - 2.13.10 will happen fairly soon thereafter; the main goal of this > release will be to test the release plans. > > - the first beta release of 2.14 will happen as soon as either 1) we > have no Regression or High-priority items in the tracker, or 2) all > the issues in the tracker have been re-categorized with the upcoming > new guidelines. > > - after 2.14, we'll begin having much shorter unstable development > phases. I know I said this last year and it didn't happen, so I have > pretty low credibility on this score, but the difference is that *now* > I can build GUB. > > To assist in this, in the near future I'll set up a daily out-of-tree > building system for lilypond (I've done it before for marsyas). If > any build fails, it will send rude messages to lilypond-devel with a > list of the names of everybody who committed things since the last > successful build. :) Would it be feasible (using git-bisect) to pin down the exact failing commit? ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: has issue #774 worked with a stable release?
On Fri, Dec 11, 2009 at 11:13 PM, Werner LEMBERG wrote: > > Could someone please check issue #774 with a stable release (either > 2.10 or 2.12) so that I can probably set the regression flag? At the > time of my report, I only had 2.11.13 for comparison, which is a > developer's version, and I still don't have any stable releases > installed. Yes, it works with 2.10.33. The regression appears to have occurred between 2.11.30 and 2.11.31. -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
