Re: LilyPond 2.23.6 released
On 2/16/22, 7:37 AM, "lilypond-devel on behalf of Thomas Scharkowski" wrote: Hi all, I installed this version today, everything seems to work. It might be of interest that the MacPorts version of 2.23.6 runs around three times faster on my MacBookPro M1, macOs 12.1 Carver Missa compile times are 28,6“ and 10,3“ MacPorts version. Is it possible that Jonas's binaries are built for i86_64, while the MacPorts version build on Thomas's machine are built for M1? If that is the case, the speed difference is probably due to the use of Rosetta 2 to run lilypond, rather than being in M1 native. I don't know if this is the case, but wanted to throw the idea out. Carl
Re: LilyPond 2.23.6 released
> Am 20.02.2022 um 10:16 schrieb Jean Abou Samra : > > > > Le 20/02/2022 à 10:13, Thomas Scharkowski a écrit : >> Sorry, couldn’t get the patched lily.scm to run - certainly a mistake on my >> side. >> If you like you can send a correct patched lily.scm to me? >> >> Thomas > > Here you go. Thanks in advance. > > Thank you, not I get the list: Success: compilation successfully completed % cumulative self time seconds seconds procedure 48.44 27.43 11.80 apply-smob/1 7.76 1.98 1.89 apply-smob/3 3.88 0.94 0.94 ly:staff-symbol-referencer::callback 2.75 0.76 0.67 ly:grob::vertical-skylines-from-stencil 2.53 0.62 0.62 lily/output-ps.scm:207:0:no-origin 2.32 3.10 0.56 ly:optimal-breaking 1.89 0.46 0.46 lily/define-event-classes.scm:132:0:ly:make-event-class 1.56 0.51 0.38 ly:grob::stencil-width 1.51 0.71 0.37 ly:grob::simple-vertical-skylines-from-extents 1.51 0.37 0.37 list? 1.02 0.25 0.25 ice-9/boot-9.scm:1098:5 0.97 1.00 0.24 ly:grob::stencil-height 0.97 0.25 0.24 ly:rhythmic-music-iterator::constructor 0.86 14.91 0.21 apply-smob/2 0.86 0.21 0.21 %after-gc-thunk 0.81 0.20 0.20 lily/output-ps.scm:210:0:settranslation 0.59 0.41 0.14 ly:axis-group-interface::width 0.59 0.14 0.14 ly:grob::pure-stencil-height 0.48 0.12 0.12 ly:axis-group-interface::calc-pure-staff-staff-spacing 0.48 0.12 0.12 lily/font.scm:133:0:lookup-font 0.43 0.16 0.10 lily/bar-line.scm:625:0:ly:bar-line::print 0.43 0.13 0.10 lily/output-ps.scm:192:0:named-glyph 0.43 0.10 0.10 ly:stem::calc-default-direction 0.43 0.10 0.10 open-output-string 0.38 0.12 0.09 lily/define-music-types.scm:906:10:make-music 0.38 0.10 0.09 ly:music::duration-length-callback 0.38 0.09 0.09 boolean? 0.38 0.09 0.09 ly:stem::calc-stem-begin-position 0.38 0.09 0.09 ly:grob-pqstring 0.05 0.01 0.01 lily/output-ps.scm:213:0:polygon 0.05 0.01 0.01 ly:staff-symbol-staff-radius 0.05 0.01 0.01 lily/define-markup-commands.scm:3523:14 0.05 0.01 0.01 ice-9/boot-9.scm:3457:0:module-export! 0.05 0.01 0.01 ly:spanner::calc-normalized-endpoints 0.05 0.01 0.01 ly:property-unset-iterator::constructor 0.05 0.01 0.01 ly:system::vertical-skyline-elements 0.05 0.01 0.01 ly:make-score 0.05 0.01 0.01 ly:accidental-interface::remove-tied 0.05 0.01 0.01 lily/music-functions.scm:773:0:make-span-event 0.05 0.01 0.01 lily/ly-syntax-constructors.scm:149:0:simultaneous-music 0.05 0.01 0.01 ice-9/eval-string.scm:56:0:eval-string 0.05 0.01 0.01 lily/ly-syntax-constructors.scm:343:0:lyric-combine 0.05 0.01 0.01 ly:grob? 0.05 0.01 0.01 lily/define-music-types.scm:623:30 0.05 0.01 0.01 lily/scheme-engravers.scm:1022:10 0.05 0.01 0.01 lily/output-ps.scm:150:0:grob-cause 0.05 0.01 0.01 lily/output-lib.scm:398:0:stem-stub::pure-height 0.05 0.01 0.01 ly:stem::calc-length 0.05 0.01 0.01 ly:stencil? 0.05 0.01 0.01 ly:spawn 0.05 0.01 0.01 ly:stem::calc-cross-staff 0.05 0.01 0.01 lily/output-ps.scm:62:0:draw-line 0.05 0.01 0.01 ly:rest::height 0.05 0.01 0.01 ly:moment? 0.05 0.01 0.01 ly:music-sequence::cumulative-length-callback 0.05 0.01 0.01 string-join 0.05 0.01 0.01 lily/output-lib.scm:862:0:accidental-interface::calc-alteration 0.05 0.01 0.01 lily/scheme-engravers.scm:953:0:Alteration_glyph_engraver 0.05 0.01 0.01 ly:note-head::include-ledger-line-height 0.05 0.01 0.01 lily/c++.scm:76:0:key-list? 0.00 48.61 0.00 ice-9/eval.scm:618:6 0.00 25.55 0.00 srfi/srfi-1.scm:634:2:for-each 0.00 24.36 0.00 ice-9/eval.scm:297:11 0.00 24.25 0.00 ice-9/boot-9.scm:781:2:catch 0.00 24.25 0.00 ly:parse-file 0.00 1.51 0.00 ly:axis-group-interface::adjacent-pure-heights 0.00 1.27 0.00 lily/framework-ps.scm:768:0:output-stencils 0.00 1.25 0.00 lily/framework-ps.scm:104:0:dump-page 0.00 1.25 0.00 ly:outputter-dump-stencil 0.00 0.79 0.00 lily/music-functions.scm:2152:2:loop 0.00 0.49 0.00 srfi/srfi-1.scm:493:0:fold-right 0.00 0.33 0.00 lily/lily-library.scm:196:0:scorify-music 0.00 0.33 0.00 srfi/srfi-1.scm:458:2:fold 0.00 0.29 0.00 lily/music-functions.scm:1049:2:loop 0.00 0.25 0.00 ly:axis-group-interface::calc-skylines 0.00 0.25
Re: LilyPond 2.23.6 released
Hi Thomas, maybe this can be handy: the `moreutils` package has a utility called `ts`, that will prepend a timestamp to each line of output. If you pipe the output of your compilation into it, you can get timing information quite easily, here's an example: % ls | ts -s "%H:%M:%.S" 00:00:00.13 _config 00:00:00.000546 myfavoritethings_ob-cm.pdf 00:00:00.000567 myfavoritethings_ob-em.pdf 00:00:00.000580 openbook_v1-1.pdf 00:00:00.000591 openbook_v1.ly 00:00:00.000602 openbook_v1.pdf 00:00:00.000613 src Here I'm using "-s" to mean "time relative to the start time", and "%.S" in the format to mean "print out subsecond timestamps". (As your runs are sub-minute, you can probably use "%M:%.S" if you feel like saving some 0's on the left) You can capture stderr also adding `2>&1` before the pipe, like this: " 2>&1 | ts ..." The moreutils package is installed in Linux distributions but doesn't appear to be there by default on MacOS, our friends on stackexchange indicate that on brew you'd use `brew install moreutils` to get the package (I just tried this, it worked fine for me), on macports I think it's something like `sudo port install moreutils` (but I don't use macports, so I haven't tested this one). HTH, Luca On Sun, Feb 20, 2022 at 9:26 AM Thomas Scharkowski < t.scharkow...@t-online.de> wrote: > Quick answer: I can notice the speed difference in the terminal output > from the very start. > I will try the diff later. > Thomas > > > Am 19.02.2022 um 20:12 schrieb Jean Abou Samra : > > > > Le 19/02/2022 à 16:41, Thomas Scharkowski a écrit : > >> One more test: > >> I installed both versions on a 2013 iMac intel Core i5. > >> > >> 24,3“ MacPorts version > >> 51,4“ gitab version > > > > > > OK, bear with me. Can you please take the following steps > > and report results? It is really important for us to identify > > what is causing this slowdown. > > > > First, does it look like one step of the compilation in particular > > is slow (for example, it takes time during "Preprocessing graphical > > objects"), or do all steps take more time? Pro tip: run lilypond with > > --verbose to have a more fine-grained view of the process. > > > > Second, edit the file lily.scm (should be under > > /path/to/lilypond-2.23.6/share/lilypond/2.23.6/scm/lily) > > to apply the following diff: > > > > > > @@ -844,8 +844,11 @@ PIDs or the number of the process." > > > > > > > > +(use-modules (statprof)) > > + > > (define-public (lilypond-main files) > >"Entry point for LilyPond." > > + (statprof (lambda () > >(eval-string (ly:command-line-code)) > >(if (ly:get-option 'help) > >(begin (ly:option-usage) > > @@ -927,7 +930,7 @@ PIDs or the number of the process." > > (ly:exit 1 #f)) > > (begin > >(ly:exit 0 #f) > > - > > +)) > > (define-public (session-start-record) > >(for-each (lambda (v) > > ;; import all public session variables natively into parser > > > > > > > > Namely, add "(use-modules (statprof))" before the definition of > > lilypond-main, "(statprof (lambda ()" after the line "Entry point > > for LilyPond", and "))" after the function. This makes LilyPond > > run under a profiling tool and report output at the end of the > > compilation. Now run once with GUILE_AUTO_COMPILE=1, to recompile > > lily.scm. The second run will be clean (all files byte-compiled); > > can you report the big list of timings that is printed at the end? > > > > Thanks in advance, > > Jean > > > > >
Re: LilyPond 2.23.6 released
Quick answer: I can notice the speed difference in the terminal output from the very start. I will try the diff later. Thomas > Am 19.02.2022 um 20:12 schrieb Jean Abou Samra : > > Le 19/02/2022 à 16:41, Thomas Scharkowski a écrit : >> One more test: >> I installed both versions on a 2013 iMac intel Core i5. >> >> 24,3“ MacPorts version >> 51,4“ gitab version > > > OK, bear with me. Can you please take the following steps > and report results? It is really important for us to identify > what is causing this slowdown. > > First, does it look like one step of the compilation in particular > is slow (for example, it takes time during "Preprocessing graphical > objects"), or do all steps take more time? Pro tip: run lilypond with > --verbose to have a more fine-grained view of the process. > > Second, edit the file lily.scm (should be under > /path/to/lilypond-2.23.6/share/lilypond/2.23.6/scm/lily) > to apply the following diff: > > > @@ -844,8 +844,11 @@ PIDs or the number of the process." > > > > +(use-modules (statprof)) > + > (define-public (lilypond-main files) >"Entry point for LilyPond." > + (statprof (lambda () >(eval-string (ly:command-line-code)) >(if (ly:get-option 'help) >(begin (ly:option-usage) > @@ -927,7 +930,7 @@ PIDs or the number of the process." > (ly:exit 1 #f)) > (begin >(ly:exit 0 #f) > - > +)) > (define-public (session-start-record) >(for-each (lambda (v) > ;; import all public session variables natively into parser > > > > Namely, add "(use-modules (statprof))" before the definition of > lilypond-main, "(statprof (lambda ()" after the line "Entry point > for LilyPond", and "))" after the function. This makes LilyPond > run under a profiling tool and report output at the end of the > compilation. Now run once with GUILE_AUTO_COMPILE=1, to recompile > lily.scm. The second run will be clean (all files byte-compiled); > can you report the big list of timings that is printed at the end? > > Thanks in advance, > Jean >
Re: LilyPond 2.23.6 released
Le 19/02/2022 à 16:41, Thomas Scharkowski a écrit : One more test: I installed both versions on a 2013 iMac intel Core i5. 24,3“ MacPorts version 51,4“ gitab version OK, bear with me. Can you please take the following steps and report results? It is really important for us to identify what is causing this slowdown. First, does it look like one step of the compilation in particular is slow (for example, it takes time during "Preprocessing graphical objects"), or do all steps take more time? Pro tip: run lilypond with --verbose to have a more fine-grained view of the process. Second, edit the file lily.scm (should be under /path/to/lilypond-2.23.6/share/lilypond/2.23.6/scm/lily) to apply the following diff: @@ -844,8 +844,11 @@ PIDs or the number of the process." +(use-modules (statprof)) + (define-public (lilypond-main files) "Entry point for LilyPond." + (statprof (lambda () (eval-string (ly:command-line-code)) (if (ly:get-option 'help) (begin (ly:option-usage) @@ -927,7 +930,7 @@ PIDs or the number of the process." (ly:exit 1 #f)) (begin (ly:exit 0 #f) - +)) (define-public (session-start-record) (for-each (lambda (v) ;; import all public session variables natively into parser Namely, add "(use-modules (statprof))" before the definition of lilypond-main, "(statprof (lambda ()" after the line "Entry point for LilyPond", and "))" after the function. This makes LilyPond run under a profiling tool and report output at the end of the compilation. Now run once with GUILE_AUTO_COMPILE=1, to recompile lily.scm. The second run will be clean (all files byte-compiled); can you report the big list of timings that is printed at the end? Thanks in advance, Jean
Re: LilyPond 2.23.6 released
One more test: I installed both versions on a 2013 iMac intel Core i5. 24,3“ MacPorts version 51,4“ gitab version Thomas > Am 18.02.2022 um 12:24 schrieb Thomas Scharkowski : > > > >> Am 17.02.2022 um 20:42 schrieb Jean Abou Samra : >> >> >> >> Le 17/02/2022 à 09:08, Thomas Scharkowski a écrit : >>> I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change >>> afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts. >> >> You did see all the logging output with warnings about 'possibly >> unbound variables' and stuff? > > Yes, I did. > >> If so, that's strange and disappointing. >> >> Jean >> > >
Re: LilyPond 2.23.6 released
> Am 17.02.2022 um 20:42 schrieb Jean Abou Samra : > > > > Le 17/02/2022 à 09:08, Thomas Scharkowski a écrit : >> I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change >> afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts. > > You did see all the logging output with warnings about 'possibly > unbound variables' and stuff? Yes, I did. > If so, that's strange and disappointing. > > Jean >
Re: LilyPond 2.23.6 released
Le 17/02/2022 à 09:08, Thomas Scharkowski a écrit : I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts. You did see all the logging output with warnings about 'possibly unbound variables' and stuff? If so, that's strange and disappointing. Jean
Re: LilyPond 2.23.6 released
I did GUILE_AUTO_COMPILE=1 lilypond file.ly - there was not much of change afterwards: MSDM.ly still needed 24“ compared to 10“ with MacPorts. Thomas > Am 17.02.2022 um 00:45 schrieb Jean Abou Samra : > > Le 16/02/2022 à 15:37, Thomas Scharkowski a écrit : >> Hi all, >> >> I installed this version today, everything seems to work. >> It might be of interest that the MacPorts version of 2.23.6 runs around >> three times faster on my MacBookPro M1, macOs 12.1 >> >> Carver Missa compile times are 28,6“ and 10,3“ MacPorts version. >> >> Thomas > > > A certain slowdown is expected -- these binaries don't have > Guile bytecode for LilyPond's .scm files yet. This should > be added eventually before we make a full switch. > > In the meanwhile, try compiling once with > > GUILE_AUTO_COMPILE=1 lilypond file.ly > > That will take longer and give you zillions of warnings, but > your LilyPond should get faster after that. It would be > interesting if you could report the timing. > > Best, > Jean > >
Re: LilyPond 2.23.6 released
Le 16/02/2022 à 15:37, Thomas Scharkowski a écrit : Hi all, I installed this version today, everything seems to work. It might be of interest that the MacPorts version of 2.23.6 runs around three times faster on my MacBookPro M1, macOs 12.1 Carver Missa compile times are 28,6“ and 10,3“ MacPorts version. Thomas A certain slowdown is expected -- these binaries don't have Guile bytecode for LilyPond's .scm files yet. This should be added eventually before we make a full switch. In the meanwhile, try compiling once with GUILE_AUTO_COMPILE=1 lilypond file.ly That will take longer and give you zillions of warnings, but your LilyPond should get faster after that. It would be interesting if you could report the timing. Best, Jean
Re: LilyPond 2.23.6 released
Hi all, I installed this version today, everything seems to work. It might be of interest that the MacPorts version of 2.23.6 runs around three times faster on my MacBookPro M1, macOs 12.1 Carver Missa compile times are 28,6“ and 10,3“ MacPorts version. Thomas > Am 08.02.2022 um 14:07 schrieb Jonas Hahnfeld via LilyPond user discussion > : > > We are happy to announce the release of LilyPond 2.23.6. This is termed > a development release, but these are usually reliable. If you want to > use the current stable version of LilyPond, we recommend using the > 2.22.1 version. > > This release also marks a transition towards Guile 2.2: The binaries > available from http://lilypond.org/development are built using GUB with > Guile 1.8, while the packages available from > https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 > were created with the new infrastructure developed over the past > months, making use of Guile 2.2. We encourage testing with your scores > to make sure that future releases of LilyPond will continue to work for > you. If there are problems with the version using Guile 2.2 that cannot > be reproduced with the binaries using Guile 1.8, we would love to hear > about them as early as possible. > > The binaries with Guile 2.2 are different in a number of ways, the two > major changes being: > 1. All binaries are 64-bit only and available for Linux, Windows (via > mingw), and macOS. In particular, this finally means official binaries > that work on macOS >= 10.15, which cannot run 32-bit programs anymore. > 2. There is no installation, simply extract the downloaded tar or zip > (for Windows) archive and run it. The binaries don't include a GUI > anymore, we recommend using third-party editors such as Frescobaldi.
Re: LilyPond 2.23.6 released
Am Samstag, dem 12.02.2022 um 21:12 +0800 schrieb Jinsong Zhao:
> Hello developers,
>
> The other issue I have encountered is in LilyPond 2.23.6/guile 2.2 is
> the following code will cause error:
>
> \version "2.23.6"
>
> \header {
> title = \markup \override #'(font-name . "思源黑体 HW Bold") "中文"
> }
>
> \relative c' {
>\key g \major
> \partial4 d4( | g4) g g |
> }
>
>
> GNU LilyPond 2.23.6 (running Guile 2.2)
> Processing `a.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...ERROR: In procedure
> ly:text-interface::interpret-markup:
> Invalid read access of chars of wide string: "鎬濇簮榛戜綋 HW Bold
> 6.13671875"
>
> And, LilyPond 2.23.6/guile 1.8 could produce correct output.
Yep, now https://gitlab.com/lilypond/lilypond/-/issues/6288 This one
affects all platforms (not only Windows), and should be relatively easy
to fix.
Thanks for reporting!
Jonas
signature.asc
Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Am Sonntag, dem 13.02.2022 um 22:37 +0100 schrieb Thomas Morley: > Am So., 13. Feb. 2022 um 16:02 Uhr schrieb Jonas Hahnfeld via LilyPond > user discussion : > > > > Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > > > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > > > LilyPond user discussion: > > > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > > > Hello developers, > > > > > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > > > > > The only issue I have currently encountered is when the filename is > > > > > > in > > > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > > > file. It could generate corrected "中文.midi", and also could generate > > > > > > correct ps and svg file, but the filenames are unreadable > > > > > > characters. > > > > > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > > > however I remember that I tested this in the past and made it work, > > > > > after fixing something in the LilyPond code. I'll have to dig up > > > > > details and figure out what broke / changed... > > > > > > > > Yep, I remembered correctly that there was a general issue with special > > > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > > > The problem was fixed quite some time ago in > > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > > > works, ie LilyPond produces the correct filenames and correctly encoded > > > > contents. What doesn't work is Ghostscript converting the generated > > > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > > > error on our side since it works with the official Windows binaries > > > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > > > have to investigate how to solve this. > > > > > > Thanks a lot for your efforts on this issue. > > > > > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > > > filenames but correctly encoded contents. The only correct filename > > > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > > > 1.8 produced all correct filenames. > > > > > > The following is the output in CMD terminal. You will find that > > > filenames of ps and svg are not correct. However the content are correct. > > > > Okay, interesting. So there actually may be multiple problems on > > Windows, again working fine on Linux... > > Not for me, being on Ubuntu 20.04 > > Compiling > \markup \override #'(font-name . "思源黑体 HW Bold") "中文" > returns: > ERROR: In procedure ly:text-interface::interpret-markup: > Invalid read access of chars of wide string: "思源黑体 HW Bold 3.8662109375" > > For both setups (see my recent mail on devel), i.e. self-compiled > 2.23.6 and the GitLab-archive Yes, that's a different problem (not related to filenames), reported in a different email thread. I also reproduced this on Linux yesterday, but didn't reply yet since I don't know what is at fault here (I presume some string conversion in our font handling). signature.asc Description: This is a digitally signed message part
\repeat segno (Was re: LilyPond 2.23.6 released)
On 2/8/2022 8:07 AM, Jonas Hahnfeld via Discussions on LilyPond development wrote: We are happy to announce the release of LilyPond 2.23.6. Thank you, especially for the new `\repeat segno` code. Works beautifully. It’ll take a little getting used to, figuring out when & when not to use `\alternative` in a `\repeat segno` block, but it’s already made my code much cleaner. Between `\repeat segno`, `\fine`, `\section` and `\sectionLabel`, most of the non-music formatting commands I’d used can be eliminated from my code. —Joel
Re: LilyPond 2.23.6 released
Am So., 13. Feb. 2022 um 16:02 Uhr schrieb Jonas Hahnfeld via LilyPond user discussion : > > Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > > LilyPond user discussion: > > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > > Hello developers, > > > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > > > The only issue I have currently encountered is when the filename is in > > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > > file. It could generate corrected "中文.midi", and also could generate > > > > > correct ps and svg file, but the filenames are unreadable characters. > > > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > > however I remember that I tested this in the past and made it work, > > > > after fixing something in the LilyPond code. I'll have to dig up > > > > details and figure out what broke / changed... > > > > > > Yep, I remembered correctly that there was a general issue with special > > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > > The problem was fixed quite some time ago in > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > > works, ie LilyPond produces the correct filenames and correctly encoded > > > contents. What doesn't work is Ghostscript converting the generated > > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > > error on our side since it works with the official Windows binaries > > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > > have to investigate how to solve this. > > > > Thanks a lot for your efforts on this issue. > > > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > > filenames but correctly encoded contents. The only correct filename > > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > > 1.8 produced all correct filenames. > > > > The following is the output in CMD terminal. You will find that > > filenames of ps and svg are not correct. However the content are correct. > > Okay, interesting. So there actually may be multiple problems on > Windows, again working fine on Linux... Not for me, being on Ubuntu 20.04 Compiling \markup \override #'(font-name . "思源黑体 HW Bold") "中文" returns: ERROR: In procedure ly:text-interface::interpret-markup: Invalid read access of chars of wide string: "思源黑体 HW Bold 3.8662109375" For both setups (see my recent mail on devel), i.e. self-compiled 2.23.6 and the GitLab-archive Cheers, Harm Verbose output: $ lilypond-git -V atest-109.ly Log level set to 287 GNU LilyPond 2.23.6 (running Guile 2.2) Relocation LilyPond binary has absolute file name: /home/hermann/lilypond-git/build/out/bin/lilypond Setting INSTALLER_PREFIX to '/home/hermann/lilypond-git/build/out' Using run-time value for datadir, setting it to '/home/hermann/lilypond-git/build/out/share/lilypond/current' Using compile-time value for libdir, setting it to '/usr/local/lib/lilypond/2.23.6' Using compile-time value for localedir, setting it to '/usr/local/share/locale' Using compile-time value for relocdir, setting it to '' Prepending '/home/hermann/lilypond-git/build/out/bin' to PATH Setting PATH to '/home/hermann/lilypond-git/build/out/bin:/home/hermann/openlilylib:/home/hermann/extending-lilypond:/home/hermann/git-cl:/home/hermann/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin' Setting GUILE_AUTO_COMPILE to '0' Setting GUILE_WARN_DEPRECATED to 'detailed' Setting XDG_CACHE_HOME to '/home/hermann/lilypond-git/build/out/share/lilypond/current' Setting GC_INITIAL_HEAP_SIZE to '40M' Setting GC_NPROCS to '1' Setting GC_FREE_SPACE_DIVISOR to '1' Effective prefix: '/home/hermann/lilypond-git/build/out/share/lilypond/current' PATH="/home/hermann/lilypond-git/build/out/bin:/home/hermann/openlilylib:/home/hermann/extending-lilypond:/home/hermann/git-cl:/home/hermann/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/lily.scm] Using (ice-9 curried-definitions) module [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/lily-library.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/output-lib.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/markup-macros.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/parser-ly-from-scheme.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/file-cache.scm]
Re: LilyPond 2.23.6 released
Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > LilyPond user discussion: > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > Hello developers, > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > The only issue I have currently encountered is when the filename is in > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > file. It could generate corrected "中文.midi", and also could generate > > > > correct ps and svg file, but the filenames are unreadable characters. > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > however I remember that I tested this in the past and made it work, > > > after fixing something in the LilyPond code. I'll have to dig up > > > details and figure out what broke / changed... > > > > Yep, I remembered correctly that there was a general issue with special > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > The problem was fixed quite some time ago in > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > works, ie LilyPond produces the correct filenames and correctly encoded > > contents. What doesn't work is Ghostscript converting the generated > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > error on our side since it works with the official Windows binaries > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > have to investigate how to solve this. > > Thanks a lot for your efforts on this issue. > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > filenames but correctly encoded contents. The only correct filename > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > 1.8 produced all correct filenames. > > The following is the output in CMD terminal. You will find that > filenames of ps and svg are not correct. However the content are correct. Okay, interesting. So there actually may be multiple problems on Windows, again working fine on Linux... > > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe 中文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `涓枃.mid'... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Converting to `涓枃.pdf'... > warning: `(gs -q -dNODISPLAY -dNOSAFER -dALLOWPSTRANSPARENCY -dNOPAUSE > -dBATCH -dAutoRotatePages=/None -dPrinted=false ./tmp--tmp-5651466)' > failed (1) > > fatal error: failed files: "涓枃.ly" > > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --ps 中文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `涓枃.mid'... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Copying to `涓枃.ps'... > Success: compilation successfully completed > > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --svg 中 > 文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --svg 中 > 文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `涓枃.mid'... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Success: compilation successfully completed > > D:\Jinso\Desktop\ly>dir > 驱动器 D 中的卷是 Data > 卷的序列号是 D6A8-795E > > D:\Jinso\Desktop\ly 的目录 > > 2022/02/12 20:32 . > 2022/02/12 20:32 .. > 2022/02/12 20:28 211 tmp--tmp-5651466 > 2022/02/12 19:57 1,617 中文.ly > 2022/02/12 20:32 1,295 中文.mid > 2022/02/12 20:28 2,187 涓枃-tmp-5790652.457878.pdf > 2022/02/12 20:2843,410,812 -tmp-5790652 > 2022/02/12 20:3243,410,812 .ps > 2022/02/12 20:3288,064 .svg > 7 个文件 86,914,998 字节 > 2 个目录 592,849,948,672 可用字节 signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Hello developers,
The other issue I have encountered is in LilyPond 2.23.6/guile 2.2 is
the following code will cause error:
\version "2.23.6"
\header {
title = \markup \override #'(font-name . "思源黑体 HW Bold") "中文"
}
\relative c' {
\key g \major
\partial4 d4( | g4) g g |
}
GNU LilyPond 2.23.6 (running Guile 2.2)
Processing `a.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...ERROR: In procedure
ly:text-interface::interpret-markup:
Invalid read access of chars of wide string: "鎬濇簮榛戜綋 HW Bold
6.13671875"
And, LilyPond 2.23.6/guile 1.8 could produce correct output.
Best,
Jinsong
On 2022/2/8 21:07, Jonas Hahnfeld via LilyPond user discussion wrote:
We are happy to announce the release of LilyPond 2.23.6. This is termed
a development release, but these are usually reliable. If you want to
use the current stable version of LilyPond, we recommend using the
2.22.1 version.
This release also marks a transition towards Guile 2.2: The binaries
available from http://lilypond.org/development are built using GUB with
Guile 1.8, while the packages available from
https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
were created with the new infrastructure developed over the past
months, making use of Guile 2.2. We encourage testing with your scores
to make sure that future releases of LilyPond will continue to work for
you. If there are problems with the version using Guile 2.2 that cannot
be reproduced with the binaries using Guile 1.8, we would love to hear
about them as early as possible.
The binaries with Guile 2.2 are different in a number of ways, the two
major changes being:
1. All binaries are 64-bit only and available for Linux, Windows (via
mingw), and macOS. In particular, this finally means official binaries
that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
2. There is no installation, simply extract the downloaded tar or zip
(for Windows) archive and run it. The binaries don't include a GUI
anymore, we recommend using third-party editors such as Frescobaldi.
Re: LilyPond 2.23.6 released
On 2022/2/12 18:48, Jonas Hahnfeld wrote: Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via LilyPond user discussion: Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: Hello developers, Thanks a lot for the transition towards Guile 2.2. I've switched to 2.23.6/guile 2.2 on Windows 10. The only issue I have currently encountered is when the filename is in Chines, for example "中文.ly", then lilypond could not generate PDF file. It could generate corrected "中文.midi", and also could generate correct ps and svg file, but the filenames are unreadable characters. I can confirm it's not working with the version using Guile 2.2 - however I remember that I tested this in the past and made it work, after fixing something in the LilyPond code. I'll have to dig up details and figure out what broke / changed... Yep, I remembered correctly that there was a general issue with special character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 The problem was fixed quite some time ago in https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this works, ie LilyPond produces the correct filenames and correctly encoded contents. What doesn't work is Ghostscript converting the generated Postscript to PDF, which I suspect is a packaging / cross-compilation error on our side since it works with the official Windows binaries from ghostscript.com and the older version of Ghostscript from GUB... Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll have to investigate how to solve this. Thanks a lot for your efforts on this issue. In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct filenames but correctly encoded contents. The only correct filename produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile 1.8 produced all correct filenames. The following is the output in CMD terminal. You will find that filenames of ps and svg are not correct. However the content are correct. D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe 中文.ly GNU LilyPond 2.23.6 (running Guile 2.2) Processing `涓枃.ly' Parsing... Interpreting music...[8][16] Preprocessing graphical objects... Interpreting music... MIDI output to `涓枃.mid'... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Converting to `涓枃.pdf'... warning: `(gs -q -dNODISPLAY -dNOSAFER -dALLOWPSTRANSPARENCY -dNOPAUSE -dBATCH -dAutoRotatePages=/None -dPrinted=false ./tmp--tmp-5651466)' failed (1) fatal error: failed files: "涓枃.ly" D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --ps 中文.ly GNU LilyPond 2.23.6 (running Guile 2.2) Processing `涓枃.ly' Parsing... Interpreting music...[8][16] Preprocessing graphical objects... Interpreting music... MIDI output to `涓枃.mid'... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Copying to `涓枃.ps'... Success: compilation successfully completed D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --svg 中 文.ly GNU LilyPond 2.23.6 (running Guile 2.2) Processing `涓枃.ly' Parsing... Interpreting music...[8][16] Preprocessing graphical objects... D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --svg 中 文.ly GNU LilyPond 2.23.6 (running Guile 2.2) Processing `涓枃.ly' Parsing... Interpreting music...[8][16] Preprocessing graphical objects... Interpreting music... MIDI output to `涓枃.mid'... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Success: compilation successfully completed D:\Jinso\Desktop\ly>dir 驱动器 D 中的卷是 Data 卷的序列号是 D6A8-795E D:\Jinso\Desktop\ly 的目录 2022/02/12 20:32 . 2022/02/12 20:32 .. 2022/02/12 20:28 211 tmp--tmp-5651466 2022/02/12 19:57 1,617 中文.ly 2022/02/12 20:32 1,295 中文.mid 2022/02/12 20:28 2,187 涓枃-tmp-5790652.457878.pdf 2022/02/12 20:2843,410,812 -tmp-5790652 2022/02/12 20:3243,410,812 .ps 2022/02/12 20:3288,064 .svg 7 个文件 86,914,998 字节 2 个目录 592,849,948,672 可用字节
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via LilyPond user discussion: > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > Hello developers, > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > 2.23.6/guile 2.2 on Windows 10. > > > > The only issue I have currently encountered is when the filename is in > > Chines, for example "中文.ly", then lilypond could not generate PDF > > file. It could generate corrected "中文.midi", and also could generate > > correct ps and svg file, but the filenames are unreadable characters. > > I can confirm it's not working with the version using Guile 2.2 - > however I remember that I tested this in the past and made it work, > after fixing something in the LilyPond code. I'll have to dig up > details and figure out what broke / changed... Yep, I remembered correctly that there was a general issue with special character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 The problem was fixed quite some time ago in https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this works, ie LilyPond produces the correct filenames and correctly encoded contents. What doesn't work is Ghostscript converting the generated Postscript to PDF, which I suspect is a packaging / cross-compilation error on our side since it works with the official Windows binaries from ghostscript.com and the older version of Ghostscript from GUB... Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll have to investigate how to solve this. signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 20:51 +0100 schrieb Jonas Hahnfeld via LilyPond user discussion: > Am Mittwoch, dem 09.02.2022 um 09:23 +0100 schrieb Mats Bengtsson: > > Googling around a bit, I foundhttps://www.tenforums.com/general- > > support/177551-how-do-i-preserve-original-folder-file-timestamp-zip- > > file.html, which explains how to unblock the extra security "feature" > > in Explorer that's behind these problems. > > Hell, what?! This also explains why it works for me, I copy the zip > archive via a USB stick, to test it even before I upload it... > > > Unfortunately, doing so requires admin rights on the machine, so for > > users with a locked machine that don't have 7-Zip installed it seems > > difficult to keep the file modification times when extracting the > > Zip. > > Fortunately, there's an easy workaround for this issue: We don't care > for the exact timestamps, all we need is that .go files are newer than > their .scm sources. We can trick Windows into creating this situation > by putting the .go files *after* the .scm files (right now things are > sorted, so lib/ goes before share/). I found and used this solution in > the "old" proof-of-concept, but thought it wasn't needed with the > current way of creating the archive. Little did I know that Windows > treats files copied from USB sticks differently than downloaded files > from the internet... Now tracked as https://gitlab.com/lilypond/lilypond/-/issues/6281, will be fixed by https://gitlab.com/lilypond/lilypond/-/merge_requests/1194 Cheers Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
On Wed, Feb 9, 2022 at 1:19 PM Jonas Hahnfeld via LilyPond user discussion < lilypond-user@gnu.org> wrote: > Am Mittwoch, dem 09.02.2022 um 21:35 +0100 schrieb David Kastrup: > > Jonas Hahnfeld via LilyPond user discussion > > writes: > > > > > Am Mittwoch, dem 09.02.2022 um 09:23 +0100 schrieb Mats Bengtsson: > > > > > > > On the other hand, the previous installers can't be installed without > > > > admin rights either, so the new Zip distribution is at least a step > > > > in the right direction for Win users without admin rights > > > > > > Yes, this is one of the motivations *not* to use an installer. It also > > > makes having multiple versions and removal of old versions no-brainers > > > > > > > One of the selling points of Frescobaldi is that it can entertain > > multiple installed versions of LilyPond. > > Yes, if you manage to install them. IIRC the Windows installer proposes > to uninstall previous versions of LilyPond. You can specify a versioned > directory for installation, but that's a manual step that the majority > of users probably won't take. > Hmm. . . I actually hadn't considered that. What I have done is to rename the current directory to , then install the new LilyPond version. If I ever have to use the older version, I can simply rename directories and get Frescobaldi to recognize the version I'm switching to. Hope that's understandable! All the best, Ralph -- Ralph Palmer Seattle USA (he, him, his) palmer.r.vio...@gmail.com
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 21:35 +0100 schrieb David Kastrup: > Jonas Hahnfeld via LilyPond user discussion > writes: > > > Am Mittwoch, dem 09.02.2022 um 09:23 +0100 schrieb Mats Bengtsson: > > > > > On the other hand, the previous installers can't be installed without > > > admin rights either, so the new Zip distribution is at least a step > > > in the right direction for Win users without admin rights > > > > Yes, this is one of the motivations *not* to use an installer. It also > > makes having multiple versions and removal of old versions no-brainers > > > > One of the selling points of Frescobaldi is that it can entertain > multiple installed versions of LilyPond. Yes, if you manage to install them. IIRC the Windows installer proposes to uninstall previous versions of LilyPond. You can specify a versioned directory for installation, but that's a manual step that the majority of users probably won't take. signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Jonas Hahnfeld via LilyPond user discussion writes: > Am Mittwoch, dem 09.02.2022 um 09:23 +0100 schrieb Mats Bengtsson: > >> On the other hand, the previous installers can't be installed without >> admin rights either, so the new Zip distribution is at least a step >> in the right direction for Win users without admin rights > > Yes, this is one of the motivations *not* to use an installer. It also > makes having multiple versions and removal of old versions no-brainers > One of the selling points of Frescobaldi is that it can entertain multiple installed versions of LilyPond. -- David Kastrup
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > Hello developers, > > Thanks a lot for the transition towards Guile 2.2. I've switched to > 2.23.6/guile 2.2 on Windows 10. > > The only issue I have currently encountered is when the filename is in > Chines, for example "中文.ly", then lilypond could not generate PDF > file. It could generate corrected "中文.midi", and also could generate > correct ps and svg file, but the filenames are unreadable characters. I can confirm it's not working with the version using Guile 2.2 - however I remember that I tested this in the past and made it work, after fixing something in the LilyPond code. I'll have to dig up details and figure out what broke / changed... signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 09:23 +0100 schrieb Mats Bengtsson: > Googling around a bit, I foundhttps://www.tenforums.com/general- > support/177551-how-do-i-preserve-original-folder-file-timestamp-zip- > file.html, which explains how to unblock the extra security "feature" > in Explorer that's behind these problems. Hell, what?! This also explains why it works for me, I copy the zip archive via a USB stick, to test it even before I upload it... > Unfortunately, doing so requires admin rights on the machine, so for > users with a locked machine that don't have 7-Zip installed it seems > difficult to keep the file modification times when extracting the > Zip. Fortunately, there's an easy workaround for this issue: We don't care for the exact timestamps, all we need is that .go files are newer than their .scm sources. We can trick Windows into creating this situation by putting the .go files *after* the .scm files (right now things are sorted, so lib/ goes before share/). I found and used this solution in the "old" proof-of-concept, but thought it wasn't needed with the current way of creating the archive. Little did I know that Windows treats files copied from USB sticks differently than downloaded files from the internet... > On the other hand, the previous installers can't be installed without > admin rights either, so the new Zip distribution is at least a step > in the right direction for Win users without admin rights Yes, this is one of the motivations *not* to use an installer. It also makes having multiple versions and removal of old versions no-brainers Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Sorry for cluttering the list, but the problem is actually with the way FontConfig 2.13.94 is packaged on NixOS. I'll report it on their Github. Thanks for the amazing work again. On Wed, Feb 9, 2022 at 3:59 PM Omid Mo'menzadeh wrote: > OK, it seems that I have found where the problem is. I built LilyPond > against FontConfig 2.13.1, and it works just like the official binary. But > the version built against FontConfig 2.13.94 and Guile 2.2 emits the same > warning I mentioned. There seems to be some sort of soft incompatibility > with FontConfig 2.13.94. > > On Wed, Feb 9, 2022 at 3:27 PM Omid Mo'menzadeh > wrote: > >> I can confirm that this is a packaging issue now. I patched the official >> binary to see the glibc on my system, and it works without any warnings. >> It's also considerably faster than my own compiled version (4.31s vs. 6.43s >> on a single file). >> >> I suppose I should go on debugging this on my own, but asking for tips, >> is there any difference in building with Guile 2.2 versus Guile 1.8, except >> the Guile available on PATH? >> >> On Wed, Feb 9, 2022 at 12:56 PM Jonas Hahnfeld wrote: >> >>> Am Mittwoch, dem 09.02.2022 um 12:50 +0330 schrieb Omid Mo'menzadeh: >>> > It works with Guile 2.2, but with a lot of the mentioned warnings. >>> > The .nix files I attached describe a recipe for building LilyPond, >>> > and two packages are built in the shell.nix file, so yes, I am >>> > building both, using the same recipe, but one with Guile 1.8, and one >>> > with Guile 2.2. Both are using the same FontConfig for sure. >>> >>> Thanks for clarifying. >>> >>> > The binaries under Nix are not really self-contained, so it would be >>> > a challenge to create a binary. But I will try to isolate the issue. >>> >>> No, that's a misunderstanding. I'm asking if you could try the binaries >>> that we provide, available for download from >>> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 on >>> your system to see if that works. >>> >>
Re: LilyPond 2.23.6 released
OK, it seems that I have found where the problem is. I built LilyPond against FontConfig 2.13.1, and it works just like the official binary. But the version built against FontConfig 2.13.94 and Guile 2.2 emits the same warning I mentioned. There seems to be some sort of soft incompatibility with FontConfig 2.13.94. On Wed, Feb 9, 2022 at 3:27 PM Omid Mo'menzadeh wrote: > I can confirm that this is a packaging issue now. I patched the official > binary to see the glibc on my system, and it works without any warnings. > It's also considerably faster than my own compiled version (4.31s vs. 6.43s > on a single file). > > I suppose I should go on debugging this on my own, but asking for tips, is > there any difference in building with Guile 2.2 versus Guile 1.8, except > the Guile available on PATH? > > On Wed, Feb 9, 2022 at 12:56 PM Jonas Hahnfeld wrote: > >> Am Mittwoch, dem 09.02.2022 um 12:50 +0330 schrieb Omid Mo'menzadeh: >> > It works with Guile 2.2, but with a lot of the mentioned warnings. >> > The .nix files I attached describe a recipe for building LilyPond, >> > and two packages are built in the shell.nix file, so yes, I am >> > building both, using the same recipe, but one with Guile 1.8, and one >> > with Guile 2.2. Both are using the same FontConfig for sure. >> >> Thanks for clarifying. >> >> > The binaries under Nix are not really self-contained, so it would be >> > a challenge to create a binary. But I will try to isolate the issue. >> >> No, that's a misunderstanding. I'm asking if you could try the binaries >> that we provide, available for download from >> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 on >> your system to see if that works. >> >
Re: LilyPond 2.23.6 released
I can confirm that this is a packaging issue now. I patched the official binary to see the glibc on my system, and it works without any warnings. It's also considerably faster than my own compiled version (4.31s vs. 6.43s on a single file). I suppose I should go on debugging this on my own, but asking for tips, is there any difference in building with Guile 2.2 versus Guile 1.8, except the Guile available on PATH? On Wed, Feb 9, 2022 at 12:56 PM Jonas Hahnfeld wrote: > Am Mittwoch, dem 09.02.2022 um 12:50 +0330 schrieb Omid Mo'menzadeh: > > It works with Guile 2.2, but with a lot of the mentioned warnings. > > The .nix files I attached describe a recipe for building LilyPond, > > and two packages are built in the shell.nix file, so yes, I am > > building both, using the same recipe, but one with Guile 1.8, and one > > with Guile 2.2. Both are using the same FontConfig for sure. > > Thanks for clarifying. > > > The binaries under Nix are not really self-contained, so it would be > > a challenge to create a binary. But I will try to isolate the issue. > > No, that's a misunderstanding. I'm asking if you could try the binaries > that we provide, available for download from > https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 on > your system to see if that works. >
Re: LilyPond 2.23.6 released
It works with Guile 2.2, but with a lot of the mentioned warnings. The .nix files I attached describe a recipe for building LilyPond, and two packages are built in the shell.nix file, so yes, I am building both, using the same recipe, but one with Guile 1.8, and one with Guile 2.2. Both are using the same FontConfig for sure. The binaries under Nix are not really self-contained, so it would be a challenge to create a binary. But I will try to isolate the issue. To test the Nix files you don't need a VM, Nix can be installed as a per-user package manager on OSX and almost any GNU/Linux distribution, but a VM may be a cleaner solution for you. On Wed, Feb 9, 2022 at 11:09 AM Jonas Hahnfeld wrote: > Am Mittwoch, dem 09.02.2022 um 00:15 +0330 schrieb Omid Mo'menzadeh: > > Thanks for the amazing work. > > I get a bunch "Fontconfig error: No writable cache directories" warnings > > using Guile 2.2, that I don't get with Lilypond compiled with Guile 1.8. > > This might be a packaging issue, but since I'm using both on the same > > system, I thought I'd share. > > Thanks for reporting. So to make sure I understand, you compile > LilyPond yourself and when using Guile 1.8 it works, but with Guile 2.2 > it doesn't? Both are using the same version of Fontconfig? Would you > mind trying the provided binaries, to rule out that there's something > wrong with LilyPond itself and it's indeed related to packaging? > > > The run-time is also heavily slower using > > Guile 2.2, with 13.37s for Guile 1.8 and 64.68s for Guile 2.2, which > might > > partly be related to the warning I mentioned. > > Some slowdown is expected because we don't have byte-compiled Scheme > files yet, but certainly not in that magnitude. > > > I'm using NixOS unstable. I will attach my shell.nix file to help with > > reproduction if needed.. > > Sounds like I need to install yet another VM... > > Jonas >
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 12:50 +0330 schrieb Omid Mo'menzadeh: > It works with Guile 2.2, but with a lot of the mentioned warnings. > The .nix files I attached describe a recipe for building LilyPond, > and two packages are built in the shell.nix file, so yes, I am > building both, using the same recipe, but one with Guile 1.8, and one > with Guile 2.2. Both are using the same FontConfig for sure. Thanks for clarifying. > The binaries under Nix are not really self-contained, so it would be > a challenge to create a binary. But I will try to isolate the issue. No, that's a misunderstanding. I'm asking if you could try the binaries that we provide, available for download from https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 on your system to see if that works. signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
On 2022-02-09 08:41, Jonas Hahnfeld
wrote:
Am Dienstag, dem 08.02.2022 um 22:35 +0100 schrieb Mats Bengtsson:
I tried the Guile 2.2 version on a Windows 10 box where I don't have
any admin rights, and even with the simplest input file, I get the
following error message:
C:\Nobackup\lilypond-2.23.6\bin\lilypond.exe test.ly
GNU LilyPond 2.23.6 (running Guile 2.2)
;;; note: source file C:/Nobackup/lilypond-2.23.6/share/guile/2.2/ice-9/eval.scm
;;; newer than compiled C:/Nobackup/lilypond-2.23.6/lib/guile/2.2/ccache/ice-9/eval.go
ERROR: In procedure apply-smob/1:
Wrong number of arguments to #
Thanks for reporting, I had hoped that we fixed this. How did you
extract the zip archive, using the Windows Explorer or some external
program? Did you move / copy the extracted directory to C:\Nobackup ?
I extracted it using Win Explorer ("Extract all"), directly into
it's current location. I just tried to extract using 7-Zip instead
and then everything works as it should. When I extracted using Win
Explorer, it seems that "Date modified" is set to the extraction
time, both on folders and individual files, whereas 7-Zip
preserves the date from the Zip archive.
/Mats
There's quite a long delay (~30s) before it prints "ERROR:" and then
another 6-7s delay before the rest of the error message. Perhaps it's
trying to rebuild the font cache, but the delay is the same when I
repeat the command several times. I tried both from CMD and
Powershell.
/Mats
Re: LilyPond 2.23.6 released
On 2022-02-09 09:10, Mats Bengtsson
wrote:
On 2022-02-09 08:41, Jonas Hahnfeld
wrote:
Am Dienstag, dem 08.02.2022 um 22:35 +0100 schrieb Mats Bengtsson:
I tried the Guile 2.2 version on a Windows 10 box where I don't have
any admin rights, and even with the simplest input file, I get the
following error message:
C:\Nobackup\lilypond-2.23.6\bin\lilypond.exe test.ly
GNU LilyPond 2.23.6 (running Guile 2.2)
;;; note: source file C:/Nobackup/lilypond-2.23.6/share/guile/2.2/ice-9/eval.scm
;;; newer than compiled C:/Nobackup/lilypond-2.23.6/lib/guile/2.2/ccache/ice-9/eval.go
ERROR: In procedure apply-smob/1:
Wrong number of arguments to #
Thanks for reporting, I had hoped that we fixed this. How did you
extract the zip archive, using the Windows Explorer or some external
program? Did you move / copy the extracted directory to C:\Nobackup ?
I extracted it using Win Explorer ("Extract all"), directly
into it's current location. I just tried to extract using 7-Zip
instead and then everything works as it should. When I extracted
using Win Explorer, it seems that "Date modified" is set to the
extraction time, both on folders and individual files, whereas
7-Zip preserves the date from the Zip archive.
/Mats
Googling around a bit, I found
https://www.tenforums.com/general-support/177551-how-do-i-preserve-original-folder-file-timestamp-zip-file.html,
which explains how to unblock the extra security "feature" in
Explorer that's behind these problems. Unfortunately, doing so
requires admin rights on the machine, so for users with a locked
machine that don't have 7-Zip installed it seems difficult to keep
the file modification times when extracting the Zip. On the other
hand, the previous installers can't be installed without admin
rights either, so the new Zip distribution is at least a step in
the right direction for Win users without admin rights (on the
other hand, you shouldn't procrastinate work tasks by typesetting
music on your employers computer, should you?)
/Mats
Re: LilyPond 2.23.6 released
Am Dienstag, dem 08.02.2022 um 22:35 +0100 schrieb Mats Bengtsson: > I tried the Guile 2.2 version on a Windows 10 box where I don't have > any admin rights, and even with the simplest input file, I get the > following error message: > C:\Nobackup\lilypond-2.23.6\bin\lilypond.exe test.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > ;;; note: source file > C:/Nobackup/lilypond-2.23.6/share/guile/2.2/ice-9/eval.scm > ;;; newer than compiled > C:/Nobackup/lilypond-2.23.6/lib/guile/2.2/ccache/ice-9/eval.go > ERROR: In procedure apply-smob/1: > Wrong number of arguments to # Thanks for reporting, I had hoped that we fixed this. How did you extract the zip archive, using the Windows Explorer or some external program? Did you move / copy the extracted directory to C:\Nobackup ? > There's quite a long delay (~30s) before it prints "ERROR:" and then > another 6-7s delay before the rest of the error message. Perhaps it's > trying to rebuild the font cache, but the delay is the same when I > repeat the command several times. I tried both from CMD and > Powershell. > /Mats signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Am Mittwoch, dem 09.02.2022 um 00:15 +0330 schrieb Omid Mo'menzadeh: > Thanks for the amazing work. > I get a bunch "Fontconfig error: No writable cache directories" warnings > using Guile 2.2, that I don't get with Lilypond compiled with Guile 1.8. > This might be a packaging issue, but since I'm using both on the same > system, I thought I'd share. Thanks for reporting. So to make sure I understand, you compile LilyPond yourself and when using Guile 1.8 it works, but with Guile 2.2 it doesn't? Both are using the same version of Fontconfig? Would you mind trying the provided binaries, to rule out that there's something wrong with LilyPond itself and it's indeed related to packaging? > The run-time is also heavily slower using > Guile 2.2, with 13.37s for Guile 1.8 and 64.68s for Guile 2.2, which might > partly be related to the warning I mentioned. Some slowdown is expected because we don't have byte-compiled Scheme files yet, but certainly not in that magnitude. > I'm using NixOS unstable. I will attach my shell.nix file to help with > reproduction if needed.. Sounds like I need to install yet another VM... Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.6 released
Hello developers, Thanks a lot for the transition towards Guile 2.2. I've switched to 2.23.6/guile 2.2 on Windows 10. The only issue I have currently encountered is when the filename is in Chines, for example "中文.ly", then lilypond could not generate PDF file. It could generate corrected "中文.midi", and also could generate correct ps and svg file, but the filenames are unreadable characters. The 2.23.6/Guile 1.8 does not have the issue. Best, Jinsong On 2022/2/8 21:07, Jonas Hahnfeld via LilyPond user discussion wrote: We are happy to announce the release of LilyPond 2.23.6. This is termed a development release, but these are usually reliable. If you want to use the current stable version of LilyPond, we recommend using the 2.22.1 version. This release also marks a transition towards Guile 2.2: The binaries available from http://lilypond.org/development are built using GUB with Guile 1.8, while the packages available from https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 were created with the new infrastructure developed over the past months, making use of Guile 2.2. We encourage testing with your scores to make sure that future releases of LilyPond will continue to work for you. If there are problems with the version using Guile 2.2 that cannot be reproduced with the binaries using Guile 1.8, we would love to hear about them as early as possible. The binaries with Guile 2.2 are different in a number of ways, the two major changes being: 1. All binaries are 64-bit only and available for Linux, Windows (via mingw), and macOS. In particular, this finally means official binaries that work on macOS >= 10.15, which cannot run 32-bit programs anymore. 2. There is no installation, simply extract the downloaded tar or zip (for Windows) archive and run it. The binaries don't include a GUI anymore, we recommend using third-party editors such as Frescobaldi.
Re: LilyPond 2.23.6 released
I tried the Guile 2.2 version on a Windows 10 box where I don't have any admin rights, and even with the simplest input file, I get the following error message: C:\Nobackup\lilypond-2.23.6\bin\lilypond.exe test.ly GNU LilyPond 2.23.6 (running Guile 2.2) ;;; note: source file C:/Nobackup/lilypond-2.23.6/share/guile/2.2/ice-9/eval.scm ;;; newer than compiled C:/Nobackup/lilypond-2.23.6/lib/guile/2.2/ccache/ice-9/eval.go ERROR: In procedure apply-smob/1: Wrong number of arguments to # There's quite a long delay (~30s) before it prints "ERROR:" and then another 6-7s delay before the rest of the error message. Perhaps it's trying to rebuild the font cache, but the delay is the same when I repeat the command several times. I tried both from CMD and Powershell. /Mats On 2022-02-08 14:07, Jonas Hahnfeld wrote:
Re: LilyPond 2.23.6 released
Thanks for the amazing work.
I get a bunch "Fontconfig error: No writable cache directories" warnings
using Guile 2.2, that I don't get with Lilypond compiled with Guile 1.8.
This might be a packaging issue, but since I'm using both on the same
system, I thought I'd share. The run-time is also heavily slower using
Guile 2.2, with 13.37s for Guile 1.8 and 64.68s for Guile 2.2, which might
partly be related to the warning I mentioned.
I'm using NixOS unstable. I will attach my shell.nix file to help with
reproduction if needed..
Omid Momenzadeh
On Tue, Feb 8, 2022 at 11:57 PM Guy Stalnaker wrote:
> I apologize for clogging up the list -- this is the first time (so far as
> I can remember) that I've had a version update trigger an error like this,
> and thus had never needed to use convert.ly.
>
> I have done so, and as Hans says ParenthesesItem.stencils is now
> Parentheses.stencils.
>
> I'll try and be good and remember that convert.ly exists :-)
>
> Thanks Jean, David, and Hans.
>
> --
>
> “Happiness is the meaning and the purpose of life, the whole aim and end
> of human existence.”
>
> ― Aristotle
>
>
> On Tue, Feb 8, 2022 at 1:45 PM Hans Aikema
> wrote:
>
>> Hi Guy,
>>
>> When you would do what you should always do for these cases (when running
>> into syntax errors when changing from an older version of lilypond to the
>> current) - run convert-ly of the new release on your code to upgrade
>> outdated syntax - it should automatically update your outdated
>> ParenthesesItem to the new Parentheses:
>>
>>
>> https://gitlab.com/lilypond/lilypond/-/blob/master/python/convertrules.py#L4410
>>
>>
>>
>> On 8 Feb 2022, at 20:17, Guy Stalnaker wrote:
>>
>>
>> I can report a change in what I see. This code does not produce an error
>> in 2.20 but does in 2.23.6:
>>
>>
>> startParenthesis = {
>> \once \override ParenthesesItem.stencils = #(lambda (grob)
>> (let ((par-list
>> (parentheses-item::calc-parenthesis-stencils grob)))
>> (list (car par-list)
>> point-stencil )))
>> }
>>
>> endParenthesis = {
>> \once \override ParenthesesItem.stencils = #(lambda (grob)
>> (let ((par-list
>> (parentheses-item::calc-parenthesis-stencils grob)))
>> (list point-stencil
>> (cadr par-list
>> }
>>
>>
>> Error is:
>>
>>
>> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:79:19
>> : error: bad grob property path
>>
>> \once \override
>>
>> ParenthesesItem.stencils = #(lambda (grob)
>>
>>
>> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19
>> : error: bad grob property path
>>
>> \once \override
>>
>> ParenthesesItem.stencils = #(lambda (grob)
>>
>>
>> I've had this in my standard include file for quite some time. What might
>> I need to change to remove the error?
>>
>>
>> Thanks
>>
>>
>> --
>>
>> “Happiness is the meaning and the purpose of life, the whole aim and end
>> of human existence.”
>>
>> ― Aristotle
>>
>>
>> On Tue, Feb 8, 2022 at 9:57 AM Jonas Hahnfeld via LilyPond user
>> discussion wrote:
>>
>>> We are happy to announce the release of LilyPond 2.23.6. This is termed
>>> a development release, but these are usually reliable. If you want to
>>> use the current stable version of LilyPond, we recommend using the
>>> 2.22.1 version.
>>>
>>> This release also marks a transition towards Guile 2.2: The binaries
>>> available from http://lilypond.org/development are built using GUB with
>>> Guile 1.8, while the packages available from
>>> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
>>> were created with the new infrastructure developed over the past
>>> months, making use of Guile 2.2. We encourage testing with your scores
>>> to make sure that future releases of LilyPond will continue to work for
>>> you. If there are problems with the version using Guile 2.2 that cannot
>>> be reproduced with the binaries using Guile 1.8, we would love to hear
>>> about them as early as possible.
>>>
>>> The binaries with Guile 2.2 are different in a number of ways, the two
>>> major changes being:
>>> 1. All binaries are 64-bit only and available for Linux, Windows (via
>>> mingw), and macOS. In particular, this finally means official binaries
>>> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
>>> 2. There is no installation, simply extract the downloaded tar or zip
>>> (for Windows) archive and run it. The binaries don't include a GUI
>>> anymore, we recommend using third-party editors such as Frescobaldi.
>>>
>>
lilypond.nix
Description: Binary data
shell.nix
Description: Binary data
Re: LilyPond 2.23.6 released
I apologize for clogging up the list -- this is the first time (so far as I
can remember) that I've had a version update trigger an error like this,
and thus had never needed to use convert.ly.
I have done so, and as Hans says ParenthesesItem.stencils is now
Parentheses.stencils.
I'll try and be good and remember that convert.ly exists :-)
Thanks Jean, David, and Hans.
--
“Happiness is the meaning and the purpose of life, the whole aim and end of
human existence.”
― Aristotle
On Tue, Feb 8, 2022 at 1:45 PM Hans Aikema wrote:
> Hi Guy,
>
> When you would do what you should always do for these cases (when running
> into syntax errors when changing from an older version of lilypond to the
> current) - run convert-ly of the new release on your code to upgrade
> outdated syntax - it should automatically update your outdated
> ParenthesesItem to the new Parentheses:
>
>
> https://gitlab.com/lilypond/lilypond/-/blob/master/python/convertrules.py#L4410
>
>
>
> On 8 Feb 2022, at 20:17, Guy Stalnaker wrote:
>
>
> I can report a change in what I see. This code does not produce an error
> in 2.20 but does in 2.23.6:
>
>
> startParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parentheses-item::calc-parenthesis-stencils grob)))
> (list (car par-list)
> point-stencil )))
> }
>
> endParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parentheses-item::calc-parenthesis-stencils grob)))
> (list point-stencil
> (cadr par-list
> }
>
>
> Error is:
>
>
> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:79:19
> : error: bad grob property path
>
> \once \override
>
> ParenthesesItem.stencils = #(lambda (grob)
>
>
> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19
> : error: bad grob property path
>
> \once \override
>
> ParenthesesItem.stencils = #(lambda (grob)
>
>
> I've had this in my standard include file for quite some time. What might
> I need to change to remove the error?
>
>
> Thanks
>
>
> --
>
> “Happiness is the meaning and the purpose of life, the whole aim and end
> of human existence.”
>
> ― Aristotle
>
>
> On Tue, Feb 8, 2022 at 9:57 AM Jonas Hahnfeld via LilyPond user discussion
> wrote:
>
>> We are happy to announce the release of LilyPond 2.23.6. This is termed
>> a development release, but these are usually reliable. If you want to
>> use the current stable version of LilyPond, we recommend using the
>> 2.22.1 version.
>>
>> This release also marks a transition towards Guile 2.2: The binaries
>> available from http://lilypond.org/development are built using GUB with
>> Guile 1.8, while the packages available from
>> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
>> were created with the new infrastructure developed over the past
>> months, making use of Guile 2.2. We encourage testing with your scores
>> to make sure that future releases of LilyPond will continue to work for
>> you. If there are problems with the version using Guile 2.2 that cannot
>> be reproduced with the binaries using Guile 1.8, we would love to hear
>> about them as early as possible.
>>
>> The binaries with Guile 2.2 are different in a number of ways, the two
>> major changes being:
>> 1. All binaries are 64-bit only and available for Linux, Windows (via
>> mingw), and macOS. In particular, this finally means official binaries
>> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
>> 2. There is no installation, simply extract the downloaded tar or zip
>> (for Windows) archive and run it. The binaries don't include a GUI
>> anymore, we recommend using third-party editors such as Frescobaldi.
>>
>
Re: LilyPond 2.23.6 released
Guy Stalnaker writes:
> I can report a change in what I see. This code does not produce an error in
> 2.20 but does in 2.23.6:
>
>
> startParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parentheses-item::calc-parenthesis-stencils grob)))
> (list (car par-list)
> point-stencil )))
> }
>
> endParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parentheses-item::calc-parenthesis-stencils grob)))
> (list point-stencil (cadr
> par-list
> }
>
>
> Error is:
>
> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:79:19
> <0>: error: bad grob property path
>
> \once \override
>
> ParenthesesItem.stencils = #(lambda (grob)
>
> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19
> <1>: error: bad grob property path
>
> \once \override
>
> ParenthesesItem.stencils = #(lambda (grob)
>
>
> I've had this in my standard include file for quite some time. What might I
> need to change to remove the error?
You could try running convert-ly on the file to find out.
--
David Kastrup
Re: LilyPond 2.23.6 released
Le 08/02/2022 à 20:02, Guy Stalnaker a écrit :
I can report a change in what I see. This code does not produce an
error in 2.20 but does in 2.23.6:
startParenthesis = {
\once \override ParenthesesItem.stencils = #(lambda (grob)
(let ((par-list
(parentheses-item::calc-parenthesis-stencils grob)))
(list (car par-list)
point-stencil )))
}
endParenthesis = {
\once \override ParenthesesItem.stencils = #(lambda (grob)
(let ((par-list
(parentheses-item::calc-parenthesis-stencils grob)))
(list point-stencil
(cadr par-list
}
Error is:
/home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:79:19
<0>: error: bad grob property path
\once \override
ParenthesesItem.stencils = #(lambda (grob)
/home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19
<1>: error: bad grob property path
\once \override
ParenthesesItem.stencils = #(lambda (grob)
I've had this in my standard include file for quite some time. What
might I need to change to remove the error?
Thanks
Just apply convert-ly which will fix your include file automatically.
Best,
Jean
Re: LilyPond 2.23.6 released
Hi Guy,
When you would do what you should always do for these cases (when running into
syntax errors when changing from an older version of lilypond to the current) -
run convert-ly of the new release on your code to upgrade outdated syntax - it
should automatically update your outdated ParenthesesItem to the new
Parentheses:
https://gitlab.com/lilypond/lilypond/-/blob/master/python/convertrules.py#L4410
> On 8 Feb 2022, at 20:17, Guy Stalnaker wrote:
>
>
> I can report a change in what I see. This code does not produce an error in
> 2.20 but does in 2.23.6:
>
>
> startParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parentheses-item::calc-parenthesis-stencils grob)))
> (list (car par-list)
> point-stencil )))
> }
>
> endParenthesis = {
> \once \override ParenthesesItem.stencils = #(lambda (grob)
> (let ((par-list
> (parentheses-item::calc-parenthesis-stencils grob)))
> (list point-stencil (cadr
> par-list
> }
>
>
> Error is:
>
> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:79:19:
> error: bad grob property path
> \once \override
> ParenthesesItem.stencils = #(lambda (grob)
> /home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19:
> error: bad grob property path
> \once \override
> ParenthesesItem.stencils = #(lambda (grob)
>
> I've had this in my standard include file for quite some time. What might I
> need to change to remove the error?
>
> Thanks
>
> --
>
> “Happiness is the meaning and the purpose of life, the whole aim and end of
> human existence.”
>
> ― Aristotle
>
>
>> On Tue, Feb 8, 2022 at 9:57 AM Jonas Hahnfeld via LilyPond user discussion
>> wrote:
>> We are happy to announce the release of LilyPond 2.23.6. This is termed
>> a development release, but these are usually reliable. If you want to
>> use the current stable version of LilyPond, we recommend using the
>> 2.22.1 version.
>>
>> This release also marks a transition towards Guile 2.2: The binaries
>> available from http://lilypond.org/development are built using GUB with
>> Guile 1.8, while the packages available from
>> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
>> were created with the new infrastructure developed over the past
>> months, making use of Guile 2.2. We encourage testing with your scores
>> to make sure that future releases of LilyPond will continue to work for
>> you. If there are problems with the version using Guile 2.2 that cannot
>> be reproduced with the binaries using Guile 1.8, we would love to hear
>> about them as early as possible.
>>
>> The binaries with Guile 2.2 are different in a number of ways, the two
>> major changes being:
>> 1. All binaries are 64-bit only and available for Linux, Windows (via
>> mingw), and macOS. In particular, this finally means official binaries
>> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
>> 2. There is no installation, simply extract the downloaded tar or zip
>> (for Windows) archive and run it. The binaries don't include a GUI
>> anymore, we recommend using third-party editors such as Frescobaldi.
Re: LilyPond 2.23.6 released
I can report a change in what I see. This code does not produce an error in
2.20 but does in 2.23.6:
startParenthesis = {
\once \override ParenthesesItem.stencils = #(lambda (grob)
(let ((par-list
(parentheses-item::calc-parenthesis-stencils grob)))
(list (car par-list)
point-stencil )))
}
endParenthesis = {
\once \override ParenthesesItem.stencils = #(lambda (grob)
(let ((par-list
(parentheses-item::calc-parenthesis-stencils grob)))
(list point-stencil (cadr
par-list
}
Error is:
/home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:79:19
<0>: error: bad grob property path
\once \override
ParenthesesItem.stencils = #(lambda (grob)
/home/guyst/Dropbox/Documents/Compositions/ResonetInLaudibus/../nak_standard_header.ly:85:19
<1>: error: bad grob property path
\once \override
ParenthesesItem.stencils = #(lambda (grob)
I've had this in my standard include file for quite some time. What might I
need to change to remove the error?
Thanks
--
“Happiness is the meaning and the purpose of life, the whole aim and end of
human existence.”
― Aristotle
On Tue, Feb 8, 2022 at 9:57 AM Jonas Hahnfeld via LilyPond user discussion <
lilypond-user@gnu.org> wrote:
> We are happy to announce the release of LilyPond 2.23.6. This is termed
> a development release, but these are usually reliable. If you want to
> use the current stable version of LilyPond, we recommend using the
> 2.22.1 version.
>
> This release also marks a transition towards Guile 2.2: The binaries
> available from http://lilypond.org/development are built using GUB with
> Guile 1.8, while the packages available from
> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
> were created with the new infrastructure developed over the past
> months, making use of Guile 2.2. We encourage testing with your scores
> to make sure that future releases of LilyPond will continue to work for
> you. If there are problems with the version using Guile 2.2 that cannot
> be reproduced with the binaries using Guile 1.8, we would love to hear
> about them as early as possible.
>
> The binaries with Guile 2.2 are different in a number of ways, the two
> major changes being:
> 1. All binaries are 64-bit only and available for Linux, Windows (via
> mingw), and macOS. In particular, this finally means official binaries
> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
> 2. There is no installation, simply extract the downloaded tar or zip
> (for Windows) archive and run it. The binaries don't include a GUI
> anymore, we recommend using third-party editors such as Frescobaldi.
>
Re: LilyPond 2.23.6 released
Hello developers, Thanks a lot for those excellent news!. I’ve switched to 2.23.6/guile 2.2 on MacOS and will report about my experience. JM > On 8 Feb 2022, at 14:07, Jonas Hahnfeld via LilyPond user discussion > wrote: > > We are happy to announce the release of LilyPond 2.23.6. This is termed > a development release, but these are usually reliable. If you want to > use the current stable version of LilyPond, we recommend using the > 2.22.1 version. > > This release also marks a transition towards Guile 2.2: The binaries > available from http://lilypond.org/development are built using GUB with > Guile 1.8, while the packages available from > https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 > were created with the new infrastructure developed over the past > months, making use of Guile 2.2. We encourage testing with your scores > to make sure that future releases of LilyPond will continue to work for > you. If there are problems with the version using Guile 2.2 that cannot > be reproduced with the binaries using Guile 1.8, we would love to hear > about them as early as possible. > > The binaries with Guile 2.2 are different in a number of ways, the two > major changes being: > 1. All binaries are 64-bit only and available for Linux, Windows (via > mingw), and macOS. In particular, this finally means official binaries > that work on macOS >= 10.15, which cannot run 32-bit programs anymore. > 2. There is no installation, simply extract the downloaded tar or zip > (for Windows) archive and run it. The binaries don't include a GUI > anymore, we recommend using third-party editors such as Frescobaldi.
LilyPond 2.23.6 released
We are happy to announce the release of LilyPond 2.23.6. This is termed a development release, but these are usually reliable. If you want to use the current stable version of LilyPond, we recommend using the 2.22.1 version. This release also marks a transition towards Guile 2.2: The binaries available from http://lilypond.org/development are built using GUB with Guile 1.8, while the packages available from https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 were created with the new infrastructure developed over the past months, making use of Guile 2.2. We encourage testing with your scores to make sure that future releases of LilyPond will continue to work for you. If there are problems with the version using Guile 2.2 that cannot be reproduced with the binaries using Guile 1.8, we would love to hear about them as early as possible. The binaries with Guile 2.2 are different in a number of ways, the two major changes being: 1. All binaries are 64-bit only and available for Linux, Windows (via mingw), and macOS. In particular, this finally means official binaries that work on macOS >= 10.15, which cannot run 32-bit programs anymore. 2. There is no installation, simply extract the downloaded tar or zip (for Windows) archive and run it. The binaries don't include a GUI anymore, we recommend using third-party editors such as Frescobaldi. signature.asc Description: This is a digitally signed message part
