Re: Using MSH Paris Nord server

> Message du 25/07/12 00:08 > De : "Trevor Daniels" > A : "Graham Percival" , "John Mandereau" > Copie à : "lilypond-devel" > Objet : Re: Using MSH Paris Nord server > > > Graham Percival wrote Tuesday, July 24, 2012 10:55 PM > > > grenouille.lilynet.net. > > I like it. Definitely better th

Re: Syntax change proposal:

Keith OHara writes: > David Kastrup gnu.org> writes: > >> One really ugly problem is interpreting things like "4.". Looks like a >> duration, but then we have >> input/regression/dynamics-broken-hairpin.ly: line-width = 4.\cm > > The parser chooses among (too) many different mod

Re: Syntax change proposal:

David Kastrup gnu.org> writes: > One really ugly problem is interpreting things like "4.". Looks like a > duration, but then we have > input/regression/dynamics-broken-hairpin.ly: line-width = 4.\cm The parser chooses among (too) many different modes ("start conditions") tellin

Re: GOP2-3 - GLISS or not

Graham Percival percival-music.ca> writes: > This is a > problem for projects such as mutopia – a large fraction of their > .ly files don’t compile with current lilypond. That means that > they can’t benefit from recent bugfixes; users wanting the sheet > music in a different size (say, printing

Re: Issue 2401 in lilypond: NR 1.2.4 - Not working snippet

> I proposed a patch for issue 2401 (see tracker). Now in codereview: http://codereview.appspot.com/6447043 got this message: WARNING: could not change issue labels; please email lilypond-devel with the issue number: 2401 Frédéric ___ lilypond-devel m

Re: GOP2-3 - GLISS or not

On Tue, Jul 24, 2012 at 3:09 AM, Graham Percival wrote: > Some “computer languages” are fairly stable. A TeX or C++ program > written 10 years ago will probably still compile with no > modifications (notwithstanding the g++ 4.3 header and namespace > changes). The same is not true of LilyPond; eve

PATCH: Countdown to 20120726

For 21:00 MDT Thursday July 26 Defect: Issue 2672 : Patch: Midi fixes - R 6420058 Issue 2691 : Chord names collide with beams (ver

Re: Issue 2653 in lilypond: Midi output does not respect tied notes

On Tue, Jul 17, 2012 at 12:07:29PM +0200, David Kastrup wrote: > Graham Percival writes: > > > On Tue, Jul 17, 2012 at 10:39:33AM +0200, David Kastrup wrote: > > > >> cranks out a list of 44 "Invalid" issues. According to the stated > >> policy, those should be marked "Verified" eventually. > >

Re: Using MSH Paris Nord server

Graham Percival wrote Tuesday, July 24, 2012 10:55 PM > grenouille.lilynet.net. I like it. Definitely better than crapaud which has an unfortunate connotation to English-speakers. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://

Re: Using MSH Paris Nord server

On Tue, Jul 24, 2012 at 10:26:14AM +0200, John Mandereau wrote: > Fine. As for the name of the server, it's called srv-lilypond in MSH > Paris Nord, but it's all right to use a different name on the internet, > what do you think of > > tadpole.lilynet.net I think tadpole. is nicer than toadunder

Re: push patch for issue 2679

On Tue, Jul 24, 2012 at 06:50:52PM +0200, David Kastrup wrote: > We don't commit anything other than patches. That's redundant. But > > Issue 2679: Function for overriding broken spanners > > would make it easier to find the corresponding issue in case one needs > to revisit the commit at one p

Re: push patch for issue 2679

David Nalesnik writes: > On Tue, Jul 24, 2012 at 12:57 PM, David Kastrup wrote: >> >> "Phil Holmes" writes: >> >> > BTW - apologies for top-posting and that, but my Windows email system >> > takes your mails as HTML and does this with them. >> >> His mails contain HTML and plain text as alterna

Re: Second set of volta changes (Issue 2673) (issue 6422061)

On 2012/07/24 19:40:35, email_philholmes.net wrote: - Original Message - From: To: ; ; Cc: ; Sent: Tuesday, July 24, 2012 8:15 PM Subject: Re: Second set of volta changes (Issue 2673) (i

Re: push patch for issue 2679

On Tue, Jul 24, 2012 at 12:57 PM, David Kastrup wrote: > > "Phil Holmes" writes: > > > BTW - apologies for top-posting and that, but my Windows email system > > takes your mails as HTML and does this with them. > > His mails contain HTML and plain text as alternatives, and Gnus (which I > use as

Re: Second set of volta changes (Issue 2673) (issue 6422061)

- Original Message - From: To: ; ; Cc: ; Sent: Tuesday, July 24, 2012 8:15 PM Subject: Re: Second set of volta changes (Issue 2673) (issue 6422061) http://codereview.appspot.com/6422061/diff/1/ly/engraver-init.ly File ly/engraver-init.ly (right): http://codereview.appspot.com/642

Re: Second set of volta changes (Issue 2673) (issue 6422061)

http://codereview.appspot.com/6422061/diff/1/ly/engraver-init.ly File ly/engraver-init.ly (right): http://codereview.appspot.com/6422061/diff/1/ly/engraver-init.ly#newcode621 ly/engraver-init.ly:621: ":|" "|:" "||:" "|." ":|:" ":|.|:" ":|.:" ".|" Trailing whitespace. http://codereview.appspot.c

Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface.

Am 24.07.2012 13:53, schrieb lilyp...@googlecode.com: Updates: Labels: -Patch-new Patch-review Comment #40 on issue 1320 by d...@gnu.org: Enhancement: user-customizable barlines through a Scheme interface. http://code.google.com/p/lilypond/issues/detail?id=1320#c40 Patchy the autobot says

Re: push patch for issue 2679

"Phil Holmes" writes: > BTW - apologies for top-posting and that, but my Windows email system > takes your mails as HTML and does this with them. His mails contain HTML and plain text as alternatives, and Gnus (which I use as my mail reader) lets me choose. In general, anything with code in it

Re: push patch for issue 2679

David Nalesnik writes: > I just tried to change the commit message as you said.  When I check > the amended patch, however, the subject line at the top of the file > is: > > Subject: [PATCH] Issue 2679: Function for overriding broken spanners > > Apparently, [PATCH] is added automatically when I

Re: push patch for issue 2679

BTW - apologies for top-posting and that, but my Windows email system takes your mails as HTML and does this with them. Anyway - you're now in master. -- Phil Holmes - Original Message - From: David Nalesnik To: Phil Holmes Cc: Graham Percival ; David Kastrup ; lilypond-deve

Re: push patch for issue 2679

Phil, On Tue, Jul 24, 2012 at 12:07 PM, Phil Holmes wrote: > ** > Pushed as > f7085cf9b2ff111b7d30c8a59e367c771a7e3c52. > Patchy is now running. > Thank you very much for doing this! -

Re: push patch for issue 2679

On Tue, Jul 24, 2012 at 12:05 PM, David Kastrup wrote: > David Nalesnik writes: > > > Arggh...sorry for making a hash of this :( > > By the way, you aren't. You are dealing with flexible and powerful > tools in action, and keeping up surprisingly well. That's the reason > nobody pipes up and s

Re: push patch for issue 2679

Pushed as f7085cf9b2ff111b7d30c8a59e367c771a7e3c52. Patchy is now running. -- Phil Holmes - Original Message - From: David Nalesnik To: Graham Percival Cc: Phil Holmes ; David Kastrup ; lilypond-devel@gnu.org Sent: Tuesday, July 24, 2012 5:37 PM Subject: Re: push patch f

Re: push patch for issue 2679

David, On Tue, Jul 24, 2012 at 11:50 AM, David Kastrup wrote: > David Nalesnik writes: > > > On Tue, Jul 24, 2012 at 11:34 AM, Graham Percival > > wrote: > > > > On Tue, Jul 24, 2012 at 05:26:01PM +0100, Phil Holmes wrote: > > > I'd be happy to push this, but would like a little advice

Re: push patch for issue 2679

David Nalesnik writes: > Arggh...sorry for making a hash of this :( By the way, you aren't. You are dealing with flexible and powerful tools in action, and keeping up surprisingly well. That's the reason nobody pipes up and says "I'll take it up from here and do all the rest, thank you", but r

Re: push patch for issue 2679

David Nalesnik writes: > On Tue, Jul 24, 2012 at 11:34 AM, Graham Percival > wrote: > > On Tue, Jul 24, 2012 at 05:26:01PM +0100, Phil Holmes wrote: > > I'd be happy to push this, but would like a little advice.  If I > > go to Rietveld and download the raw patch set, it comes withou

Re: GOP2-3 - GLISS or not

Nicolas Sceaux writes: > As a maintainer of 100+ Mbytes of LilyPond files, I'm very interested > in this topic. > > IMHO, we should aim at stabilizing what is currently hardcoded in the > lexer and parser (notes, file structure...). Nowadays, only David > works in this area, he has the best expe

Re: push patch for issue 2679

On Tue, Jul 24, 2012 at 11:34 AM, Graham Percival wrote: > On Tue, Jul 24, 2012 at 05:26:01PM +0100, Phil Holmes wrote: > > I'd be happy to push this, but would like a little advice. If I > > go to Rietveld and download the raw patch set, it comes without > > proper email addresses and formatting

Re: push patch for issue 2679

On Tue, Jul 24, 2012 at 05:26:01PM +0100, Phil Holmes wrote: > I'd be happy to push this, but would like a little advice. If I > go to Rietveld and download the raw patch set, it comes without > proper email addresses and formatting. This means to push stuff > from Rietveld, I have to git apply t

Re: push patch for issue 2679

"Phil Holmes" writes: > I'd be happy to push this, but would like a little advice.  If I go to > Rietveld and download the raw patch set, it comes without proper email > addresses and formatting.  This means to push stuff from Rietveld, I > have to git apply the diff, then manually update the aut

Re: push patch for issue 2679

I'd be happy to push this, but would like a little advice. If I go to Rietveld and download the raw patch set, it comes without proper email addresses and formatting. This means to push stuff from Rietveld, I have to git apply the diff, then manually update the author (assuming I remember). I

Re: GOP2-3 - GLISS or not

Le 24 juil. 2012 à 11:09, Graham Percival a écrit : > ** Stability or not? > > Stabilizing a language is a tricky process. If you do it too > early, then you’re stuck with whatever mistakes or poor design > decisions. If you do it too late, then there’s a large body of > documents in the pre-stab

Re: push patch for issue 2679

> OK, I succeeded in doing this and uploaded a new patch set. I'm going to > redo this now as I see I failed to delete two newlines... > > OK, all should be well now. Patch corrected. -David ___ lilypond-devel mailing list lilypond-devel@gnu.org https:

Re: push patch for issue 2679

David, > > > Is there any reason I can't manually remove the markers for the merge > > conflict, namely the lines: > > > > <<< HEAD > > > > === > > > Function for overriding broken spanners > > If the result is the intended result, sure. You are getting the merge > conflict beca

Re: push patch for issue 2679

David Nalesnik writes: > David, >   > > > > > > So, in this case, would I do something like: > > > > git pull -r > > > > then submit a new patch set? > > > That's probably the easiest way.  You'll likely get a merge > conflict > with instructions

Re: push patch for issue 2679

David, > > > > So, in this case, would I do something like: > > > > git pull -r > > > > then submit a new patch set? > > That's probably the easiest way. You'll likely get a merge conflict > with instructions. Personally, I use Emacs and > > M-x smerge-ediff RET > > on the problematic file(s) f

Instrument names

I'd like to look at fixing 766. Could someone suggest the best way to go about this, please? One option would seem to be to calculate the length of the text of the instrument names, and set the indent on the score equal to that plus a bit. Is this the best way? It seems to me that a system base

Re: push patch for issue 2679

David Nalesnik writes: > On Tue, Jul 24, 2012 at 8:56 AM, David Kastrup wrote: > > "Phil Holmes" writes: > > > I get the patch fails to apply - presumably because > > music-functions.scm has been updated twice since the patch was > > created?  Does this mean it needs rebasi

Re: GOP-PROP 2-1: LilyPond is part of GNU

Il giorno lun, 16/07/2012 alle 14.57 +0200, Federico Bruni ha scritto: > info manuals are only in english? > I can't see other languages in /usr/share/info > > both info and yelp show only the english version of the manual > how can I see another language? AFAIK there is no i18n design or support

Re: push patch for issue 2679

On Tue, Jul 24, 2012 at 8:56 AM, David Kastrup wrote: > "Phil Holmes" writes: > > > I get the patch fails to apply - presumably because > > music-functions.scm has been updated twice since the patch was > > created? Does this mean it needs rebasing, or somesuch? > > Likely. So, in this case,

Second set of volta changes (Issue 2673) (issue 6422061)

Reviewers: Ian Hulin (gmail), dak, Graham Percival, Message: Please review Description: The second set of proposed changes to volta syntax, posted on behalf of Arnold Theresius. Checked with make and make test. Please review this at http://codereview.appspot.com/6422061/ Affected files: M l

Re: push patch for issue 2679

"Phil Holmes" writes: > I get the patch fails to apply - presumably because > music-functions.scm has been updated twice since the patch was > created?  Does this mean it needs rebasing, or somesuch? Likely. -- David Kastrup ___ lilypond-devel mail

Re: push patch for issue 2679

I get the patch fails to apply - presumably because music-functions.scm has been updated twice since the patch was created? Does this mean it needs rebasing, or somesuch? -- Phil Holmes - Original Message - From: David Nalesnik To: Lilypond Dev Sent: Tuesday, July 24, 2012

push patch for issue 2679

Hi, I don't have push ability, so would someone who does please push my patch for issue 2679 ("Add function for overriding broken spanners to LilyPond") for me? Thanks so much, David ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.g

Re: GOP2-3 - GLISS or not

Francisco Vila writes: > Take this as the result of a quick reading of the summary. My comment > as a non-expert is that probably a good, reliably working convert-ly > is a substitute for syntax stability, because it is precisely what > will make your documents compile on the long term. convert-

Re: GOP2-3 - GLISS or not

Hi Graham, On 24/07/12 10:09, Graham Percival wrote: > > Hopefully we can settle those questions now. > http://lilypond.org/~graham/gop/gop_4.html > > > ** Summary > > Let’s decide whether to try to stabilize the syntax or not. What > type of project do we want LilyPond to be? What kinds of

Re: GOP2-3 - GLISS or not

On Tue, Jul 24, 2012 at 11:00:30AM +0100, Phil Holmes wrote: > Surely an alternative is to have an archive of stable version > installations? We have that already: http://lilypond.org/old-downloads.html > We could advise users who require that their work > will compile into the future to ensure i

Re: GOP2-3 - GLISS or not

On Tue, Jul 24, 2012 at 11:48:13AM +0200, Francisco Vila wrote: > Take this as the result of a quick reading of the summary. My comment > as a non-expert is that probably a good, reliably working convert-ly > is a substitute for syntax stability, I disagree. For one thing it is often very difficul

Re: GOP2-3 - GLISS or not

- Original Message - From: "Francisco Vila" To: "Graham Percival" Cc: Sent: Tuesday, July 24, 2012 10:48 AM Subject: Re: GOP2-3 - GLISS or not Take this as the result of a quick reading of the summary. My comment as a non-expert is that probably a good, reliably working convert-ly i

Re: GOP2-3 - GLISS or not

Take this as the result of a quick reading of the summary. My comment as a non-expert is that probably a good, reliably working convert-ly is a substitute for syntax stability, because it is precisely what will make your documents compile on the long term. Your personal, misfortunate case would not

Re: Issue 1320: Scheme bar line interface (issue 6305115)

Am 23.07.2012 23:45, schrieb k-ohara5...@oco.net: Looks like LilyPond defines two line-thicknesses, one for staff-line thickness in each StaffSymbol, and one (confusingly called staffline in C) for bar-line width in paper.scm. Thanks for your explanation! Indeed, staffline is not the best variab

GOP2-3 - GLISS or not

This summer hasn't been going as I'd hoped -- heh, who am I kidding, this whole year hasn't been going as I'd hoped. Anyway, we seem to have radically different concepts of what "input stabilization" might mean, or even if it's a good idea worth doing. Hopefully we can settle those questions now.

Re: Volta enhancements tranche 1 (issue 6398055)

- Original Message - From: "ArnoldTheresius" To: Now the qestion: I my original intent »@funindex \inStaffSegno« better than the »@cindex \inStaffSegno« I mentioned in my last mail? ArnoldTheresius I believe the answer is here: http://lilypond.org/doc/v2.15/Documentation/contribu

Re: Using MSH Paris Nord server

Il giorno lun, 23/07/2012 alle 20.42 +0100, Graham Percival ha scritto: > On Mon, Jul 23, 2012 at 06:42:15PM +0200, John Mandereau wrote: > > and we'd need A and DNS records for something like > > builder.lilypond.org or builder.lilynet.net to make the machine > > reachable more easily than ju

Re: Fwd: error while running make check (g++ 4.7.0): missing include of unistd.h

Frédéric Bron writes: >> A description of the issue. For new issues, this is usually filled in >> with the commit message(s) automatically. > > OK, I did it but failed when asking for : > Could not find stored credentials > /home/fred/.lilypond-project-hosting-login > Please enter login detail