Re: Lilypond error behaviour

Andrew Bernard writes: > If you look at the MWE example I provided to illustrate what I believe > is misleading information about a ‘FATAL’ error, then it has plain > text which it ignores, claims a fatal error and proceeds to make a > perfectly good PDF. LilyPond wouldn't know that, and in any

Re: Tuplet number direction

David Wright writes: > On Fri 15 Apr 2016 at 10:23:55 (+0200), David Kastrup wrote: >> >> Which would usually involve triplet brackets rather than hacking this >> into partial note values at measure boundaries. Which is how it was >> done in the score I have been singing this from. > > Surely o

Re: Lilypond error behaviour

Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : >Andrew Bernard writes: > >> If you look at the MWE example I provided to illustrate what I >believe >> is misleading information about a ‘FATAL’ error, then it has plain >> text which it ignores, claims a fatal error and proceeds to make

Re: Lilypond error behaviour

Urs Liska writes: > Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : > >>A warning is appropriate for something which is not an error: namely >>LilyPond has a well-specified task but the results will not likely >>make sense. LilyPond does not return an error code for a warning. > > Well,

Re: Lilypond error behaviour

Am 17. April 2016 10:51:34 MESZ, schrieb David Kastrup : >Urs Liska writes: > >> Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : >> >>>A warning is appropriate for something which is not an error: namely >>>LilyPond has a well-specified task but the results will not likely >>>make sense

score as footnote/footer

It is sometimes the case in an etude book that a model of the etude showing a different general rhythm or articulation pattern will be given at the bottom of a page. Typically, the model will be only one or a very few measures in a smaller size, centered at the bottom of the page. Is this poss

Re: score as footnote/footer

Am 17. April 2016 11:28:23 MESZ, schrieb "bobr...@centrum.is" : >It is sometimes the case in an etude book that a model of the etude >showing a different general rhythm or articulation pattern will be >given at the bottom of a page. Typically, the model will be only one >or a very few measures

Re: Lilypond error behaviour

Urs Liska writes: > Am 17. April 2016 10:51:34 MESZ, schrieb David Kastrup : >>Urs Liska writes: >> >>> Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : >>> A warning is appropriate for something which is not an error: namely LilyPond has a well-specified task but the results wil

Re: Lilypond error behaviour

On 17.04.2016 04:29, David Wright wrote: As to lilypond making a best effort at producing output, I have never seen this referred to in the NR. That ought to go in somewhere. Um, the purpose of LP is to produce output (lilypond.org line 1).

Re: score as footnote/footer

