Re: LilyPond 2.25.9
On 10/7/2023 10:41 AM, Jonas Hahnfeld via Discussions on LilyPond development wrote: With this release, LilyPond's HTML documentation switches (back) to texi2any. While we tried to make sure that existing links will continue to work, please report back if that is not the case. The initial appearance is good. Jonas, you are somehow the go-to developer for major technical-debt upgrades like this. Whatever further adjustments texi2any ends up needing, just having this in place is an excellent accomplishment. -- Karlin High Missouri, USA
Re: textSpanner - disable repeat of text on new line
Thanks Leo - perfect.
On Sun, Oct 8, 2023 at 8:34 AM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> Hi Bevan!
>
> I think what you are looking for is:
>
> \override TextSpanner.bound-details.left-broken.text = ##f
>
> HTH
> /Leo
>
> > 7 okt. 2023 kl. 21:13 skrev Bevan Broun :
> >
> > Hi All
> >
> > When using a text spanner I get the text repeated after a line break,
> followed by new dashes. Can I disable getting the repeat of the text and
> only get dashes on the new line? I have a case where the repeated text is
> banging up against some other text and it would be clearer with just dashes
> on the new line.
> >
> > Thanks
> >
> > \version "2.22.2"
> >
> > mybar = { c4 d c d }
> > \score {
> > \relative c' {
> > \mybar \mybar \mybar
> > \override TextSpanner.bound-details.left.text = "poco a poco
> accelerando"
> > c \startTextSpan d c d
> > \mybar
> > \mybar \break
> > \mybar
> > \stopTextSpan
> > \tempo "Tempo I"
> > \mybar \mybar \mybar \mybar
> > }
> > }
> >
> >
>
>
Re: textSpanner - disable repeat of text on new line
On Sat, Oct 7, 2023 at 1:39 PM Bevan Broun wrote:
> Hi All
>
> When using a text spanner I get the text repeated after a line break,
> followed by new dashes. Can I disable getting the repeat of the text and
> only get dashes on the new line? I have a case where the repeated text is
> banging up against some other text and it would be clearer with just dashes
> on the new line.
>
> Thanks
>
> \version "2.22.2"
>
> mybar = { c4 d c d }
> \score {
> \relative c' {
> \mybar \mybar \mybar
> \override TextSpanner.bound-details.left.text = "poco a poco
> accelerando"
> c \startTextSpan d c d
> \mybar
> \mybar \break
> \mybar
> \stopTextSpan
> \tempo "Tempo I"
> \mybar \mybar \mybar \mybar
> }
> }
>
Try using:
\override TextSpanner.bound-details.left-broken.text = ""
like this:
\version "2.22.2"
mybar = { c4 d c d }
\score {
\relative c' {
\mybar \mybar \mybar
\override TextSpanner.bound-details.left.text = "poco a poco
accelerando"
\override TextSpanner.bound-details.left-broken.text = "" % <-- add this
c \startTextSpan d c d
\mybar
\mybar \break
\mybar
\stopTextSpan
\tempo "Tempo I"
\mybar \mybar \mybar \mybar
}
}
--
Knute Snortum
Re: textSpanner - disable repeat of text on new line
Hi Bevan!
I think what you are looking for is:
\override TextSpanner.bound-details.left-broken.text = ##f
HTH
/Leo
> 7 okt. 2023 kl. 21:13 skrev Bevan Broun :
>
> Hi All
>
> When using a text spanner I get the text repeated after a line break,
> followed by new dashes. Can I disable getting the repeat of the text and only
> get dashes on the new line? I have a case where the repeated text is banging
> up against some other text and it would be clearer with just dashes on the
> new line.
>
> Thanks
>
> \version "2.22.2"
>
> mybar = { c4 d c d }
> \score {
> \relative c' {
> \mybar \mybar \mybar
> \override TextSpanner.bound-details.left.text = "poco a poco accelerando"
> c \startTextSpan d c d
> \mybar
> \mybar \break
> \mybar
> \stopTextSpan
> \tempo "Tempo I"
> \mybar \mybar \mybar \mybar
> }
> }
>
>
textSpanner - disable repeat of text on new line
Hi All
When using a text spanner I get the text repeated after a line break,
followed by new dashes. Can I disable getting the repeat of the text and
only get dashes on the new line? I have a case where the repeated text is
banging up against some other text and it would be clearer with just dashes
on the new line.
Thanks
\version "2.22.2"
mybar = { c4 d c d }
\score {
\relative c' {
\mybar \mybar \mybar
\override TextSpanner.bound-details.left.text = "poco a poco
accelerando"
c \startTextSpan d c d
\mybar
\mybar \break
\mybar
\stopTextSpan
\tempo "Tempo I"
\mybar \mybar \mybar \mybar
}
}
Re: programming error: note-column has no direction
Hello Harm,
The error you are seeing is caused by handling NoteCollisions. This has
different behavior depending on the direction of the note column. The direction
is set by the stem engraver, which is removed in this context.
To get rid of this message we can either remove collision handling alltogether
by doing
\layout {
\context {
\GregorianTranscriptionStaff
\remove Collision_engraver
}
}
or we can let Lilypond properly handle collision by having a Stem grob
created, but not actually printed:
\layout {
\context {
\GregorianTranscriptionVoice
\consists Stem_engraver
\omit Stem
}
}
The second one is most likely the more stable one, as other places might also
assume that a note column does always have a stem.
Regarding whether this is a valid bug: Basically we are running into UB here.
This context is explicitely intended for transcribing gregorian chant, so we
would not expect polyphony in the first place. But I think no syntactically
correct Lilypond code should trigger an internal error, so I’d say there are
these two paths to resove this:
→ Remove the very concept of collision from these contexts or
→ Allow the context to create silent Stem grobs
I do not know if there is any reason for not engraving the stems, but if there
isn’t I’d say the latter one is the more stable path.
Cheers,
Valentin
Am Samstag, 7. Oktober 2023, 10:35:20 CEST schrieb Thomas Morley:
> Hi,
>
> this came up in the german forum:
> https://lilypondforum.de/index.php/topic,1280.msg6613.html
>
> A more minimel example:
>
> \version "2.24.2"
>
> %% \include "gregorian.ly"
> %%
> %% \layout {
> %% \context {
> %% \GregorianTranscriptionVoice
> %% \consists Stem_engraver
> %% \omit Stem
> %% }
> %% }
>
> \new GregorianTranscriptionStaff
> <<
> \new GregorianTranscriptionVoice
> { \voiceOne b' }
> \new GregorianTranscriptionVoice
> { \voiceTwo g' }
>
>
> Returns:
> programming error: note-column has no direction
> { \voiceOne
> b' }
>
> Looks like its triggered by the removed Stem_engraver in 2.24., thus a
> first fix is to reconsist said engraver and omit Stems.
>
> Is this a valid bug?
>
>
> Thanks,
> Harm
signature.asc
Description: This is a digitally signed message part.
Re: Still failing to operate lilypond 2.20.0 64-bit version.
> On Oct 7, 2023, at 18:46, Ian West wrote: > > I can see that it is a complex business constructing a new software package. > > I was under the impression that, on 12 Aug 2022, I downloaded lilypong02.20.0 > build 20200311175017-darwin-64.tar, unpacked it and ran the package on my > 64-bit M2 MacBookAir running Ventura 13.4.1 > It ran successfully (once I had satisfied it that GS was ‘safe’. I used it > successfully for a year. From what I can see, there is https://gitlab.com/lilypond/lilypond/-/releases/v2.24.2/downloads/lilypond-2.24.2-darwin-x86_64.tar.gz listed on the page https://lilypond.org/download.html Download it, and unpack it. Probably it can be put anywhere, if compiled with relative links. To use it: In Frescobaldi, Preferences, say which one binary to use. Otherwise, use Terminal, or any other program that calls the binary. Either call the binary with full or relative (Unix style) path in Terminal, or set the environment variable PATH to include its directory "bin", or write a script which includes it. The script can be put in /usr/local/bin/ as that is included by default in PATH. See what the PATH is say one of echo $PATH env A script named "lilypond" put in say /usr/local/bin/ is a text file that may contain: export LC_CTYPE=en_US.UTF-8 export LANG=en_US.UTF-8 exec /opt/local/bin/lilypond "$@" where /opt/local/bin/lilypond is if it is MacPorts, otherwise whatever path you have chosen. After making the text file named "lilypond", make chmod a+x lilypond sudo cp lilypond /usr/local/bin/ Then, in to run it in Terminal, just write lilypond …
Re: Still failing to operate lilypond 2.20.0 64-bit version.
I can see that it is a complex business constructing a new software package. I was under the impression that, on 12 Aug 2022, I downloaded lilypong02.20.0 build 20200311175017-darwin-64.tar, unpacked it and ran the package on my 64-bit M2 MacBookAir running Ventura 13.4.1 It ran successfully (once I had satisfied it that GS was ‘safe’. I used it successfully for a year. Was there a version (or a build) of 2.20.0 that ran on 64 bit machines? Some say there was not; I think there was and that I used it. Beyond this last question I am done. I shall revert to using 2.18 on a old MacBook that still words; transferriing output to the 64-bit M2 machine for midi and for printing. Yours Ian West === > On 7 Oct 2023, at 09:27, Hans Åberg wrote: > > >> On Oct 7, 2023, at 07:43, Werner LEMBERG wrote: >> >>> libpaper is listed on >>> https://ports.macports.org/port/ghostscript/details/ >>> >>> Well, that's too bad since there is no actual license >>> incompatibility due to the use as subprocess, as already noted by >>> several others. Not sure if MacPorts can be taught that. >> >> It would be a manual override by the MacPorts people to get pre-built >> LilyPond binaries. >> >> However, a better solution to the whole problem is actually quite >> simple, providing someone has some experience with MacPorts and a bit >> of spare time: Just provide a Pull Request for >> >> https://trac.macports.org/ticket/66653 >> >> to get an LGPLed 'libpaper' library. > > Dependent dynamic libraries, when binaries, are in MacPorts not bundled with > the programs that depend on them, but installed separately, and linked at > runtime. From a copyright point of view, this does not seem different from > calling another installed program. > > >
LilyPond 2.25.9
We are happy to announce the release of LilyPond 2.25.9. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.25/Documentation/learning/installing With this release, LilyPond's HTML documentation switches (back) to texi2any. While we tried to make sure that existing links will continue to work, please report back if that is not the case. Also please let us know if, after clearing your browser's cache, something looks significantly worse than before (compared to the documentation for v2.24, for example). signature.asc Description: This is a digitally signed message part
programming error: note-column has no direction
Hi,
this came up in the german forum:
https://lilypondforum.de/index.php/topic,1280.msg6613.html
A more minimel example:
\version "2.24.2"
%% \include "gregorian.ly"
%%
%% \layout {
%% \context {
%% \GregorianTranscriptionVoice
%% \consists Stem_engraver
%% \omit Stem
%% }
%% }
\new GregorianTranscriptionStaff
<<
\new GregorianTranscriptionVoice
{ \voiceOne b' }
\new GregorianTranscriptionVoice
{ \voiceTwo g' }
>>
Returns:
programming error: note-column has no direction
{ \voiceOne
b' }
Looks like its triggered by the removed Stem_engraver in 2.24., thus a
first fix is to reconsist said engraver and omit Stems.
Is this a valid bug?
Thanks,
Harm
Re: Still failing to operate lilypond 2.20.0 64-bit version.
> On Oct 7, 2023, at 07:43, Werner LEMBERG wrote: > >> libpaper is listed on >> https://ports.macports.org/port/ghostscript/details/ >> >> Well, that's too bad since there is no actual license >> incompatibility due to the use as subprocess, as already noted by >> several others. Not sure if MacPorts can be taught that. > > It would be a manual override by the MacPorts people to get pre-built > LilyPond binaries. > > However, a better solution to the whole problem is actually quite > simple, providing someone has some experience with MacPorts and a bit > of spare time: Just provide a Pull Request for > > https://trac.macports.org/ticket/66653 > > to get an LGPLed 'libpaper' library. Dependent dynamic libraries, when binaries, are in MacPorts not bundled with the programs that depend on them, but installed separately, and linked at runtime. From a copyright point of view, this does not seem different from calling another installed program.
