Hi all, I am fluent English speaker, no problem, but thanks for the French link.
Thanks for the explanations and for the two-ways editor (my Latex ed is also going both ways). I am most familiar with XEmacs but as for Latex, I am ready to use a specific editor like Frescobaldi indeed. The only trouble is that it seems to have some problems for the Mac versions. I will try to go thru macports instead of using the dmg. So I have no excuse to not read all the doc… ☹️ Thanks guys, Merci Pierre et Jean Laurent > Le 18 sept. 2022 à 11:17, Jean Abou Samra <[email protected]> a écrit : > > Hi Laurent, > > As you can see, Jan redirected you to the lilypond-user mailing list, which > is the primary discussion 'forum' for LilyPond. > > Since your name sounds French: there is also a French-speaking equivalent of > this list, lilypond-user-fr. I'm mentioning it just in case you are more > comfortable with French. > > https://lists.gnu.org/mailman/listinfo/lilypond-user-fr > <https://lists.gnu.org/mailman/listinfo/lilypond-user-fr> > > > Le 18/09/2022 à 11:01, Jan Nieuwenhuizen 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 > > > > > If you write tons of pages, use bar checks. Whenever you write a '|' > sign, LilyPond will check that there is indeed a bar line at this point, > and warn you otherwise. They also help you navigating in the code. > > With bar checks, you input becomes > > \version "2.22.2" > > { > c' e' g' e'1 | > <e e''' e''>2 | > } > > and LilyPond gives the warnings > > /tmp/frescobaldi-nqep4lmj/tmpeggrcs80/document.ly <http://document.ly/>:4:16: > warning: barcheck failed at: 3/4 > > c' e' g' e'1 > > | > > /tmp/frescobaldi-nqep4lmj/tmpeggrcs80/document.ly <http://document.ly/>:5:17: > warning: barcheck failed at: 1/4 > > <e e''' e''>2 > > | > > > >>> 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) > > > There is. Check out Frescobaldi. > > https://frescobaldi.org/ <https://frescobaldi.org/> > > It's also possible to make point-and-click work for a number > of other editors as well (Emacs, Vim, VS Code, ...). > > If you don't already have a favorite editor that you don't want > to leave, I **strongly** recommend Frescobaldi to begin. It > doesn't just have point-and-click, but a huge number of practical > features that make entering scores much easier. > > For example, there is not only a link from the typeset score > to the source code, but also from the source code to the score, > so you can find back where your cursor is in the PDF. Plus, > there is a link from the console to the code. When I compile > the erroneous score above, the two lines with warnings get colored > in red, and when I click on the first warning, the cursor jumps > to the corresponding location in the source code, as you can > see in the screenshot attached. > > Best, > Jean > <Capture d’écran du 2022-09-18 11-16-10.png> ******************************************************* Il ne faut pas parapher après la délation Joël Martin *******************************************************
