Re: Lilypond error behaviour

Thomas Morley writes: > Anyone, with an example for an _immediate_ abort? toplevel-score-handler = "bad" \score { { c1 } \layout { } } #(display "not reached") -- David Kastrup ___ lilypond-user mailing list

Re: Lilypond error behaviour

2016-04-19 23:28 GMT+02:00 David Kastrup : > Thomas Morley writes: > >>> just turn on >>> warning-as-error and be done with it. >> >> As I wrote days ago ... > > We could implement an option for the maximum number of non-fatal errors > before abort. People

Re: Lilypond error behaviour

Hi Martin, > Doesn't anyone think this is a ridiculously long thread for such a minor > problem? 1. Your post answers your own question, doesn’t it? ;) 2. cf. David K’s mention of “bike-shedding” (which, I have to admit, I didn’t know about until I searched it on the web). Best, Kieren.

Re: Termination of variable definitions

Thomas Morley writes: > Well, LilyPond uses an input-language, I don't think it qualifies as a > programming-language. > But you you can do a lot > > xx = \override NoteHead.color = #red > is one expression > yy = \override NoteHead.font-size = #5 > is one

Re: Lilypond error behaviour

Sharon Rosner writes: >> More exactly, LilyPond's task is to read a LilyPond input file and >> process its contained expression according to the setting of hook >> variables (those may do something other than typesetting, for example >> converting to a MusicXML expression and

Re: Termination of variable definitions

2016-04-19 23:25 GMT+02:00 David Sumbler : > Thank you all for your help on this. > > My original question, "how does Lilypond recognize the end of the > definition of a variable" has been answered: the definition has to be a > single, complete expression. > > Which of course

Re: Contemporary glissando breaks bar-checking

> On 19 Apr 2016, at 19:45, Malte Meyn wrote: > > > > Am 19.04.2016 um 19:41 schrieb Michael Hendry: >> I’ve returned to a file I created under version 2.14.0 >> >> […] and I get bar-check warnings and unsatisfactory layout. >> > > The \cadenzaOn and \cadenzaOff

Re: Lilypond error behaviour

> It would be a little less futile, if people would try harder to read > and to understand what was written and think about it. > Really no reason for a flame-war. That was not my intention, and I tried really hard to think about this problem. Call me slow :-) Sharon

Re: Lilypond error behaviour

> More exactly, LilyPond's task is to read a LilyPond input file and > process its contained expression according to the setting of hook > variables (those may do something other than typesetting, for example > converting to a MusicXML expression and writing it out again). Some > processing may

Re: Lilypond error behaviour

Thomas Morley writes: >> just turn on >> warning-as-error and be done with it. > > As I wrote days ago ... We could implement an option for the maximum number of non-fatal errors before abort. People who really do not want to have LilyPond continue after an error can

Re: Termination of variable definitions

Thank you all for your help on this. My original question, "how does Lilypond recognize the end of the definition of a variable" has been answered: the definition has to be a single, complete expression. Which of course produces another question: "what is classed as a single expression?" Well,

Re: Lilypond error behaviour

Doesn't anyone think this is a ridiculously long thread for such a minor problem? -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Lilypond error behaviour

Sharon Rosner writes: >> What's wrong with the exit code? I thought people rather complained >> about the error message. > > For the given examples, the non-zero exit code signifies failure, when > lilypond has actually completed its task - generating a PDF - > successfully.

Re: Lilypond error behaviour

2016-04-19 22:41 GMT+02:00 Sharon Rosner : >> Now it appears that there are people who want to change that >> because they want to add some sort of post-processing by machine >> (embedding LP in Makefiles, or into a server), or even just the >> imposition of some tidier design

Re: Lilypond error behaviour

> What's wrong with the exit code? I thought people rather complained > about the error message. For the given examples, the non-zero exit code signifies failure, when lilypond has actually completed its task - generating a PDF - successfully. And this goes hand in hand with the misleading

Re: Lilypond error behaviour

Sharon Rosner writes: >> Now it appears that there are people who want to change that >> because they want to add some sort of post-processing by machine >> (embedding LP in Makefiles, or into a server), or even just the >> imposition of some tidier design principle that has

Re: Termination of variable definitions

David Wright writes: > violin = \new Voice b > you can substitute again, this time for "b". > (Within limits: contexts have a parent/child ordering, so Staff > can contain Voice but not vice versa.) Semantically not, but syntactically this is not a problem: \relative

Re: Termination of variable definitions

http://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00465.html > ... But it's recursive. what does that mean? - J.W. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Termination of variable definitions

2016-04-19 21:31 GMT+02:00 David Sumbler : > On Tue, 2016-04-19 at 20:51 +0200, David Kastrup wrote: >> David Sumbler writes: >> >> > In starting to experiment with selective compilation using includes >> > and/or the $(if condition action) structure

Re: Lilypond error behaviour

> Now it appears that there are people who want to change that > because they want to add some sort of post-processing by machine > (embedding LP in Makefiles, or into a server), or even just the > imposition of some tidier design principle that has nothing > to do with printing music. Lilypond's

