2.14 release, or GOP now (part 2)

A brief reminder of the timeline: - 18 Sep 2010: "we need to sort out various policies, but let's wait until 2.14" http://lists.gnu.org/archive/html/lilypond-devel/2010-09/msg00178.html - 22 Sep 2010: "alpha test 1 for 2.14, only 1 critical issue" http://lists.gnu.org/archive/html/info-lilypond/2

Re: GUB target_cpu error

On Mon, Nov 29, 2010 at 07:40:17AM +0100, Ralf Wildenhues wrote: > * Graham Percival wrote on Mon, Nov 29, 2010 at 07:28:09AM CET: > > I would be astonished if the same functionality couldn't be > > reached using POSIX shell commands, which should work on any unix > > shell. > > This is about 'sho

Re: GUB target_cpu error

* Graham Percival wrote on Mon, Nov 29, 2010 at 07:28:09AM CET: > I would be astonished if the same functionality couldn't be > reached using POSIX shell commands, which should work on any unix > shell. This is about 'shopt -s nocasematch', right? No, Posix shell doesn't have shopt, nor does it h

Re: GUB target_cpu error

On Sun, Nov 28, 2010 at 11:58:48PM +0100, Valentin Villenave wrote: > On Sun, Nov 28, 2010 at 9:59 PM, Neil Puttock wrote: > > I'm on 64-bit and still get the same error.  The attached patch seems > > to fix the problem, though it leads to another issue: Valentin's > > original patch uses shopt, w

Re: 2.13.40 regtests

On Sun, 28 Nov 2010 21:10:03 -0800, Graham Percival wrote: les-nerides: this is definitely an improvement. I'm surprised to see that the old version involved a collision between fingering and a slur in different staves, though! (end of bar 2) Could somebody look into whether this is a known bu

Re: Position of cue clefs?

