Re: [PATCH] Fix crash when output-preview-framework is missing

On Wed, May 27, 2009 at 6:04 PM, Patrick McCarty wrote: > Hello, > > This patch fixes a crash that occurs when the specified backend does > not have an output-preview-framework (used for -dpreview). > > I also added a similar check for output-framework just in case a user > tries to add a new back

[PATCH] Fix compile for GCC 4.4

Hello, I need the attached patch to compile LilyPond. It looks like a C vs. C++ issue: http://www.cplusplus.com/reference/clibrary/cstring/strchr/ Interestingly, Arch Linux is currently using a snapshot of GCC, so this compiler improvement must have landed post-GCC 4.4. Thanks, Patrick From 7c2

Re: DOCS: revising LM "Score and Parts"

Jonathan Kulp Wednesday, May 27, 2009 7:13 PM Ok I think this makefile and the linux version are about ready for the docs. Trevor, do you think it's logical to put this topic in the vicinity of "Score and Parts" or handling large projects? For the moment I'll just write the texinfo source f

Re: better error msg for ambiguous (de)crescendo?

> Here are my candidates: > "warning: impossible or ambiguous (de)crescendo." > "warning: impossible or ambiguous (de)crescendo (MIDI)." > "warning: ignoring impossible or ambiguous (de)crescendo." > "warning: ignoring impossible or ambiguous (de)crescendo (MIDI)." > "warning: MIDI found

Re: better error msg for ambiguous (de)crescendo?

Hi Mark, Werner The most important thing about these errors is that they can _always_ be traced back to a source line so is it possible to word the error something like: warning: lilypond cannot interpret a (de)crescendo. MIDI output ignoring (de)crescendo starting at line . This wa

[PATCH]: Tablature support

I've posted Marc Hohl's excellent work on improved tab support on rietveld for your review. Please review the patch, located at Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.g

Re: better error msg for ambiguous (de)crescendo?

> warning: lilypond cannot interpret a (de)crescendo. > MIDI output ignoring (de)crescendo starting at line . > > This way the diagnostic states why Lily can't do what the user has > coded, what it's doing as a result, and the consequences of the > error condition detected. This is not

Re: better error msg for ambiguous (de)crescendo?

Hi Werner, Werner LEMBERG wrote: warning: lilypond cannot interpret a (de)crescendo. MIDI output ignoring (de)crescendo starting at line . This way the diagnostic states why Lily can't do what the user has coded, what it's doing as a result, and the consequences of the error condition

Re: [PATCH] (was: Re: suspicious break-align values)

2009/5/28 Mark Polesky : > okay. Thanks, applied. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: better error msg for ambiguous (de)crescendo?

Ian Hulin wrote: > What makes the (de)crescendo as coded impossible or ambiguous? I agree, we > need > to be as precise as possible, but we need to also give the user as big a > steer > as we can towards sorting the problem. See http://lists.gnu.org/archive/html/lilypond-user/2008-11/msg0024

Re: [PATCH] Fix crash when output-preview-framework is missing

2009/5/28 Patrick McCarty : > Attached is a revised patch. That was quick. :) LGTM. + warning (_f ("the `%s' backend does not support -dprint-pages", +get_output_backend_name ())); + warning (_f ("the `%s' backend does not support -dpreview", +

Re: [PATCH] Fix crash when output-preview-framework is missing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 28. Mai 2009 22:18:23 schrieb Neil Puttock: > + warning (_f ("the `%s' backend does not support -dprint-pages", > + get_output_backend_name ())); > > + warning (_f ("the `%s' backend does not support -dpreview",

Re: where to put useful lists in the docs?

2009/5/25 Mark Polesky : > Here's a proposal: > > Here are two generic functions that could be incorporated into IR > 4 "Scheme functions" (though if C++ is required, someone else > would have to help). C++ would be required, though these aren't suitable candidates for export since they don't do

Re: two patches

Carl D. Sorensen a écrit : So, in this particular case, changing Lilypond to LilyPond qualifies as a simple text subtitution, I guess? Yes. My confusion came from not understanding that the proposed patch constituted "General maintenance." All historical developers and contributors have n

Re: [PATCH] Fix compile for GCC 4.4

On Thu, May 28, 2009 at 01:00:14AM -0700, Patrick McCarty wrote: > Hello, > > I need the attached patch to compile LilyPond. On second thought, please ignore this patch for now. Even though I currently need it, I doubt very many distributions are updating GCC until 4.4.1 comes out, because of al

Re: [PATCH] Fix crash when output-preview-framework is missing

On Thu, May 28, 2009 at 10:46:11PM +0200, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Donnerstag, 28. Mai 2009 22:18:23 schrieb Neil Puttock: > > + warning (_f ("the `%s' backend does not support -dprint-pages", > > +get_output_backend_name

Re: [PATCH] Fix crash when output-preview-framework is missing

On Thu, May 28, 2009 at 4:45 PM, Patrick McCarty wrote: > On Thu, May 28, 2009 at 10:46:11PM +0200, Reinhold Kainhofer wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Am Donnerstag, 28. Mai 2009 22:18:23 schrieb Neil Puttock: >> > +   warning (_f ("the `%s' backend does not suppor

what happened to lilypond.git/summary at gnu.org?

Umm... what's going on? All of a sudden lilypond's entire history goes back all of 8 hours... http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=summary - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/ma

Re: what happened to lilypond.git/summary at gnu.org?

looks like a glitch with the savannah server. On Fri, May 29, 2009 at 1:08 AM, Mark Polesky wrote: > > Umm... what's going on? All of a sudden lilypond's > entire history goes back all of 8 hours... > > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=summary > > - Mark > > > > > > >

Re: [PATCH] Fix compile for GCC 4.4

On Thu, May 28, 2009 at 4:19 PM, Patrick McCarty wrote: > On Thu, May 28, 2009 at 01:00:14AM -0700, Patrick McCarty wrote: >> Hello, >> >> I need the attached patch to compile LilyPond. > > On second thought, please ignore this patch for now.  Even though I > currently need it, I doubt very many d

Re: where to put useful lists in the docs?

Neil Puttock wrote: > A much more suitable home would be lily-library.scm, but you'd > need to document them manually as Graham suggests. Oh my gosh, why was I never told about lily-library.scm before? That is one of the most useful little files I've seen in a while. Is it mentioned in the docs?