Re: LilyPond 2.23.8 released
On Mon, Apr 25, 2022 at 3:50 PM David Kastrup wrote: > > We are happy to announce the release of LilyPond 2.23.8. 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.2 version. > > In this release, dropping Guile 1.8 support has finally become possible > also for our sources. We'd like to dedicate this release to Ian Hulin > who was one of the first systematically working on our numerous > roadblocks for Guile 2 migration after tackling a few other high-level > problems. In the time spans where his health permitted it, he was able > to significantly reduce the amount of remaining problems for the Guile 2 > migration after having started working on them in 2010, making the goal > that we finally reached now more tangible for others to work on after he > left us in 2015. > > -- > David Kastrup > What reference manual should I use to write guile 2 for LilyPond? Thank you, ƒg
Re: LilyPond 2.23.8 released
On Tue, Apr 26, 2022 at 7:58 PM David Kastrup wrote: > Freeman Gilmore writes: > > > On Mon, Apr 25, 2022 at 3:50 PM David Kastrup wrote: > > > >> > >> We are happy to announce the release of LilyPond 2.23.8. 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.2 version. > >> > >> In this release, dropping Guile 1.8 support has finally become possible > >> also for our sources. We'd like to dedicate this release to Ian Hulin > >> who was one of the first systematically working on our numerous > >> roadblocks for Guile 2 migration after tackling a few other high-level > >> problems. In the time spans where his health permitted it, he was able > >> to significantly reduce the amount of remaining problems for the Guile 2 > >> migration after having started working on them in 2010, making the goal > >> that we finally reached now more tangible for others to work on after he > >> left us in 2015. > >> > >> -- > >> David Kastrup > >> > > > > Is there going to be a non binary version for windows coming soon? > > The source code is the same independent of operating system, so you > apparently don't mean "source code" when you say "non binary". What > would your expectations of a "non binary version for windows" be? > > -- > David Kastrup > Ok i see it now, but this was my problem. I know that the source code (binary) is usually the same for all but I have never worked with source code for LilyPond so when I read this, "Documentation writers and testers will generally want to download the latest binary:" with 5 binaries listed below, *Note, the colon should be a period;* and make it look like it is not the header for a listing. I may not b the only dummy out there!. Thank you, ƒg
Re: LilyPond 2.23.8 released
Freeman Gilmore writes: > On Mon, Apr 25, 2022 at 3:50 PM David Kastrup wrote: > >> >> We are happy to announce the release of LilyPond 2.23.8. 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.2 version. >> >> In this release, dropping Guile 1.8 support has finally become possible >> also for our sources. We'd like to dedicate this release to Ian Hulin >> who was one of the first systematically working on our numerous >> roadblocks for Guile 2 migration after tackling a few other high-level >> problems. In the time spans where his health permitted it, he was able >> to significantly reduce the amount of remaining problems for the Guile 2 >> migration after having started working on them in 2010, making the goal >> that we finally reached now more tangible for others to work on after he >> left us in 2015. >> >> -- >> David Kastrup >> > > Is there going to be a non binary version for windows coming soon? The source code is the same independent of operating system, so you apparently don't mean "source code" when you say "non binary". What would your expectations of a "non binary version for windows" be? -- David Kastrup
Re: LilyPond 2.23.8 released
On Mon, Apr 25, 2022 at 3:50 PM David Kastrup wrote: > > We are happy to announce the release of LilyPond 2.23.8. 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.2 version. > > In this release, dropping Guile 1.8 support has finally become possible > also for our sources. We'd like to dedicate this release to Ian Hulin > who was one of the first systematically working on our numerous > roadblocks for Guile 2 migration after tackling a few other high-level > problems. In the time spans where his health permitted it, he was able > to significantly reduce the amount of remaining problems for the Guile 2 > migration after having started working on them in 2010, making the goal > that we finally reached now more tangible for others to work on after he > left us in 2015. > > -- > David Kastrup > Is there going to be a non binary version for windows coming soon? ƒg
Re: LilyPond 2.23.8 released
Le 26/04/2022 à 22:49, fremoin a écrit : Hello, Quoting Jean : « A change. These are static binaries. There is no installation needed. Just unpack them somewhere and use the executable /.../bin/lilypond. You can make a symlink in ~/bin/ if you want the command to be invoked as 'lilypond'. » in https://lists.gnu.org/archive/html/lilypond-user/2022-0/msg00359.html Yes. Thanks for sparing me a reply :-) In 2.23.8, Jonas has fixed relocation (https://gitlab.com/lilypond/lilypond/-/merge_requests/1313), so the tip on symlinks should actually work now. Best, Jean
Re: LilyPond 2.23.8 released
Hello, Quoting Jean : « A change. These are static binaries. There is no installation needed. Just unpack them somewhere and use the executable /.../bin/lilypond. You can make a symlink in ~/bin/ if you want the command to be invoked as 'lilypond'. » in https://lists.gnu.org/archive/html/lilypond-user/2022-0/msg00359.html hth, Frédéric Le 26/04/2022 à 19:13, Joram Noeck a écrit : Hi, will there be a .sh file like for older releases? https://lilypond.org/download/binaries/linux-64/ The Download page https://lilypond.org/development.html links to https://gitlab.com/lilypond/lilypond/-/releases/v2.23.8/downloads/lilypond-2.23.8-linux-x86_64.tar.gz whereas it used to link to an installer (.sh) in the past. Best, Joram
Re: LilyPond 2.23.8 released
On Tue 26 Apr 2022 at 17:13:47 (+0200), Joram Noeck wrote: > Hi, > > will there be a .sh file like for older releases? > https://lilypond.org/download/binaries/linux-64/ > > The Download page https://lilypond.org/development.html links to > https://gitlab.com/lilypond/lilypond/-/releases/v2.23.8/downloads/lilypond-2.23.8-linux-x86_64.tar.gz > whereas it used to link to an installer (.sh) in the past. You don't need one. Just untar the file and that's it. I used: $ cd $ tar -zxvf path-to-my-archive/lilypond-2.23.7-linux-x86_64.tar.gz $ mv -i lilypond-2.23.7 lilypond-2.23.7-linux-x86_64¹ I run it from a script as: $ ~/lilypond-2.23.7-linux-x86_64/bin/lilypond though some prefer it in their $PATH. I presume it's changed because it no longer needs all the wrapping that the old installer script did. ¹ I want the architecture in the directory name. Cheers, David.
Re: LilyPond 2.23.8 released
On Tue, 2022-04-26 at 17:14 +0200, Federico Bruni wrote: > > On Tue, Apr 26 2022 at 08:04:40 +0100, J Martin Rushton > wrote: > > On Tue, 2022-04-26 at 00:03 +0200, Jean Abou Samra wrote: > > > I seem to recall that the Frescobaldi Flatpak package actually > > > bundles LilyPond. Maybe Federico can tell more? > > > > > Frescobaldi hasn't run on some flavours of Linux properly for two > > or > > three years. I think it stopped working around CentOS 7.9 and > > doesn't > > work correctly under AlmaLinux. The flatpack version won't run > > correctly either, so beware! > > > > I guess that the flatpak version is not working as you expect > because > you're missing some knowledge about flatpak. > If you think something is not working, please open an issue here: > https://github.com/flathub/org.frescobaldi.Frescobaldi/issues > OK, I'll have yet another go, perhaps the dependencies have been fixed in the recent updates. Funny, neither my pencil nor the manuscript paper I bought ages ago has any dependencies that stop it functioning!
Re: LilyPond 2.23.8 released
Hi, will there be a .sh file like for older releases? https://lilypond.org/download/binaries/linux-64/ The Download page https://lilypond.org/development.html links to https://gitlab.com/lilypond/lilypond/-/releases/v2.23.8/downloads/lilypond-2.23.8-linux-x86_64.tar.gz whereas it used to link to an installer (.sh) in the past. Best, Joram
Re: LilyPond 2.23.8 released
On Tue, Apr 26 2022 at 08:04:40 +0100, J Martin Rushton wrote: On Tue, 2022-04-26 at 00:03 +0200, Jean Abou Samra wrote: I seem to recall that the Frescobaldi Flatpak package actually bundles LilyPond. Maybe Federico can tell more? Frescobaldi hasn't run on some flavours of Linux properly for two or three years. I think it stopped working around CentOS 7.9 and doesn't work correctly under AlmaLinux. The flatpack version won't run correctly either, so beware! I guess that the flatpak version is not working as you expect because you're missing some knowledge about flatpak. If you think something is not working, please open an issue here: https://github.com/flathub/org.frescobaldi.Frescobaldi/issues
Re: (Semi)German chords (B <-> H) with normal slash chords?
Am 26.04.22 um 12:09 schrieb Boris Lau:
Dear list,
I'm working on a songbook for german kids. Although I personally don't
like them, I want to use German chord names (B and H exchanged). I could
use \germanChords or \semiGermanChords to achieve that, but that also
changes the behavior of slash chords:
B7 -> H7 <-- this is what I want
E/G# -> E/gis <-- this is weird
Maybe some developer thought, that E/gis is how it's done in Germany.
I think it's rather uncommon and pretty ugly ;-)
But personal tastes aside, is there a way to get the B<->H thing without
changing the slash chords?
Many thanks in advance,
Best, Boris
Hello Boris,
only a few weeks ago I asked the same (subject: "German chords with
uppercase bass".
Thomas Morley answered:
\germanChords uses `chord-name->german-markup' to print the root-name
(chordRootNamer) of a chord and `note-name->german-markup' to print an
additional bass-note (chordNoteNamer).
If you comment the chordNoteNamer there, the chordRootNamer takes over.
germanChords = {
\set chordRootNamer = #(chord-name->german-markup #t)
%\set chordNoteNamer = #note-name->german-markup
}
scm = \chordmode {
c1/c | cis/cis
b1/b | bis/bis | bes/bes
}
<<
\new ChordNames {
\germanChords \scm
}
\context Voice { \scm }
NB altered bass notes are now printed like the root, i.e. C♯ not Cis.
Already ok? If not holler.
Imho, german chords in LilyPond are not correct and were never: as an
example, C♯ is never a _german_ naming
Also see my comment:
https://gitlab.com/lilypond/lilypond/-/issues/6305#note_890059707
Hraban
(Semi)German chords (B <-> H) with normal slash chords?
Dear list, I'm working on a songbook for german kids. Although I personally don't like them, I want to use German chord names (B and H exchanged). I could use \germanChords or \semiGermanChords to achieve that, but that also changes the behavior of slash chords: B7 -> H7 <-- this is what I want E/G# -> E/gis <-- this is weird Maybe some developer thought, that E/gis is how it's done in Germany. I think it's rather uncommon and pretty ugly ;-) But personal tastes aside, is there a way to get the B<->H thing without changing the slash chords? Many thanks in advance, Best, Boris -- Dr. Boris Lau +49 174 9436758 http://www.borislau.de Im Ried 7a, 79249 Merzhausen, Germany
Re: LilyPond 2.23.8 released
On Tue, Apr 26 2022 at 00:03:17 +0200, Jean Abou Samra wrote: (Apparently no PPA or Flatpak version.) https://flathub.org/apps/details/org.frescobaldi.Frescobaldi I seem to recall that the Frescobaldi Flatpak package actually bundles LilyPond. Maybe Federico can tell more? Yes, it currently bundles 2.22.2 and 2.23.7. There's currently an issue in one of the build (flatpak) dependencies which blocks any update.
Re: LilyPond 2.23.8 released
On Tue, 2022-04-26 at 00:03 +0200, Jean Abou Samra wrote: > I seem to recall that the Frescobaldi Flatpak package actually > bundles LilyPond. Maybe Federico can tell more? > Frescobaldi hasn't run on some flavours of Linux properly for two or three years. I think it stopped working around CentOS 7.9 and doesn't work correctly under AlmaLinux. The flatpack version won't run correctly either, so beware! Martin
