Re: Lilypond

[Valentin Petzel]

Hi Laurent, Hi Pierre,

usually using Bar checks is the way to go, but this does have its own 
limitations. E.g. if we misspell

\time 3/4 c2 d4 |

as

\time 3/4 c2 d1 |

this will not throw an error. Of course we could make use of bar number 
checks. But then, bar number checks only work if you know what bar you are in, 
and bar checks only work if you know what time signature you’re in.

But it is not hard to add additional checks. The appended file defines a 
pseudoengraver that checks for each placed rhythmic head if there is sufficient 
remaining space left in the measure and issues a warnign otherwise.

Cheers,
Valentin

Am Sonntag, 18. September 2022, 11:15:20 CEST schrieb Pierre Perol-Schneider:
> Hi Laurent, Hi Jan,
> @Laurent, see:
> https://lilypond.org/doc/v2.22/Documentation/notation/bars.html#bar-and-bar-> 
> number-checks e.g.:
> \version "2.22.0"
> { c' e' g' e'1 | <e e''' e''>2 <e e''' e''> }
> Cheers,
> Pierre
> 
> Le dim. 18 sept. 2022 à 11:02, Jan Nieuwenhuizen <janneke@gnu.org> a écrit :
> > pagani laurent writes:
> > 
> > Can someone answer Laurent?
> > 
> > > Hi Jan,
> > > 
> > > Sorry to disturb you (possibly I should have gone to some forum but
> > > this is so fundamental for me that if the answer is no, I won’t use
> > > Lilypond, so I don’t want to bother entering the forum if it is to
> > > leave it immediately).
> > > 
> > > I am having a look at Lilypond and I have a very simple question :
> > > I wrote a very simple test score :
> > > 
> > > \version "2.22.0"
> > > {
> > > c' e' g' e'1 <e e''' e''>2
> > > }
> > > 
> > > and the compilation ran without error :
> > > 
> > > Traitement de « /Users/laurent/Desktop/test.ly »
> > > Analyse...
> > > Interprétation en cours de la musique...
> > > Pré-traitement des éléments graphiques...
> > > Détermination du nombre optimal de pages...
> > > Répartition de la musique sur une page...
> > > Dessin des systèmes...
> > > Conversion à « test.pdf »...
> > > Compilation menée à son terme, avec succès.
> > > 
> > > However, there is an obvious error : the e’1.
> > > 
> > > 
> > > 
> > > 
> > > Does this mean that Lilypond will not report such errors when writing
> > > a score ? That would be worrysome because that means that after having
> > > written tons of pages, one has to go through the final product to
> > > check for such errors and then locate them in the input file (I guess
> > > there is no such interface as with some Latex editor where the pdf and
> > > the latex are linked so that clicking on the pdf text, you are
> > > directed to the corresponding latex code) which might not be very
> > > obvious. If this is explained further in the manual, just tell me to
> > > read the manual completely but again I won’t embark in this long task
> > > if it is to give up at the end...
> > > 
> > > Thanks
> > > Laurent
> > > 
> > > 
> > > 
> > > It’s tough to make predictions- especially about the future.
> > > Yogi Berra
> > 
> > --
> > Jan Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://lilypond.org
> > Freelance IT https://JoyOfSource.com | Avatar® https://AvatarAcademy.com

measure-length-warning.ly
Description: Text Data

signature.asc
Description: This is a digitally signed message part.