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
Setting relative pitch as a global declaration?
I'm sorry about all these damn-fool queries of mine; I promise to go back
under my rock soon. Anyway:
In the current 18th century suite I'm typesetting (for two treble
instruments without bass), there is a separate variable (containing the
notes) for each part of each movement. Then there are global declarations
about the instruments, and the key and time-signature of each movement; and
these are all brought together in score blocks.
The one thing I don't know how to do is to declare the relative pitch
globally. Thus, each music variable looks like
movement1_part1 = \new Voice \relative c'' { notes, notes, and more notes }
The difficulty is that I want to re-set the second part for a bass
instrument, so it might start off as
movement1_part2 = \new Voice \relative c { notes, notes, and more notes }
Currently this means changing the relative pitch for each movement
individually. It would be much more efficient to be able to do this just
once at the beginning, with an appropriate global declaration. Can this be
done? Is there a way to set the relative pitch of some music in a \global
block?
(Note, I have indeed RTFM, but it's quite hard - even with the search
function - to find answers to this, or examples of such use. Hence this
message...)
Thank you,
Alasdair
--
0432 854 858
https://numbersandshapes.net
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: Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac
Hello Jesse, I cannot say anything for sure (lacking a mac to try this on), but theoretically you just need to find the folder homebrew installs the packages to (according to the internet /usr/local/Cellar), find the folder for lilypond and and put the fonts into share/lilypond/current/fonts/ Cheers, Valentin Am Mittwoch, 9. Februar 2022, 00:03:34 CET schrieb Jesse Wiener: > Hi all, > > Apologies if this has been covered. I couldn't find anything about it in > the archives. > > I have an M1 mac running Monterey. I use Frescobaldi and my LilyPond > install was done with Homebrew. It all works wonderfully well. > > My question is: > > Is there some way to install alternate music fonts with this setup? > Obviously there's no .app package to put the fonts into, which makes me > think that until we have an official LilyPond.app for recent macOS > releases, there might be no way around this. > > But I wanted to put it to the group. Has anyone found a workaround? > > I did try placing font files into the 'share' folder that Homebrew creates > but that didn't seem to work. Frescobaldi threw errors. > > Thank you! > > Best, > Jesse Wiener signature.asc Description: This is a digitally signed message part.
Re: Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac
Le 09/02/2022 à 00:03, Jesse Wiener a écrit : Hi all, Apologies if this has been covered. I couldn't find anything about it in the archives. I have an M1 mac running Monterey. I use Frescobaldi and my LilyPond install was done with Homebrew. It all works wonderfully well. My question is: Is there some way to install alternate music fonts with this setup? Obviously there's no .app package to put the fonts into, which makes me think that until we have an official LilyPond.app for recent macOS releases, there might be no way around this. Read the announcement for version 2.23.6 posted today. There is now an official solution for recent macOS. It's not a LilyPond.app, but you can still drop fonts into it. Keep in mind that it's a development release. But I wanted to put it to the group. Has anyone found a workaround? I did try placing font files into the 'share' folder that Homebrew creates but that didn't seem to work. Frescobaldi threw errors. If you still want to continue with this setup (for example because it's a stable version), please post the error messages. It is hard to tell the problem without them. Regards, Jean
Installing Alternate Music Fonts with Frescobaldi and Homebrew Installation on M1 Mac
Hi all, Apologies if this has been covered. I couldn't find anything about it in the archives. I have an M1 mac running Monterey. I use Frescobaldi and my LilyPond install was done with Homebrew. It all works wonderfully well. My question is: Is there some way to install alternate music fonts with this setup? Obviously there's no .app package to put the fonts into, which makes me think that until we have an official LilyPond.app for recent macOS releases, there might be no way around this. But I wanted to put it to the group. Has anyone found a workaround? I did try placing font files into the 'share' folder that Homebrew creates but that didn't seem to work. Frescobaldi threw errors. Thank you! Best, Jesse Wiener
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.
Optional syntax highlighting now added to LilyPond's HTML documentation
Hi, The change to add syntax highlighting in the HTML version of the LilyPond documentation, discussed at https://lists.gnu.org/archive/html/lilypond-user/2022-01/msg00012.html on the lilypond-user list and in various lilypond-devel and GitLab threads, has now landed in the source tree and will be included in the next release, 2.23.7. A demo of the latest version that has been merged can be found at http://abou-samra.fr/new-highlighting-demo/notation/index.html (this will stay available for a week or so, after which I will have to delete it in order to free space on the server). Along with style adjustments, this includes a toggle to disable syntax highlighting, found at the bottom of the page. The preference can be saved in the browser so it remains across documentation pages and between browser sessions. This change was discussed over months and sparked numerous posts. I wish to thank all those, too many to list, who provided the feedback, both positive and negative, that led to its ultimate form. Special thanks go to Matthäus G. Chajdas, the Pygments maintainer who reviewed and merged the pull requests against Pygments adding and refining LilyPond support. Best regards, Jean
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
Re: Dal segno?
Hi Alasdair, Am 06.02.22 um 11:06 schrieb Alasdair McAndrew: When I search on "da capo", "dal segno" I get a huge amount of explanatory material in the Lilypond glossary, but I can't find examples of their use, or a description of their symbols. I'm sure it's there somewhere ... but so far I can't find where. How do I insert a "DC al fine" or "Dal Segno" or similar in a score? LilyPond 2.23.6 was released a few days ago, now including Dan Eble's extensive work on out-of-the-box support for da capo, dal segno, fine etc. http://lilypond.org/doc/v2.23/Documentation/notation/repeats.html http://lilypond.org/doc/v2.23/Documentation/notation/long-repeats.html Lukas
Re: Right justifying text between systems
Thank you very much: the use of "\fill-line" and "\null" works perfectly.
I was in fact trying to see how to use fill-line, and I didn't know about
"null". I'll explore the padding as well, but right at the moment even
without it, it seems that fill-line is working very well.
Again - thank you!
Alasdair
On Tuesday 08 February 2022 19:47:41 (+11:00), Aaron Hill wrote:
> On 2022-02-07 11:04 pm, Alasdair McAndrew wrote:
> > \markup {\hspace #70 \fontsize #2 {\italic {Au Rondeau puis au
premier}}}
>
> For right-alignment, you should use \fill-line:
>
>
> \markup \fill-line { \null \italic "Lorem ipsum..." }
>
>
>
> > I could do this by adding the text as a markup to one of the notes in
> > the bottom staff of Rondeau II, but then it's too close to the score
> > block.
>
> You could use a RehearsalMark at the very end with appropriate padding:
>
>
> \paper { #(set-paper-size "a5") }
>
> Rondeau.I = { R1*13 \bar "||" }
> Rondeau.II = { R1*13 \bar "||" }
> Bourree.I = { R1*13 \bar "|." }
>
> \score { \header { piece = "Rondeau I" } { \Rondeau.I } }
> \score { \header { piece = "Rondeau II" }
> { \Rondeau.II
> \tweak break-visibility #end-of-line-visible
> \tweak direction #DOWN
> \tweak font-size #0
> \tweak padding #2
> \tweak self-alignment-X #RIGHT
> \mark \markup \italic "Repeat Rondeau I" }
> }
> \score { \header { piece = "Bourree I" } { \Bourree.I } }
>
>
>
> -- Aaron Hill
>
--
0432 854 858
https://numbersandshapes.net
Re: Right justifying text between systems
Dear Rémy,
Many thanks - that works perfectly. I didn't know about "null", which makes
"fill-line" work just the way I want.
Alasdair
On Tuesday 08 February 2022 19:53:18 (+11:00), Remy CLAVERIE wrote:
Hi Alaisdair,
What about :
\markup\fill-line{ \null \fontsize #2 \italic "Au Rondeau puis au premier"} ??
Rémy
envoyé : 8 février 2022 à 08:04
de : Alasdair McAndrew
à : lilypond-user@gnu.org
objet : Right justifying text between systems
Hello,
I'm typesetting some French late baroque music, which starts with the three
movements Rondeau I, Rondeau II, Bourree I. After Rondeau II I need to
include the text direction to repeat Rondeau I. In order to try to get the
"feel" of the original, I want to have this text right justified on the
page. The best I can find so far is to manually put some space before it
and put this between two \score blocks:
\markup {\hspace #70 \fontsize #2 {\italic {Au Rondeau puis au premier}}}
This works, except for the vertical spacing - it's too far from the Rondeau
II score block, and too close to the next score block for Bourree I. I
want this text to be somehow "anchored" to Rondeau II, and let the page
layout algorithm put as much space as it needs before Bourree I.
I could do this by adding the text as a markup to one of the notes in the
bottom staff of Rondeau II, but then it's too close to the score block.
Does this make sense? What I want is:
Rondeau I
Rondeau II
"repeat Rondeau I" (and right justified)
Bourree I
and with the text closer to Rondeau II than to Bourree I. I would have
thought this would be trivial - and maybe it is - but I still can't work
out how to do it. Thank you all!
Alasdair
--
0432 854 858
https://numbersandshapes.net
Re: Right justifying text between systems
Hi Alaisdair,What about : \markup\fill-line{ \null \fontsize #2 \italic "Au Rondeau puis au premier"} ??Rémyenvoyé : 8 février 2022 à 08:04de : Alasdair McAndrew à : lilypond-user@gnu.orgobjet : Right justifying text between systemsHello,I'm typesetting some French late baroque music, which starts with the three movements Rondeau I, Rondeau II, Bourree I. After Rondeau II I need to include the text direction to repeat Rondeau I. In order to try to get the "feel" of the original, I want to have this text right justified on the page. The best I can find so far is to manually put some space before it and put this between two \score blocks:\markup {\hspace #70 \fontsize #2 {\italic {Au Rondeau puis au premier}}}This works, except for the vertical spacing - it's too far from the Rondeau II score block, and too close to the next score block for Bourree I. I want this text to be somehow "anchored" to Rondeau II, and let the page layout algorithm put as much space as it needs before Bourree I. I could do this by adding the text as a markup to one of the notes in the bottom staff of Rondeau II, but then it's too close to the score block. Does this make sense? What I want is:Rondeau IRondeau II"repeat Rondeau I" (and right justified)Bourree Iand with the text closer to Rondeau II than to Bourree I. I would have thought this would be trivial - and maybe it is - but I still can't work out how to do it. Thank you all!Alasdair-- https://numbersandshapes.net
Re: Right justifying text between systems
On 2022-02-07 11:04 pm, Alasdair McAndrew wrote:
\markup {\hspace #70 \fontsize #2 {\italic {Au Rondeau puis au
premier}}}
For right-alignment, you should use \fill-line:
\markup \fill-line { \null \italic "Lorem ipsum..." }
I could do this by adding the text as a markup to one of the notes in
the bottom staff of Rondeau II, but then it's too close to the score
block.
You could use a RehearsalMark at the very end with appropriate padding:
\paper { #(set-paper-size "a5") }
Rondeau.I = { R1*13 \bar "||" }
Rondeau.II = { R1*13 \bar "||" }
Bourree.I = { R1*13 \bar "|." }
\score { \header { piece = "Rondeau I" } { \Rondeau.I } }
\score { \header { piece = "Rondeau II" }
{ \Rondeau.II
\tweak break-visibility #end-of-line-visible
\tweak direction #DOWN
\tweak font-size #0
\tweak padding #2
\tweak self-alignment-X #RIGHT
\mark \markup \italic "Repeat Rondeau I" }
}
\score { \header { piece = "Bourree I" } { \Bourree.I } }
-- Aaron Hill
Right justifying text between systems
Hello,
I'm typesetting some French late baroque music, which starts with the three
movements Rondeau I, Rondeau II, Bourree I. After Rondeau II I need to
include the text direction to repeat Rondeau I. In order to try to get the
"feel" of the original, I want to have this text right justified on the
page. The best I can find so far is to manually put some space before it
and put this between two \score blocks:
\markup {\hspace #70 \fontsize #2 {\italic {Au Rondeau puis au premier}}}
This works, except for the vertical spacing - it's too far from the Rondeau
II score block, and too close to the next score block for Bourree I. I
want this text to be somehow "anchored" to Rondeau II, and let the page
layout algorithm put as much space as it needs before Bourree I.
I could do this by adding the text as a markup to one of the notes in the
bottom staff of Rondeau II, but then it's too close to the score block.
Does this make sense? What I want is:
Rondeau I
Rondeau II
"repeat Rondeau I" (and right justified)
Bourree I
and with the text closer to Rondeau II than to Bourree I. I would have
thought this would be trivial - and maybe it is - but I still can't work
out how to do it. Thank you all!
Alasdair
--
https://numbersandshapes.net