Hi David, Try: \version "2.19.39" \header { title = "Scores as footnotes" } \markup { \null \footnote \null \concat { "*" \hspace #1.5 \score { \relative { c'8 d e f g a b c} \layout { indent = 0 } } } \null \footnote \null \concat {

Re: score as footnote/footer

Urs Liska writes: > Am 17. April 2016 11:28:23 MESZ, schrieb "bobr...@centrum.is" > : >>It is sometimes the case in an etude book that a model of the etude >>showing a different general rhythm or articulation pattern will be >>given at the bottom of a page. Typically, the model will be only one

Re: Lilypond error behaviour

I now understand, which I had not previously, that lilypond will make its best effort to continue at all times, and this is a core value of the design philosophy – thanks Simon for pointing this out. But nobody has been able to explain to me how classing the error in question as fatal and then g

Re: score as footnote/footer

Thanks for the responses. The score-in-copyright idea does precisely what I want; it's centered at the bottom of the first and only the first page of a score. \version "2.18.0" models = \relative c' { c4-( d-) e-( f-) \bar "||" c4. d8 e4. f8 } \layout {} tune = \relativ

Re: Lilypond error behaviour

Am 17.04.2016 um 12:33 schrieb David Kastrup: > Urs Liska writes: > >> Am 17. April 2016 10:51:34 MESZ, schrieb David Kastrup : >>> Urs Liska writes: >>> Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : > A warning is appropriate for something which is not an error: namely

Re: Lilypond error behaviour

Am 17.04.2016 um 04:29 schrieb David Wright: > I think a better analogy than compilers writing programs would be > browsers rendering web pages. Can you imagine a WWW where malformed > pages produced a few error messages on the screen and nothing else? > No, we expect the browser to make its best

Re: Lilypond error behaviour

On Sun, 17 Apr 2016, Urs Liska wrote: > No, of course not. If LilyPond is able to "recover" (as Andrew put it) it > should of course do so. But it should not report a "fatal error" and a > "failed file" then. I think the whole thing comes down to something very simple which ought to go without say

Re: Lilypond error behaviour

Urs Liska writes: > Am 17.04.2016 um 12:33 schrieb David Kastrup: >> Urs Liska writes: >> >>> Am 17. April 2016 10:51:34 MESZ, schrieb David Kastrup : Urs Liska writes: > Am 17. April 2016 08:20:52 MESZ, schrieb David Kastrup : > >> A warning is appropriate for something w

Re: Lilypond error behaviour

2016-04-17 13:59 GMT+02:00 : > On Sun, 17 Apr 2016, Urs Liska wrote: >> No, of course not. If LilyPond is able to "recover" (as Andrew put it) it >> should of course do so. But it should not report a "fatal error" and a >> "failed file" then. > > I think the whole thing comes down to something ver

Re: Lilypond error behaviour

Hi all, On Apr 17, 2016, at 8:15 AM, David Kastrup wrote: > why can one now consider LilyPond as having succeeded in compiling the file? If no final output file (e.g., PDF) exists before compilation begins, a final output file does exist after compilation ends, most users would understand the

Re: Lilypond error behaviour

Kieren MacMillan writes: > That being said, if (as in David K’s example) one or more > sub-compilations fails “fatally” — in other words, it would have > resulted in no meaningful/useful/concrete/verifiable output if it were > the sole compilation task — then the log should reflect that in some >

Re: Lilypond error behaviour

Hi David, > Except that the premise of this thread was that users […] > want to be able to deduce the presence of errors from the existence of output > files. Ah… sorry, I didn’t get that that was the premise. > So it pretty much doesn't matter what we write on the console: it's not > acceptabl

Re:Lilypond error behaviour

The errors that I frequently make show up as an additional empty stave or a ridiculously over long bar that runs off the page. This alerts me to an error but I have to search for it and they can be be very simple typos. Error messages in the log may also be a later result of the error rather than

Re: score as footnote/footer

hey, maybe a bit late, but I've done this in footnotes in the past. There was one issue though, footnotes are placed on top of each other like: 1. one score here 2. second score here. 3. third score here. What I needed back then was footnotes next to each other like: 1. one score here. 2. secon

Re: Lilypond error behaviour

Am 17.04.2016 um 16:49 schrieb Kieren MacMillan: >> Except that the premise of this thread was that users […] >> > want to be able to deduce the presence of errors from the existence of >> > output files. > Ah… sorry, I didn’t get that that was the premise. I don't think so. To me it seems quit

Turn moving of objects into code

Hi, there was a discussion some time ago about graphical adjustments that are translated into ly code; e.g. to move or shape slurs in svg and get the numbers in your ly file as a Frescobaldi feature. Something similar seems to be achieved for css: https://bugzilla.mozilla.org/show_bug.cgi?id=1139

Re: Lilypond error behaviour

> Except that the premise of this thread was that users refuse to look > _at_ _all_ at _any_ messages or error status and instead want to be able > to deduce the presence of errors from the existence of output files. > So it pretty much doesn't matter what we write on the console: it's not > accep

Re: Lilypond error behaviour

Noeck writes: > These two are often similar but not always. > IMHO, it would make sense to consider both and have 3 categories: > - warning: user, please look at this > - error: this is severe, there is something definitely wrong, but > Lilypond did its very best to keep running > - fatal error

Re: score as footnote/footer

bart deruyter writes: > hey, > > maybe a bit late, but I've done this in footnotes in the past. There was > one issue though, footnotes are placed on top of each other like: > > 1. one score here > 2. second score here. > 3. third score here. > > What I needed back then was footnotes next to each

Re: Lilypond error behaviour

Sharon Rosner writes: >> Except that the premise of this thread was that users refuse to look >> _at_ _all_ at _any_ messages or error status and instead want to be able >> to deduce the presence of errors from the existence of output files. > >> So it pretty much doesn't matter what we write on

Re: Lilypond error behaviour

> On Apr 17, 2016, at 3:16 PM, David Kastrup wrote: > > Noeck writes: > >> These two are often similar but not always. >> IMHO, it would make sense to consider both and have 3 categories: >> - warning: user, please look at this >> - error: this is severe, there is something definitely wrong,

Re: Lilypond error behaviour

2016-04-17 21:01 GMT+02:00 Noeck : > IMHO, it would make sense to [...] have 3 categories: > - warning: user, please look at this > - error: this is severe, there is something definitely wrong, but > Lilypond did its very best to keep running > - fatal error: this is severe and Lilypond could no

Re: score as footnote/footer

You could also do something like this \version "2.18.2" \header { title = "FootNote" tagline = "FootNote" } %%% footOne = \markup { %% space \vspace #2 % \hspace #1 \dir-column { %% \vspace #0 \concat { "*" \hspace #1.5 \score { \relat

Re: Lilypond error behaviour

2016-04-18 1:26 GMT+02:00 Thomas Morley : > 2016-04-17 21:01 GMT+02:00 Noeck : > >> IMHO, it would make sense to [...] have 3 categories: >> - warning: user, please look at this >> - error: this is severe, there is something definitely wrong, but >> Lilypond did its very best to keep running >> -