Re: Termination of variable definitions

On Tue 19 Apr 2016 at 19:38:14 (+0100), David Sumbler wrote: > So at the risk of embarrassing myself, I should be grateful if somebody > would explain the following: how does Lilypond recognize the end of a > variable definition? Oversimplifying, there are about four things you can define with a

Re: Termination of variable definitions

David Sumbler writes: > On Tue, 2016-04-19 at 20:51 +0200, David Kastrup wrote: >> David Sumbler writes: >> >> > In starting to experiment with selective compilation using includes >> > and/or the $(if condition action) structure provided by David

Re: Termination of variable definitions

On Tue, 2016-04-19 at 20:51 +0200, David Kastrup wrote: > David Sumbler writes: > > > In starting to experiment with selective compilation using includes > > and/or the $(if condition action) structure provided by David Kastrup, I > > found that there is something very, very

Re: Lilypond error behaviour

Stephan Neuhaus writes: > On 2016-04-19 17:54, Tim Reeves wrote: >> Maybe they should be called "mortally-wounding" errors? :) > > This is an excellent suggestion. Perhaps we could implement that further > output from Lilypond becomes more and more incoherent as the poison

Re: Termination of variable definitions

David Sumbler writes: > In starting to experiment with selective compilation using includes > and/or the $(if condition action) structure provided by David Kastrup, I > found that there is something very, very basic that I have never really > understood. > > So at the risk of

Re: Lilypond error behaviour

On Tue 19 Apr 2016 at 13:22:50 (+0200), Stephan Neuhaus wrote: > On 2016-04-18 20:29, David Wright wrote: > >That begs the question. How do you define "clearly malformed input." > >If it is malformed, it can't be clear. > > > >Of course, if you mean "clearly-malformed", then I contest this >

Re: Contemporary glissando breaks bar-checking

Am 19.04.2016 um 19:41 schrieb Michael Hendry: I’ve returned to a file I created under version 2.14.0 […] and I get bar-check warnings and unsatisfactory layout. The \cadenzaOn and \cadenzaOff behaviour changed between 2.16 and 2.18; \cadenzaOff doesn’t set the measurePosition to zero

Termination of variable definitions

In starting to experiment with selective compilation using includes and/or the $(if condition action) structure provided by David Kastrup, I found that there is something very, very basic that I have never really understood. So at the risk of embarrassing myself, I should be grateful if somebody

Re: Lilypond error behaviour

On 2016-04-19 17:54, Tim Reeves wrote: > Maybe they should be called "mortally-wounding" errors? :) This is an excellent suggestion. Perhaps we could implement that further output from Lilypond becomes more and more incoherent as the poison sets in? And finally, the pain is too much to bear and

Re: Lilypond error behaviour

Peter Gentry wrote: > ... how the heck does the code know what your intentions are > and what is an "error" in your source. (wearing my professional hat for a moment) in the programing languages I use and teach, the answer is: "from static type declarations". I declare types of

Contemporary glissando breaks bar-checking

I’ve returned to a file I created under version 2.14.0, in which I used the zigzag glissando technique recommended in the online manual. As far as I can remember, this worked well, but now I’ve returned to this file to make some adjustments, and I get bar-check warnings and unsatisfactory

Re: Stems in tab

Hi Guillaume, See : http://lilypond.1069038.n5.nabble.com/Stem-length-at-a-fixed-height-td172661.html#a172686 HTH. Cheers, Pierre 2016-04-19 18:43 GMT+02:00 guillaume : > > Hello, > > > I am trying to reproduce with lilypond a tab that would look like the >

Re: temporarily add extra staff - two times in a row?

Johannes Waldmann writes: > Hi, > > How could I get a extra staff temporarily, > and then a second time, and both at the same distance > to the staff that is running through? > > I am starting from this: > http://lsr.di.unimi.it/LSR/Item?id=110 > but it does not work

Stems in tab

Hello, I am trying to reproduce with lilypond a tab that would look like the following picture and as a beginner with lilypond I am having difficulties. http://hpics.li/bb56e04 My first goal is to have all the stems ending in at same location, it works for beamed stems (thanks to \override

temporarily add extra staff - two times in a row?

Hi, How could I get a extra staff temporarily, and then a second time, and both at the same distance to the staff that is running through? I am starting from this: http://lsr.di.unimi.it/LSR/Item?id=110 but it does not work two times in a row: \score{ \new StaffGroup { \new Staff

Re: Lilypond error behaviour

> Message: 4 > Date: Tue, 19 Apr 2016 01:48:17 -0500 (CDT) > From: msk...@ansuz.sooke.bc.ca > To: Noeck > Cc: lilypond-user@gnu.org > Subject: Re: Lilypond error behaviour > Message-ID: > > Content-Type:

Re: articulation on musical expression

On Tue, Apr 19, 2016 at 10:28 AM, Gianmaria Lari wrote: > Thank you David and Urs, these are exactly what I need! > > * * * > > Before asking this question I tried googling but without success. If I > understand correctly David, the key was to search for "snippet",

Re: articulation on musical expression

