Re: GUB fails to rebuild, configure issues?
Op dinsdag 11-08-2009 om 21:01 uur [tijdzone -0700], schreef Graham Percival: > On Tue, Aug 11, 2009 at 02:30:53PM +0200, John Mandereau wrote: > > Le mardi 11 août 2009 à 04:46 -0700, Graham Percival a écrit : > > > Odd behavior: if I rm -rf target/*/build/lilypond*, > > > I thought that I'd seen error messages about needing to remove > > > config.hh, but this last time that I cleaned things out and > > > generated the error, there's no such message. > > Got it now! > > /home/lilypond/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-master/config.hh > is out of date > *** Remove it and rerun autogen: > rm > /home/lilypond/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-master/config.hh; > ./autogen.sh This is now fixed in master. It turns out that git reset --hard updates all time stamps, even on files that are not modified. Unlike git checkout which makes a point of documenting the importance of preserving/updating timestamps, git reset --hard blindly destroys all timestamps on not-modified files. This breaks configure-up-to-date checks, notably lilypond's. Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
2.13.4 "I'm now a Glasgow student" released
Rejoice, everybody! I've officially registered (matriculated, as it's called here) as a PhD student at Glasgow University. Postgraduate research students had to wait until today, so despite having building keys, a computer, and demonstrating labs for first-year students who don't know how to solder, I had no official standing with the university until 20 minutes ago. Of much more importance to you all, 2.13.4 has been accidentally uploaded. As previously mentioned, this wasn't a particularly planned release; it just happened while Jan and I were bashing away at the various scripts and testing stuff. Of much more annoyance to some of you, the regtest comparisons are completely borked. Helpful suggestions would be appreciated. I'll start looking at how these are generated on Monday. As previously mentioned, I'm hoping to have 2.13.5 out in a week or so. Basically, as soon as I can generate comparisons (yes Mats, comparisons to 2.13.3) and can write down a reliable series of steps, I'm pushing 2.13.5 out the door. I therefore suggest that we don't advertize this release. Once 2.13.5 is out, I'll do 2.12.whatever. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Errors in Documentation/snippets
Hello,
glad to see that 2.13.4 is out!
However, by clicking through the docs, I found some errors on
http://lilypond.org/doc/v2.13/Documentation/snippets/Fretted-strings#Fretted-strings
1) Guitar slides:
Here the ledger lines are still visible. Moreover, guitar notation is
generally
notated with \clef "treble_8".
%% Hide fret number: useful to draw slide into/from a casual point of
%% the fretboard.
hideFretNumber = { \once \override TabNoteHead #'transparent = ##t
\once \override NoteHead #'transparent = ##t
\once \override Stem #'transparent = ##t
\once \override NoteHead #'no-ledgers = ##t %%%<- should be added
}
music= \relative c' {
\grace { \hideFretNumber d8\2 \glissando s2 } g2\2
\grace { \hideFretNumber g8\2 \glissando s2 } d2 |
\grace { \hideFretNumber c,8 \glissando s } f4\5^\markup \tiny "Slide into"
\grace { \hideFretNumber f8 \glissando s } a4\4
\grace { \hideFretNumber e'8\3 \glissando s } b4\3^\markup \tiny "Slide
from"
\grace { \hideFretNumber b'8 \glissando s2 } g4 |
}
\score {
<<
\new Staff {
\clef "G_8" %%%<_ should be added
\music
}
\new TabStaff {
\music
}
>>
}
2) Modern TAB text clef
I don't know whether this snippet is still needed because since 2.13.4
we have
\clef "moderntab" as an option, so no markup constructs are necessary.
If this example should stay, it can simply be achieved by:
\new TabStaff {
\clef "moderntab"
a
}
If there is a consensus whether 2) should be deleted or changed, I can
create a small patch for this.
Marc
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in Documentation/snippets
On Thu, Sep 24, 2009 at 04:05:22PM +0200, Marc Hohl wrote: > 1) Guitar slides: > > Here the ledger lines are still visible. Moreover, guitar notation is > generally > notated with \clef "treble_8". I'll let a guitar person handle this. > %% Hide fret number: useful to draw slide into/from a casual point of > %% the fretboard. Add this to LSR yourself, then tell us what the snippet number is. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Errors in Documentation/snippets
Dear tablature users,
Here's the chance for you to step up and help LilyPond.
Marc has added substantially to the tablature support for LilyPond. Now we
need to have the documentation added.
I'm hoping we can get one of the tablature users to take care of the
documentation. I'll be happy to provide the support needed to make this
happen.
It would be great if it could be done this week, because 2.13.5 is coming
out soon.
Please let me know if you're willing to tackle this.
Thanks,
Carl
On 9/24/09 8:05 AM, "Marc Hohl" wrote:
> Hello,
>
> glad to see that 2.13.4 is out!
>
> However, by clicking through the docs, I found some errors on
>
> http://lilypond.org/doc/v2.13/Documentation/snippets/Fretted-strings#Fretted-s
> trings
>
> 1) Guitar slides:
>
> Here the ledger lines are still visible. Moreover, guitar notation is
> generally
> notated with \clef "treble_8".
>
> %% Hide fret number: useful to draw slide into/from a casual point of
> %% the fretboard.
> hideFretNumber = { \once \override TabNoteHead #'transparent = ##t
> \once \override NoteHead #'transparent = ##t
> \once \override Stem #'transparent = ##t
> \once \override NoteHead #'no-ledgers = ##t %%%<- should be added
> }
>
> music= \relative c' {
> \grace { \hideFretNumber d8\2 \glissando s2 } g2\2
> \grace { \hideFretNumber g8\2 \glissando s2 } d2 |
>
> \grace { \hideFretNumber c,8 \glissando s } f4\5^\markup \tiny "Slide into"
> \grace { \hideFretNumber f8 \glissando s } a4\4
> \grace { \hideFretNumber e'8\3 \glissando s } b4\3^\markup \tiny "Slide
> from"
> \grace { \hideFretNumber b'8 \glissando s2 } g4 |
> }
>
> \score {
> <<
> \new Staff {
> \clef "G_8" %%%<_ should be added
> \music
> }
> \new TabStaff {
> \music
> }
>>>
> }
>
>
>
> 2) Modern TAB text clef
>
> I don't know whether this snippet is still needed because since 2.13.4
> we have
> \clef "moderntab" as an option, so no markup constructs are necessary.
> If this example should stay, it can simply be achieved by:
>
> \new TabStaff {
> \clef "moderntab"
> a
> }
>
> If there is a consensus whether 2) should be deleted or changed, I can
> create a small patch for this.
>
> Marc
>
>
>
>
>
>
>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Progress indicator
Hi all, I'd like to propose the following as a possibility to provide a simple progress indicator for the "Preprocessing graphical objects" stage. I'm happy to read your comments. http://codereview.appspot.com/122051 Regards, Michael ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
line breaks and broken beams
What's the reason that line breaks are by default forbidden if there is a broken beam crossing the bar line, and that you have to set the `breakable' flag manually to override it? BTW, it is very unpleasant that lilypond doesn't emit any kind of warning if it produces an overlong staff caused by that issue. It silently accumulates unbreakable bars and happily walks out of the right margin. I would consider this behaviour a bug. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
MacUpdate Dev: LilyPond updated
lilypond.org, LilyPond 2.13.2-0 has just been updated to version 2.13.4-1 on MacUpdate. Check it out at: http://www.macupdate.com/info.php/id/19024/lilypond Please keep MacUpdate informed of any new Mac version releases of your products, so we can promote them for you. You can update your listing by signing up for a developer tools account: http://www.macupdate.com/developer/ Partner in our 24-hour promotion of your software through mupromo.com: http://www.mupromo.com/ -MacUpdate Team www.macupdate.com [You're being notified of this update because you're listed as the developer of LilyPond. Please email us if you are not the developer: upda...@macupdate.com]. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
dutch translation error
Hi, Has someone fixed this little typo in the dutch translation yet: "kan wellicht geen goede waardestreephelling kunnen vinden" should be "kan wellicht geen goede waardestreephelling vinden" -- Martin Tarenskeen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