> I prefer to have the cue start clef always after the bar line, after > a key signature or meter, right before the first note of the cue. > It should be a small clef, and it should intentionally look > `artificial'. And it should be transposed to the instrument's transposition. I've seen untran

Re: Position of cue clefs?

Reinhold, I can only give my personal preferences here. > In particular, > > -) the cue start clef is sometimes before the barline, sometimes > after. (Typically, if a clef/key/time change is involved, the cue > clef comes after the barline, otherwise before the barline; But that > is not alwa

Re: 2.13.40 regtests

On Sat, Nov 27, 2010 at 11:32:57AM -, Phil Holmes wrote: > http://www.holmessoft.co.uk/homepage/lilypond/imagediffs.htm les-nerides: this is definitely an improvement. I'm surprised to see that the old version involved a collision betwee fingering and a slur in different staves, though! (end

Re: Add tab-tie-follow-engraver (issue2723043)

On 2010/11/28 22:24:05, Neil Puttock wrote: http://codereview.appspot.com/2723043/diff/109001/lily/tab-harmonic-engraver.cc#newcode59 lily/tab-harmonic-engraver.cc:59: victim->set_property ("style", ly_symbol2scm ("harmonic")); This makes it difficult for users to tweak the appearance of the

Position of cue clefs?

As you know from my previous patch (http://codereview.appspot.com/2726043), I'm working on clef support for cue notes. Unfortunately, I found out that all scores handle cue notes with clefs a little different, and I don't really know what the modern convention is. Does anyone have some deeper in

Re: GUB target_cpu error

On Sun, Nov 28, 2010 at 9:59 PM, Neil Puttock wrote: > I'm on 64-bit and still get the same error.  The attached patch seems > to fix the problem, though it leads to another issue: Valentin's > original patch uses shopt, which doesn't work with my default shell > command; If I do the following, T

Re: Add tab-tie-follow-engraver (issue2723043)

http://codereview.appspot.com/2723043/diff/109001/lily/tab-harmonic-engraver.cc File lily/tab-harmonic-engraver.cc (left): http://codereview.appspot.com/2723043/diff/109001/lily/tab-harmonic-engraver.cc#oldcode83 lily/tab-harmonic-engraver.cc:83: "HarmonicParenthesesItem ", This is never created

Re: GUB target_cpu error

On 27 November 2010 10:03, Graham Percival wrote: > I'd rather not simply revert it, since it seems like a good > feature.  How are you declaring target_cpu ?  Did you succeed in > building GUB from scratch?  if you can build it from scratch and I > can't, then there must be something weird about

Re: T1247 - Conditionally do (use-modules (ice-9 curried-definitions)) if running with Guile V2, (issue2219044)

Hi Ian, On 2010/11/25 15:56:26, ianhulin44 wrote: Another thought re the conditional (define-module) idea, if it's (if) making the guile compilation barf, we could try using (cond) or (cond-expand) instead. I just tried all of these options, and nothing seems to work. I'm pretty baffled. In

Re: Add tab-tie-follow-engraver (issue2723043)

Just some remarks about the harmonic detection. Regards, Marc http://codereview.appspot.com/2723043/diff/109001/scm/tablature.scm File scm/tablature.scm (right): http://codereview.appspot.com/2723043/diff/109001/scm/tablature.scm#newcode296 scm/tablature.scm:296: (harmonic (eq? (ly:grob-prope

Re: gettext status?

Le 28/11/2010 15:14, Carl Sorensen disait : On 11/28/10 7:08 AM, "Valentin Villenave" wrote: Hi Jean-Charles, greetings everybody, I've been working on a patch for fr.po but I have a few questions: - how do we register at the Translation Project? (actually, I'd prefer not to bother with it

Re: gettext status?

On 11/28/10 7:08 AM, "Valentin Villenave" wrote: > Hi Jean-Charles, greetings everybody, > > I've been working on a patch for fr.po but I have a few questions: > - how do we register at the Translation Project? (actually, I'd > prefer not to bother with it at all, I'd rather send you my patc

gettext status?

Hi Jean-Charles, greetings everybody, I've been working on a patch for fr.po but I have a few questions: - how do we register at the Translation Project? (actually, I'd prefer not to bother with it at all, I'd rather send you my patch and let you review it and upload it for me :) - I noticed tha

Re: Add harmonic by fret and by ratio to tablatures (issue3326042)

I forgot to mention that this patch applies on top of http://codereview.appspot.com/2723043/ Thanks, Carl http://codereview.appspot.com/3326042/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-d

Re: server down?

> I'm unable to ping git.sv.gnu.org since yesterday night (22:00 CET). > What's up, Duck? Savannah is still down, see http://identi.ca/group/fsfstatus Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/l

Re: server down?

* Jean-Charles Malahieude wrote on Sun, Nov 28, 2010 at 10:50:08AM CET: > I'm unable to ping git.sv.gnu.org since yesterday night (22:00 CET). > What's up, Duck? Savannah is down. See . Cheers, Ralf ___ lilypond-devel

server down?

Hi all, I'm unable to ping git.sv.gnu.org since yesterday night (22:00 CET). What's up, Duck? Cheers, Jean-Charles ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add harmonic by fret and by ratio to tablatures (issue3326042)

Am 28.11.2010 um 10:22 schrieb Marc Hohl: Am 28.11.2010 05:23, schrieb carl.d.soren...@gmail.com: Reviewers: marc, p.l.schmidt_gmx.de, Message: I've taken Marc's harmonic.ly and moved the scheme functions into scm/tablature.scm, the music functions into ly/engraver-init.ly, and the test mu

Re: [Patch:] Tablature: provide custom fret labels

Am 27.11.2010 21:12, schrieb Carl Sorensen: Marc, Do you have a regtest file that uses the custom fret label? Now I do ;-) Thanks, Marc >From a34ec51095cdc2f5e06e847c85fcd86b95ae7b1e Mon Sep 17 00:00:00 2001 From: Marc Hohl Date: Tue, 23 Nov 2010 21:18:25 +0100 Subject: [PATCH] tablatur

Re: Add harmonic by fret and by ratio to tablatures (issue3326042)

Am 28.11.2010 05:23, schrieb carl.d.soren...@gmail.com: Reviewers: marc, p.l.schmidt_gmx.de, Message: I've taken Marc's harmonic.ly and moved the scheme functions into scm/tablature.scm, the music functions into ly/engraver-init.ly, and the test music into input/regression/tablature-harmonic-fun

Re: Modify fret calculation algorithm (issue3320041)

Am 27.11.2010 21:19, schrieb Carl Sorensen: On 11/27/10 1:03 PM, "Marc Hohl" wrote: Am 27.11.2010 14:36, schrieb Carl Sorensen: [...] No, it's not a syntax error, any more than \time 4/4 c4 c c | is a syntax error. I'm fine to throw an error instead of a warning, so that the outp