Re: [frogs] indenting scheme code

On Wed, Aug 3, 2011 at 7:22 AM, Graham Percival wrote: > Anybody interested in writing / modifying a scheme script to > indent scheme files?  This is a much easier problem than C++ code. No trolling intended (and I know this has been extensively discussed before), but doesn't GNU Emacs do an exce

Re: Lilynet down?

On Sun, Jul 31, 2011 at 9:42 PM, James Lowe wrote: > Sunday evening...I am guessing this is routine maintenance. Wow, I was doubting anyone would notice. Sorry for the downtime folks, I have migrated everything to a new server and (most importantly) I'm setting up the new Mutopia forge, which tur

Re: Remove special case in staff-spacing (issue4188051)

On 2011/08/02 21:29:24, Janek Warchol wrote: It does the things i hoped for for ages :) It merely restores the spacing rules LilyPond had through version 2.10.20 or so. See almost anything on mutopiaproject, I also see some differ

Re: [frogs] indenting scheme code

On Wed, Aug 03, 2011 at 09:04:55AM +0200, Valentin Villenave wrote: > On Wed, Aug 3, 2011 at 7:22 AM, Graham Percival > wrote: > > Anybody interested in writing / modifying a scheme script to > > indent scheme files?  This is a much easier problem than C++ code. > > No trolling intended (and I kn

Re: [frogs] indenting scheme code

Valentin Villenave writes: > On Wed, Aug 3, 2011 at 7:22 AM, Graham Percival > wrote: >> Anybody interested in writing / modifying a scheme script to >> indent scheme files?  This is a much easier problem than C++ code. > > No trolling intended (and I know this has been extensively discussed > b

Re: [frogs] indenting scheme code

On Wed, Aug 3, 2011 at 9:28 AM, David Kastrup wrote: > Not all that impressive when we are talking mixed Lily/Scheme files.  On > pure Scheme, things work better. Indeed. That's what I was referring to. When it comes to mixed scm/ly code, I think Frescobaldi has the smartest auto-indenter I've se

Dealing with nested properties.

What is the general feeling about override/revert with nested properties? The current implementation for property list of grob properties maintains a data structure suitable for lazy updates of the spine of the grob property list. However, overrides for nested properties duplicate part of the _l

RE: Dealing with nested properties.

Hello, )-Original Message- )From: lilypond-devel-bounces+james.lowe=datacore@gnu.org )[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On )Behalf Of David Kastrup )Sent: 03 August 2011 11:08 )To: lilypond-devel@gnu.org )Subject: Dealing with nested properties. ) ) )What

Re: Dealing with nested properties.

James Lowe writes: > You already know that I am not capable of giving you the technical > answer you want, but as a 'joe user' having to list a dozen individual > overrides in my layout block or within the music itself is very > tedious. > But taking a specific and easy to get, example, I have i

Re: auto numbering footnote checkin doesn't play with \null and \musicglyph

Am Monday 01 August 2011, 23:59:22 schrieben Sie: > On Aug 1, 2011, at 12:12 PM, Reinhold Kainhofer wrote: > > Why can't we have both auto-numbered and unnumbered footnotes at the same > > time? > > This is doable, but let's say that a user did. > > \autoFootnoteGrob #'NoteHead #'(1 . 1) "bar" a1

Re: [frogs] indenting scheme code

>>> Anybody interested in writing / modifying a scheme script to >>> indent scheme files?  This is a much easier problem than C++ code. >> >> No trolling intended (and I know this has been extensively >> discussed before), but doesn't GNU Emacs do an excellent job at it? > > Not all that impressiv

Re: auto numbering footnote checkin doesn't play with \null and \musicglyph

Am Mittwoch, 3. August 2011, 16:39:59 schrieben Sie: > > An example of some undesired ordering is the other example I sent a > > few days > > ago. The first system is utterly messed up (maybe a bug), but there > > are also > > other "issues": The hairpin gets the footnote printed at the right > > e

make test-clean test segfaults on master

Hi, the regtests bomb out with a segfault right now for me. Running lilypond...GNU LilyPond 2.15.9 Segmentation fault (core dumped) command failed: /usr/local/tmp/lilypond/out/bin/lilypond -I ./ -I ./out-test -I ../../input -I /usr/local/tmp/lilypond/Documentation -I /usr/local/tmp/lilypond/Do

Re: make test-clean test segfaults on master

On Wed, Aug 03, 2011 at 07:38:07PM +0200, David Kastrup wrote: > > /Documentation/snippets" -I "/usr/local/tmp/lilypond/input/regression" -I > "/usr/local/tmp/lilypond/Documentation/included" -I > "/usr/local/tmp/lilypond/mf/out" -I "/usr/local/tmp/lilypond/mf/out" -I > "/usr/local/t

Re: make test-clean test segfaults on master

Graham Percival writes: > On Wed, Aug 03, 2011 at 07:38:07PM +0200, David Kastrup wrote: >> >> /Documentation/snippets" -I >> "/usr/local/tmp/lilypond/input/regression" -I >> "/usr/local/tmp/lilypond/Documentation/included" -I >> "/usr/local/tmp/lilypond/mf/out" -I "/usr/local/tmp/lilypond/mf/o

