Tie suicide location
Using 2.21.3: fitting music on 124 or 125 pages... Drawing systems... programming error: Tie without heads. Suicide continuing, cross fingers programming error: Tie without heads. Suicide continuing, cross fingers Any clues on how to find out the source location of this error? [I don't think it is particularly related to the release, just something I have messed up.] Andrew
Re: Automatically centering markup along an arrow
Am So., 19. Juli 2020 um 01:06 Uhr schrieb Sam Bivens : > > Hi Harm, > Yes, I see now that I was unclear. I'd like the X to be horizontally centered > between the endpoints, but not vertically centered. The markup should always > be outside the slur. And yes, I would prefer this to be outside the staff; > it's for teaching purposes, so I want to make the text clear and unencumbered > by the staff lines. > Thanks, > Sam Ok, I'll try to have a closer look tomorrow. Laters, Harm
Re: Automatically centering markup along an arrow
Hi Harm, Yes, I see now that I was unclear. I'd like the X to be *horizontally* centered between the endpoints, but not vertically centered. The markup should always be outside the slur. And yes, I would prefer this to be outside the staff; it's for teaching purposes, so I want to make the text clear and unencumbered by the staff lines. Thanks, Sam On Sat, Jul 18, 2020 at 6:57 PM Thomas Morley wrote: > Am Sa., 18. Juli 2020 um 20:34 Uhr schrieb Sam Bivens >: > > > > Hi all, > > I've recently discovered Harm's terrific arrow markup; see attached. Is > there any way to automatically center new markup along these paths instead > of manually tweaking an halign for every one? > > In other words, the "X" in the attached MWE should automatically center > itself between the endpoints of the slur/arrow. How might this be possible? > > Thanks! > > Sam > > Hi Sam, > > meanwhile Aaron heavily improved the coding: > https://lists.gnu.org/archive/html/lilypond-user/2019-04/msg00240.html > Thanks again! > > Though, it's not clear to me what you aim at: > (1) Do you really _need_ the outside-staff functionality? > (2) You wrote "the "X" in the attached MWE should automatically center > itself between the endpoints of the slur/arrow." > Alas this would look like the attached image. > Or should the added markup rather be (always?) outside the slur? > > Cheers, > Harm > -- Sam Bivens, Ph.D. Music Theory Faculty Cleveland Institute of Music 11021 East Boulevard Cleveland, OH 44106 sam.biv...@cim.edu
Re: Automatically centering markup along an arrow
Am Sa., 18. Juli 2020 um 20:34 Uhr schrieb Sam Bivens : > > Hi all, > I've recently discovered Harm's terrific arrow markup; see attached. Is there > any way to automatically center new markup along these paths instead of > manually tweaking an halign for every one? > In other words, the "X" in the attached MWE should automatically center > itself between the endpoints of the slur/arrow. How might this be possible? > Thanks! > Sam Hi Sam, meanwhile Aaron heavily improved the coding: https://lists.gnu.org/archive/html/lilypond-user/2019-04/msg00240.html Thanks again! Though, it's not clear to me what you aim at: (1) Do you really _need_ the outside-staff functionality? (2) You wrote "the "X" in the attached MWE should automatically center itself between the endpoints of the slur/arrow." Alas this would look like the attached image. Or should the added markup rather be (always?) outside the slur? Cheers, Harm
Automatically centering markup along an arrow
Hi all,
I've recently discovered Harm's terrific arrow markup; see attached. Is
there any way to automatically center new markup along these paths instead
of manually tweaking an halign for every one?
In other words, the "X" in the attached MWE should automatically center
itself between the endpoints of the slur/arrow. How might this be possible?
Thanks!
Sam
\version "2.19.84"
\include "harm-arrows.ily"
\new Staff \with { \arrowed-slur-outside-staff } {
c'1(_\markup \halign #-5 "X" |
c')
}
harm-arrows.ily
Description: Binary data
Re: A question about grace notes
Andrew Bernard writes:
> I have used this construct successfully for a long time to put grace
> notes before the barline:
>
> %--
> \version "2.21.3"
> {
> \time 2/4
> c'4 c'
> \grace {
> \bar ""
> c'8 _~
> \bar "|"
> } |
> c'4 c' |
> }
>
> %--
>
> In 2.21.3 this no longer appears to work in the context of my 300 page
> score, whereas it used to. I am at a loss to know how to provide an
> MWE as I can't make a small example where this problem arises. As this
> is a large score, I have only just uncovered the matter, and it may
> well have started going wrong with earlier development releases - I
> can't be sure.
>
> Hence the question is, has anybody seen such an issue with grace
> notes? I wonder where it could be going wrong.
My money would be on issue 34. Namely parallel context-starting events
for which some have grace timing and some not.
--
David Kastrup
A question about grace notes
I have used this construct successfully for a long time to put grace
notes before the barline:
%--
\version "2.21.3"
{
\time 2/4
c'4 c'
\grace {
\bar ""
c'8 _~
\bar "|"
} |
c'4 c' |
}
%--
In 2.21.3 this no longer appears to work in the context of my 300 page
score, whereas it used to. I am at a loss to know how to provide an
MWE as I can't make a small example where this problem arises. As this
is a large score, I have only just uncovered the matter, and it may
well have started going wrong with earlier development releases - I
can't be sure.
Hence the question is, has anybody seen such an issue with grace
notes? I wonder where it could be going wrong.
I am not asking people to solve this by editing an MWE for me. I am
asking if this is a known issue, to see if it is not something I have
been doing incorrectly all along, or something has changed recently.
Andrew
Re: 2.21.3 build problem on Mac OS X Mojave
PS> My goal is to build Lily to do experiments on the Mac, which is much faster and confortable for me to work with, rather that on my Debian virtual machine. > Le 18 juil. 2020 à 17:23, Jacques Menu a écrit : > > Hello Jonas and Werner, > > In fact I did the ‘git clone’ afresh, moving aside previous attempts. Thus > the contents of ‘build’ on both OSes is the result of the commands I showed, > up to '../configure'. > > That’s why I don’t get what happens… > > JM > > >> Le 18 juil. 2020 à 16:46, Werner LEMBERG a écrit : >> >> >>> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and >>> Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s >>> XCode, the needed tools in /opt with MacPorts, and the needed fonts >>> in /opt/local/share/fonts/urw-core35-fonts. >> >> You might apply >> >> https://github.com/macports/macports-ports/pull/7732 >> >> to build 2.21.3 with MacPorts. It's a bit unfortunate that the >> MacPorts people are slow with pull requests – 2.21.4 is coming soon... >> >> >> Werner >
Re: 2.21.3 build problem on Mac OS X Mojave
Hello Jonas and Werner, In fact I did the ‘git clone’ afresh, moving aside previous attempts. Thus the contents of ‘build’ on both OSes is the result of the commands I showed, up to '../configure'. That’s why I don’t get what happens… JM > Le 18 juil. 2020 à 16:46, Werner LEMBERG a écrit : > > >> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and >> Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s >> XCode, the needed tools in /opt with MacPorts, and the needed fonts >> in /opt/local/share/fonts/urw-core35-fonts. > > You might apply > > https://github.com/macports/macports-ports/pull/7732 > > to build 2.21.3 with MacPorts. It's a bit unfortunate that the > MacPorts people are slow with pull requests – 2.21.4 is coming soon... > > >Werner
Re: 2.21.3 build problem on Mac OS X Mojave
> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and > Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s > XCode, the needed tools in /opt with MacPorts, and the needed fonts > in /opt/local/share/fonts/urw-core35-fonts. You might apply https://github.com/macports/macports-ports/pull/7732 to build 2.21.3 with MacPorts. It's a bit unfortunate that the MacPorts people are slow with pull requests – 2.21.4 is coming soon... Werner
Re: 2.21.3 build problem on Mac OS X Mojave
Hi, Am Samstag, den 18.07.2020, 15:14 +0200 schrieb Jacques Menu: > Hello folks, > > I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and Mac OS X > 10.14.6 (Mojave). > On the latter, I installed Apple’s XCode, the needed tools in /opt with > MacPorts, and the needed fonts in /opt/local/share/fonts/urw-core35-fonts. > > Performing the same ‘git clone’ and the same steps alongside, I run into a > situation in which the contents of the build directory is by far different on > both OSes, see below. > > Then ‘make' runs fine on Debian, but fails on Mojave due to a missing > build/make directory. > > That beats me. Can someone explain why ‘../configure’ creates fewer files on > the Mac OS X side? The trace it produces is at the end of this message. > > [...] > > menu@macbookprojm: ~/lilypond-git/build > ../configure > --with-urwotf-dir=/opt/local/share/fonts/urw-core35-fonts > [...] > configure: creating ./config.status > config.status: creating config.make > config.status: creating config.hh > config.status: config.hh is unchanged This looks as if the build directory was not empty. Could it be that the directory still contained stale results from a previous invocation of configure? If that failed, I'm not sure if configure correctly recovers in all cases... It's of course possible that this is the result of executing configure again to obtain a log after the failures described before. In that case, creating a new build directory won't help much and maybe you already tried... Jonas signature.asc Description: This is a digitally signed message part
2.21.3 build problem on Mac OS X Mojave
Hello folks, I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s XCode, the needed tools in /opt with MacPorts, and the needed fonts in /opt/local/share/fonts/urw-core35-fonts. Performing the same ‘git clone’ and the same steps alongside, I run into a situation in which the contents of the build directory is by far different on both OSes, see below. Then ‘make' runs fine on Debian, but fails on Mojave due to a missing build/make directory. That beats me. Can someone explain why ‘../configure’ creates fewer files on the Mac OS X side? The trace it produces is at the end of this message. Thanks for your help! JM — Linux side: 574 git clone https://git.savannah.gnu.org/git/lilypond.git lilypond-git ; cd lilypond-git 575 ll 576 ./autogen.sh --noconfigure 577 ll 578 mkdir build/ ; cd build/ 579 ../configure user@debian: ~/lilypond-git/build > ls -sal total 228 4 drwxr-xr-x 19 user user 4096 Jul 18 14:51 . 4 drwxr-xr-x 23 user user 4096 Jul 18 14:51 .. 4 drwxr-xr-x 20 user user 4096 Jul 18 14:51 Documentation 4 -r--r--r-- 1 user user73 Jul 18 14:51 GNUmakefile 40 -rw-r--r-- 2 user user 38783 Jul 18 14:51 INSTALL.txt 4 -rw-r--r-- 2 user user 2390 Jul 18 14:51 README.txt 4 -rw-r--r-- 1 user user 2022 Jul 18 14:51 config.hh 60 -rw-r--r-- 1 user user 57730 Jul 18 14:51 config.log 8 -rw-r--r-- 1 user user 4281 Jul 18 14:51 config.make 32 -rwxr-xr-x 1 user user 31770 Jul 18 14:51 config.status 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 elisp 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 flower 4 drwxr-xr-x 3 user user 4096 Jul 18 14:51 input 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 lily 0 -rw-r--r-- 1 user user 0 Jul 18 14:51 local.make 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 ly 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 make 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 mf 4 drwxr-xr-x 3 user user 4096 Jul 18 14:51 out 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 po 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 ps 4 drwxr-xr-x 3 user user 4096 Jul 18 14:51 python 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 scm 4 drwxr-xr-x 3 user user 4096 Jul 18 14:51 scripts 4 drwxr-xr-x 3 user user 4096 Jul 18 14:51 stepmake 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 tex 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 vim user@debian: ~/lilypond-git/build > Then ‘make' succeeds, with the make subdirectory containing: user@debian: ~/lilypond-git/build > ls -sal make total 108 4 drwxr-xr-x 2 user user 4096 Jul 18 14:51 . 4 drwxr-xr-x 19 user user 4096 Jul 18 14:51 .. 4 -rw-r--r-- 1 user user 79 Jul 18 14:51 abc-rules.make 4 -rw-r--r-- 1 user user 81 Jul 18 14:51 abc-targets.make 4 -rw-r--r-- 1 user user 78 Jul 18 14:51 abc-vars.make 4 -rw-r--r-- 1 user user 89 Jul 18 14:51 doc-i18n-root-rules.make 4 -rw-r--r-- 1 user user 91 Jul 18 14:51 doc-i18n-root-targets.make 4 -rw-r--r-- 1 user user 88 Jul 18 14:51 doc-i18n-root-vars.make 4 -rw-r--r-- 1 user user 83 Jul 18 14:51 generic-rules.make 4 -rw-r--r-- 1 user user 85 Jul 18 14:51 generic-targets.make 4 -rw-r--r-- 1 user user 82 Jul 18 14:51 generic-vars.make 4 -rw-r--r-- 1 user user 89 Jul 18 14:51 lilypond-book-rules.make 4 -rw-r--r-- 1 user user 91 Jul 18 14:51 lilypond-book-targets.make 4 -rw-r--r-- 1 user user 88 Jul 18 14:51 lilypond-book-vars.make 4 -rw-r--r-- 1 user user 84 Jul 18 14:51 lilypond-rules.make 4 -rw-r--r-- 1 user user 86 Jul 18 14:51 lilypond-targets.make 4 -rw-r--r-- 1 user user 83 Jul 18 14:51 lilypond-vars.make 4 -rw-r--r-- 1 user user 78 Jul 18 14:51 ly-rules.make 4 -rw-r--r-- 1 user user 80 Jul 18 14:51 ly-targets.make — Mac OS X side: 657 git clone https://git.savannah.gnu.org/git/lilypond.git lilypond-git ; cd lilypond-git 658 ll 659 ./autogen.sh --noconfigure 660 ll 661 mkdir build/ ; cd build/ 662 ../configure --with-urwotf-dir=/opt/local/share/fonts/urw-core35-fonts menu@macbookprojm: ~/lilypond-git/build > ls -sal total 232 0 drwxr-xr-x 8 menu staff256 Jul 18 14:51 . 0 drwxr-xr-x 46 menu staff 1472 Jul 18 14:51 .. 8 -r--r--r-- 1 menu staff 73 Jul 18 14:51 GNUmakefile 8 -rw-r--r-- 1 menu staff 2022 Jul 18 14:51 config.hh 128 -rw-r--r-- 1 menu staff 62212 Jul 18 14:51 config.log 16 -rw-r--r-- 1 menu staff 5353 Jul 18 14:51 config.make 72 -rwxr-xr-x 1 menu staff 32811 Jul 18 14:51 config.status 0 -rw-r--r-- 1 menu staff 0 Jul 18 14:51 local.make menu@macbookprojm: ~/lilypond-git/build > Then ‘make' fails because there’s no ‘make' subdirectory: menu@macbookprojm: ~/lilypond-git/build > make /Users/menu/lilypond-git/build/../GNUmakefile.in:36: make/stepmake.make: No such file or directory — menu@macbookprojm: ~/lilypond-git/build > ../configure --with-urwotf-dir=/opt/local/share/fonts/urw-core35-fonts checking build system type... x86_64-ap
