Dear Jonas,
thanks for Your reply.
I send You the complete fille:

> \version "2.22.0"
> \include"arranger.ly"
> global = { s1*1000 }
>  %% a long length is provided
> #(init '())
>  %% Instruments list initially empty =>
> %% the positions take into account previous timing insertions.
> %% ( \global is re-analysed each time. )
> #(begin
>  ;; Builds \global
> (rm-with 'global 1 #{ \time 3/4 #} / ;; First, time signatures
> 10 #{ \time 5/8 #} /
> 20 #{ \time 4/4 #})
> (cut-end 'global 70)
>  ;; Cuts what's beyond
> (x-rm 'global #{ \mark\default #}
>  ;; Marks
> 10 20 30 40 50 60)
> (tempos
>  ;; Tempo indications
> 1 (metronome "Allegro" "4" 120) /
> 10 (metronome "" "8" "8") /
> 20 (metronome "Allargando" "4" "4.")
> 30 "Piu mosso"
> 60 (markup #:column ("FINAL"
> (metronome "Allegro vivo" "4" 200))))
> (rm-with 'global 1 #{ \key c \major #} / ;; Key signatures
> 20 #{ \key c \minor #} /
> 30 #{ \key c \major #})
> (x-rm 'global #{ \bar "||" #} 20 30 60)
>  ;; Bars
> (rm-with 'global 1 #{ \markLengthOn #})
>  ;; Miscellaneous
> (rm 'global 70 #{ \bar "|." #})
>  ;; ...the final touch
> )
>  %% End \global
> %% The list of instruments can now be initialized.
> #(init '(test)) %% List not empty = fixed metric: any new timing event
> will be ignored
> \new Staff { << \global \test >> }
>

And the console messages:

> GNU LilyPond 2.22.0
> Processing `arrangertest.ly'
> Parsing...
> arrangertest.ly:9:2: error: GUILE signaled an error for the expression
> beginning here
> #
>  (begin
> Interpreting
> music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256][264][272][280][288][296][304][312][320][328][336][344][352][360][368][376][384][392][400][408][416][424][432][440][448][456][464][472][480][488][496][504][512][520][528][536][544][552][560][568][576][584][592][600][608][616][624][632][640][648][656][664][672][680][688][696][704][712][720][728][736][744][752][760][768][776][784][792][800][808][816][824][832][840][848][856][864][872][880][888][896][904][912][920][928][936][944][952][960][968][976][984][992][1000]
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 5 or 6 pages...
> Drawing systems...
> Converting to `arrangertest.pdf'...
> Unbound variable: expand-notes-and-chords-copy-of
> Success: compilation successfully completed
>

Am Sa., 10. Apr. 2021 um 12:32 Uhr schrieb Jonas Hahnfeld <hah...@hahnjo.de
>:

> Hi Stefan,
>
> it's of course possible that arranger.ly is not yet prepared for
> LilyPond 2.22.0. In any case, it might help to post the exact error
> message (if there is one other than "GUILE signaled an error") so
> others can try to help.
>
> Jonas
>
> Am Samstag, dem 10.04.2021 um 12:28 +0200 schrieb Stefan Thomas:
> > Dear community,
> > I've remove lyp and I've also uninstalled and reinstalled lilypond
> > but the problem still persists.
> > Does someone of You know, what I could do now?
> > Thanks,
> > Stefan
> >
> > Am Fr., 9. Apr. 2021 um 17:20 Uhr schrieb Stefan Thomas
> > <kontrapunktste...@gmail.com>:
> > > Dear Jonas,
> > > I've download my lilypond from the lilypond-website, not from my
> > > linux distro.
> > > Stefan
> > >
> > > Am Do., 8. Apr. 2021 um 15:40 Uhr schrieb Jonas Hahnfeld
> > > <hah...@hahnjo.de>:
> > > > Hi,
> > > >
> > > > Am Donnerstag, dem 08.04.2021 um 11:12 +0200 schrieb Stefan
> > > > Thomas:
> > > > > Dear gilles,
> > > > > thanks very much for Your reply and Your kind help.
> > > > > I'm using version 2.22.0 now. Unfortunately, with this version,
> > > > > I
> > > > > can't see neither metronome-marks nor time signature nor
> > > > > anything
> > > > > else.
> > > > > I've got this error message:
> > > > > >  error: GUILE signaled an error for the expression beginning
> > > > > > here
> > > > > > #
> > > > > >  (begin
> > > > > >
> > > > >
> > > >
> > > > where did you get 2.22.0 from, do you use the official binaries
> > > > from
> > > > lilypond.org? If you installed LilyPond from your distribution,
> > > > and
> > > > they happen to build with Guile 2.2 already, please file a bug
> > > > with
> > > > them and ask them to move back to Guile 1.8.
> > > >
> > > > Regards
> > > > Jonas
>
>

Reply via email to