Re: make test-clean test segfaults on master

On Wed, Aug 03, 2011 at 07:55:38PM +0200, David Kastrup wrote: > dak@lola:/usr/local/tmp/lilypond/out/lybook-testdb$ for i in `cat > /usr/local/tmp/lilypond/out/lybook-testdb/snippet-names--1980013010.ly`;do > ../bin/lilypond $i || { echo $i; break; } ;done Cute! > Renaming input to: `tie-direc

Re: make test-clean test segfaults on master

Graham Percival writes: > On Wed, Aug 03, 2011 at 07:55:38PM +0200, David Kastrup wrote: >> dak@lola:/usr/local/tmp/lilypond/out/lybook-testdb$ for i in `cat >> /usr/local/tmp/lilypond/out/lybook-testdb/snippet-names--1980013010.ly`;do >> ../bin/lilypond $i || { echo $i; break; } ;done > > Cute!

test macosx 10.7 binaries

Get them here: http://lilypond.org/~graham/ Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Fix for Issue 620. (issue4814041)

cannot apply to master due to fixcc. http://codereview.appspot.com/4814041/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: modifying default behaviour of tremolo slashes (issue4636081)

cannot apply to master due to fixcc. http://codereview.appspot.com/4636081/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: New engraver for braces (issue4807053)

sorry, unforutnately this patch cannot be applied to git master due to fixcc. http://codereview.appspot.com/4807053/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG (issue4822055)

awesome work, I really love this. Unfortunately it cannot apply directly to git master due to fixcc. http://codereview.appspot.com/4822055/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: print transposed guitar chords on piano sheets (issue4626094)

patch fails due to fixcc. http://codereview.appspot.com/4626094/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES: 48-hour countdown for subvoice queues, breve vertical lines, staff-spacing, and notation appendix

Friday, 1pm PST. Fix 1214: cueDuring and quoteDuring should also quote voices that create subvoices http://codereview.appspot.com/4816044/ font: change breve vertical lines http://codereview.appspot.com/4748044 Remove special case in staff-spacing http://codereview.appspot.com/4188051/ Add N

Re: Add Notation appendix for context mod identifiers. (issue4794057)

LGTM, fantastic work as always. http://codereview.appspot.com/4794057/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

New French PO file for 'lilypond' (version 2.15.9)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the French team of translators. The file is available at: http://translationproject.org/latest/lilypond/fr.po (We can arrange things so that

GOP-PROP 7: Developers as resources (probable decision)

nothing to see here, move along... http://lilypond.org/~graham/gop/gop_7.html ** Proposal summary We shall treat developers (and contributors) as Independent volunteers: each person does whatever they want, whenever they want. We have busy careers and lives; we make no expectations of action fro

Re: modifying default behaviour of tremolo slashes (issue4636081)

Oh no! I hoped to get it on this countdown. A version compatible with fixcc uploaded. http://codereview.appspot.com/4636081/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: print transposed guitar chords on piano sheets (issue4626094)

This patch is obsolete. Current patch is here http://codereview.appspot.com/4800051/ and it is compatible with fixcc. My bad... I should've closed this issue and sent a note. http://codereview.appspot.com/4626094/ ___ lilypond-devel mailing list lilyp

Re: PATCHES: 48-hour countdown for subvoice queues, breve vertical lines, staff-spacing, and notation appendix

2011/8/3 Graham Percival : > Friday, 1pm PST. > > > Fix 1214: cueDuring and quoteDuring should also quote voices that > create subvoices > http://codereview.appspot.com/4816044/ > > font: change breve vertical lines > http://codereview.appspot.com/4748044 > > Remove special case in staff-spacing >

Re: GOP-PROP 8: issue priorities

On Tue, Aug 02, 2011 at 10:37:18AM +0200, David Kastrup wrote: > Actually, I read this first as "bugs in undocumented features can't have > high priority", carrying the message "if you don't document your new > feature, we refuse to make fixing problems with it a high priority". I wasn't going for

Re: GOP-PROP 8: issue priorities

On Tue, Aug 02, 2011 at 07:48:12AM +, Keith OHara wrote: > I'm curious first what we want the "priority" field to mean. > > Probably we do not mean literally the priority with which contributors will > give attention to the bugs, because contributors are volunteers driven by > individual int

Re: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG (issue4822055)

On Sat, Jul 30, 2011 at 2:42 PM, Reinhold Kainhofer wrote: > Am Samstag, 30. Juli 2011, 18:28:32 schrieben Sie: >> overall commment: the parts that do the reporting should not need to >> know about the format of loglevel. > > Which parts exactly do you mean? Those that call the error/message/warni

Re: GOP-PROP 8: issue priorities

On 2 August 2011 10:28, Phil Holmes wrote: > > So any bug in Lily that produces bad output can never be High? Or - to put > it another way, we, the developers ,only regard bugs as high when they > hinder us, not when they make you, the user's life difficult. I don't like > that. I remain of the