Thank you David and Urs, these are exactly what I need! * * * Before asking this question I tried googling but without success. If I understand correctly David, the key was to search for "snippet", isn't it? g. On Tue, Apr 19, 2016 at 4:08 PM, Urs Liska wrote: > > > Am

Re: Absfontsize wrong font size in final PDF

On 2016-04-19 12:32, reetpetite wrote: Dear lilypond-user group, I am struggling with a font size problem. When using abs-fontsize the final pdf font sizes are always a bit smaller than the values specified results in a pdf where the font sizes are default : 10.96 pt abs-fontsize #16: 15.94 pt

Re: Absfontsize wrong font size in final PDF

On 4/19/16 4:32 AM, "reetpetite" wrote: >Dear lilypond-user group, > >I am struggling with a font size problem. >When using abs-fontsize the final pdf font sizes are always a bit smaller >than the values specified > > > >results in a pdf where the font sizes are >default :

Absfontsize wrong font size in final PDF

Dear lilypond-user group, I am struggling with a font size problem. When using abs-fontsize the final pdf font sizes are always a bit smaller than the values specified results in a pdf where the font sizes are default : 10.96 pt abs-fontsize #16: 15.94 pt abs-fontsize #12: 11.95 pt

Re: articulation on musical expression

Am 19. April 2016 16:01:43 MESZ, schrieb David Nalesnik : >Hi Gianmaria, > >On Tue, Apr 19, 2016 at 8:44 AM, Gianmaria Lari > >wrote: > >> Is there any way to apply an articulation (accent, staccato etc.) to >a >> musical expression instead of

Re: articulation on musical expression

Hi Gianmaria, On Tue, Apr 19, 2016 at 8:44 AM, Gianmaria Lari wrote: > Is there any way to apply an articulation (accent, staccato etc.) to a > musical expression instead of a single note? > > For instance, if I have a variable like this: > > c4 e g a > c a g e > >

articulation on musical expression

Is there any way to apply an articulation (accent, staccato etc.) to a musical expression instead of a single note? For instance, if I have a variable like this: c4 e g a c a g e is there any way to transform it to: c4\staccato e\staccato g\staccato a\staccato c\staccato a\staccato

Re: Lilypond error behaviour

> The non-fatal errors are re-raised as a fatal error after the pdf is > produced just to alert the user in the end that there were errors. And I > think that is what confuses most people here. The error was non-fatal > but still after everything is done, an additional fatal error is raised > to

Re: Lilypond error behaviour

On 2016-04-18 20:29, David Wright wrote: That begs the question. How do you define "clearly malformed input." If it is malformed, it can't be clear. Of course, if you mean "clearly-malformed", then I contest this vehemently. I think I was precise enough. But I must say that I don't feel

Re: Lilypond error behaviour

Thomas Morley writes: > 2016-04-19 8:48 GMT+02:00 : >> On Tue, 19 Apr 2016, Noeck wrote: >>> think that is what confuses most people here. The error was non-fatal >>> but still after everything is done, an additional fatal error is raised >>>

Re: Lilypond error behaviour

On Tue, 19 Apr 2016, Thomas Morley wrote: > My thesis was that even a non_fatal_error will be turned into a fatal > for alerting purpose finally. Yes. Mine was that such an error is fatal by definition, even if misleadingly called "non-fatal." -- Matthew Skala msk...@ansuz.sooke.bc.ca

Re: Lilypond error behaviour

2016-04-19 8:48 GMT+02:00 : > On Tue, 19 Apr 2016, Noeck wrote: >> think that is what confuses most people here. The error was non-fatal >> but still after everything is done, an additional fatal error is raised >> to draw attention to previous non-fatal errors. > >

Re: \fromproperty as instrument name

2016-04-19 9:58 GMT+02:00 David Kastrup : > Menu Jacques writes: > >> Hello folks, >> >> I’d like to use the instrument name specified in the header as the actual >> instrument name: >> >> %% >> \version "2.19.39" >> >> \header { >> instrument =

Re: \fromproperty as instrument name

Menu Jacques writes: > Hello folks, > > I’d like to use the instrument name specified in the header as the actual > instrument name: > > %% > \version "2.19.39" > > \header { > instrument = "Premier" > } > > % The score definition > \score { > { > \new Staff

\fromproperty as instrument name

Hello folks, I’d like to use the instrument name specified in the header as the actual instrument name: %% \version "2.19.39" \header { instrument = "Premier" } % The score definition \score { { \new Staff << \set Staff.instrumentName = \markup{\fill-line{\fromproperty

Re: Lilypond error behaviour

On Tue, 19 Apr 2016, Noeck wrote: > think that is what confuses most people here. The error was non-fatal > but still after everything is done, an additional fatal error is raised > to draw attention to previous non-fatal errors. Those are fatal errors. They kill the program. They're just not

Re: Lilypond error behaviour

Hi Sharon, Thomas Morley explained it to me rather well in another branch of this thread: https://www.mail-archive.com/lilypond-user@gnu.org/msg111048.html The non-fatal errors are re-raised as a fatal error after the pdf is produced just to alert the user in the end that there were errors. And