Re: lost in trying to fine oll-core and or package.ily

On Wed, Oct 16, 2019 at 8:50 PM David Wright wrote: > On Wed 16 Oct 2019 at 00:17:06 (-0400), Freeman Gilmore wrote: > > On Tue, Oct 15, 2019 at 7:16 PM Urs Liska wrote: > > > > > Simon has already given a very clear answer, but I want to add some > more > > > examples that may help you understa

Re: replace-stencil and overlay-stencil (was: Re: time signature 4 / \breve ?)

Thank you for this Aaron! Cheers, Pierre Le jeu. 17 oct. 2019 à 06:42, Aaron Hill a écrit : > On 2019-10-16 7:00 pm, Graham King wrote: > > \version "2.19.82" > > { > > \once \override Staff.TimeSignature #'stencil = > > #(lambda (grob) > > (grob-interpret-markup > >grob > >

Re: time signature 4 / \breve ?

Graham, Thank you very much for both your solutions! Paul On Oct 16, 2019, at 7:00 PM, Graham King wrote: > Another way (slightly different result): > > \version "2.19.82" > > { > \once \override Staff.TimeSignature #'stencil = >#(lambda (grob) > (grob-interpret-markup > gro

Re: time signature 4 / \breve ?

On Oct 16, 2019, at 6:14 PM, Ben wrote: Ben, Thank you very much! Paul > On 10/16/2019 8:59 PM, Paul Scott wrote: >> Is it possible to write a time signature 4 / \breve ? >> >> This occurs in Carmina Burana. >> >> Thank you for any ideas, >> >> Paul >> > Hi Paul, > > Does this help get y

replace-stencil and overlay-stencil (was: Re: time signature 4 / \breve ?)

On 2019-10-16 7:00 pm, Graham King wrote: \version "2.19.82" { \once \override Staff.TimeSignature #'stencil = #(lambda (grob) (grob-interpret-markup grob #{ \markup \override #'(baseline-skip . 1) \center-column { \musicglyph "four"

Re: time signature 4 / \breve ?

Another way (slightly different result): \version "2.19.82" { \once \override Staff.TimeSignature #'stencil = #(lambda (grob) (grob-interpret-markup grob #{ \markup \override #'(baseline-skip . 1) \center-column { \musicglyph "four"

Re: time signature 4 / \breve ?

\version "2.19.82" tsMarkup = \markup { \override #'(baseline-skip . 0.5) \column { \number 4 \note #"breve" #0 } } { \override Staff.TimeSignature.style = #'default \override Staff.TimeSignature.stencil = #(lambda (grob) (grob-interpret-markup grob tsMarkup)) \time

Re: time signature 4 / \breve ?

On 10/16/2019 8:59 PM, Paul Scott wrote: Is it possible to write a time signature 4 / \breve ? This occurs in Carmina Burana. Thank you for any ideas, Paul Hi Paul, Does this help get you close to what you're looking for? (see attached) %%% \version "2.19.83" #(use-modules (

Re: lost in trying to fine oll-core and or package.ily

On Tue 15 Oct 2019 at 14:34:25 (+), Urs Liska wrote: > > For example call LilyPond with (something like (adjust to the Windows > environment) > lilypond-windows.exe -I C:\openLilyLib path\to\document.loy ↑ Does this mean the trailing slash bug¹ been

time signature 4 / \breve ?

Is it possible to write a time signature 4 / \breve ? This occurs in Carmina Burana. Thank you for any ideas, Paul ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Tuplets up and down at the same musical moment

Hi Andrew, > Any clues what greater context could be affecting this? Could it be the same problem as in this thread ? Just a thought. Kieren. Kieren MacMillan, composer (he/him/his) ‣ websi

Re: lost in trying to fine oll-core and or package.ily

On Wed 16 Oct 2019 at 00:17:06 (-0400), Freeman Gilmore wrote: > On Tue, Oct 15, 2019 at 7:16 PM Urs Liska wrote: > > > Simon has already given a very clear answer, but I want to add some more > > examples that may help you understanding the context and a part of your > > question that may not be

Re: Tuplets up and down at the same musical moment

Any clues what greater context could be affecting this? Andrew On Wed, 16 Oct 2019 at 22:18, Andrew Bernard wrote: > Pardon this somewhat strange question. The following MWE showing how to > tweak tuplet brackets up and down at the same musical moment works > perfectly fine (!). But in the con

Re: Tweaking glissando timing stems

Am Mo., 14. Okt. 2019 um 12:22 Uhr schrieb Leo Correia de Verdier : > When you write that "inner beams positions can’t be affected from > Glissando.after-line-breaking", do you mean it’s impossible, that they would > need to be recreated rather than repositioned or just that the actual code > c

Re: Makefile help!

foxfanfare: > piano-solo.01.pdf: piano-solo.01.ly \ > $(general) \ > dialogs.01.ily \ > global.01.ily \ > notes.piano-solo.01.ily \ > pedals.01.ily ... > ... and so on! Is there a better way to write this only one time? Try something like: piano-solo.%.pdf: piano-sol

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6 and Catalina 10.15

> On 16 Oct 2019, at 23:08, Thomas Scharkowski > wrote: > > Original-Nachricht >>> On 16 Oct 2019, at 21:54, Thomas Scharkowski >>> wrote: >>> >>> Original-Nachricht > On 16 Oct 2019, at 18:35, Thomas Scharkowski > wrote: > > I am cautio

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

Original-Nachricht On 16 Oct 2019, at 21:54, Thomas Scharkowski wrote: Original-Nachricht On 16 Oct 2019, at 18:35, Thomas Scharkowski wrote: I am cautious and did not upgrade to 10.15 Catalina yet. On my current (10.14.6) system lilypond-devel does not

Makefile help!

Hi all, I'm currently working on a big project and learning how to use a makefile for convenience. I'd like to know if some guys here knows how to write a proper loop? I have the following example which can generate the PDF for every single movement of a large set of pieces (there is 35 pieces in

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

> On 16 Oct 2019, at 21:54, Thomas Scharkowski > wrote: > > Original-Nachricht >>> On 16 Oct 2019, at 18:35, Thomas Scharkowski >>> wrote: >>> >>> I am cautious and did not upgrade to 10.15 Catalina yet. >>> >>> On my current (10.14.6) system lilypond-devel does not build:

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

Original-Nachricht On 16 Oct 2019, at 18:35, Thomas Scharkowski wrote: I am cautious and did not upgrade to 10.15 Catalina yet. On my current (10.14.6) system lilypond-devel does not build: error: expected initializer before '__OSX_AVAILABLE_STARTING' https://trac.macport

Re: Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

Hi Robert, > 16 bars in normal 2-staff PianoStaff on 4 systems. Then follow 4 bars in > 3-staff PianoStaff on one system, followed by 12 bars in in normal 2-staff > PianoStaff on three systems. How about this? %%% SNIPPET BEGINS \version "2.19.83" showMMRs = { \set Staff.keepAliveInterface

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

error: expected initializer before '__OSX_AVAILABLE_STARTING' https://trac.macports.org/ticket/59130 >> >> Try to install gcc9, then retry installation of lilypond-devel >> (with `port clean lilypond-devel' before doing that). > > I have already done this - no success. OK. Unfortunately

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

> On 16 Oct 2019, at 18:35, Thomas Scharkowski > wrote: > > I am cautious and did not upgrade to 10.15 Catalina yet. > > On my current (10.14.6) system lilypond-devel does not build: > > > error: expected initializer before '__OSX_AVAILABLE_STARTING' > > https://trac.macports.org/ticket/59130

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

Original-Nachricht On my current (10.14.6) system lilypond-devel does not build: error: expected initializer before '__OSX_AVAILABLE_STARTING' https://trac.macports.org/ticket/59130 Try to install gcc9, then retry installation of lilypond-devel (with `port clean lilypond-d

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

> On my current (10.14.6) system lilypond-devel does not build: > >> error: expected initializer before '__OSX_AVAILABLE_STARTING' >> https://trac.macports.org/ticket/59130 Try to install gcc9, then retry installation of lilypond-devel (with `port clean lilypond-devel' before doing that).

Re: Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

Hi Kieren, Thanks for your reaction. I could not imagine a MWE for this problem. But I can tell you what my “trick'’ is and I can also send you the whole file. It is Federico Mompou's Prelude No. 9. It begins with 16 bars in normal 2-staff PianoStaff on 4 systems. Then follow 4 bars in 3-staf

64 bit - MacPorts lilypond-devel on Mojave 10.14.6

I am cautious and did not upgrade to 10.15 Catalina yet. On my current (10.14.6) system lilypond-devel does not build: > error: expected initializer before '__OSX_AVAILABLE_STARTING' > https://trac.macports.org/ticket/59130 Would this be different on Catalina? I'd rather try to build lilypond-d

Re: 64 bit

>>> Maybe if a compiler is not listed as a dependency, it will just >>> take what is currently installed. >> >> Yes. > > So perhaps it suffices to remove it from the lilypond-devel > dependency list to get it to install. What dependency? Werner ___

Re: 64 bit

> On 16 Oct 2019, at 15:53, Mario Bolognani wrote: > > is there any simple way to run Frescobaldi+LilyPond on Catalina? Maybe in a > not so delayed future? It is also in MacPorts: % port info frescobaldi frescobaldi @2.20.0_1 (editors, python) % port info frescobaldi-devel frescobaldi-devel

64 bit

Dear developers, is there any simple way to run Frescobaldi+LilyPond on Catalina? Maybe in a not so delayed future? Your suggestions are for experienced users not for musicians with an amateur approach to the platform? Mario Bolognani ___ lilypond

Re: 64 bit

> On 16 Oct 2019, at 15:37, Werner LEMBERG wrote: > >> Maybe if a compiler is not listed as a dependency, it will just take >> what is currently installed. > > Yes. So perhaps it suffices to remove it from the lilypond-devel dependency list to get it to install. ___

Re: 64 bit

> It may be the case that only lilypond-devel is actively maintained, Probably true. I only take care of `lilypond-devel' and know nothing of `lilypond'. > but it was reported on the devel list that the dependency gcc8 > didn’t build. The patch to fall back to gcc9 has been applied to the git

Re: Slurring into another voice without breaking a beam

On 10/16/2019 9:32 AM, Simon Albrecht wrote: Hi Ben, could you maybe submit an issue to ? If not, I’ll do it myself, but I’m currently short on time… Best, Simon Oh, good idea! I'll submit it shortly :) Have a great day! On 16.10.19 13:

Re: Slurring into another voice without breaking a beam

Hi Ben, could you maybe submit an issue to ? If not, I’ll do it myself, but I’m currently short on time… Best, Simon On 16.10.19 13:15, Ben wrote: On 10/15/2019 6:16 PM, Simon Albrecht wrote: On 15.10.19 23:35, Ben wrote: On 10/15/2019 4:43

Re: 64 bit

> On 16 Oct 2019, at 09:09, Alan Shaw wrote: > > PS By doing this I got 2.18.2. This is 'sudo port install lilypond’. It may be the case that only lilypond-devel is actively maintained, but it was reported on the devel list that the dependency gcc8 didn’t build. Curiously, it is not listed as

Re: 64 bit

PS By doing this I got 2.18.2. On Wed, Oct 16, 2019 at 12:06 AM Alan Shaw wrote: > Here's what I did: > 1. > https://www.ghostwheel.com/2019/09/05/installing-macports-on-macos-10-15-catalina-beta-7/ > (step 17, sudo make install, failed, but I ran it again and it succeeded.) > 2. https://lists.g

Re: 64 bit

Here's what I did: 1. https://www.ghostwheel.com/2019/09/05/installing-macports-on-macos-10-15-catalina-beta-7/ (step 17, sudo make install, failed, but I ran it again and it succeeded.) 2. https://lists.gnu.org/archive/html/lilypond-user/2019-03/msg00040.html Both of these took a very long time b

Tuplets up and down at the same musical moment

Pardon this somewhat strange question. The following MWE showing how to tweak tuplet brackets up and down at the same musical moment works perfectly fine (!). But in the context of my larger score the inner bracket refuses to move with the tweak. I can't provide a minimal example for the error beca

Re: Slurring into another voice without breaking a beam

On 10/15/2019 6:16 PM, Simon Albrecht wrote: On 15.10.19 23:35, Ben wrote: On 10/15/2019 4:43 PM, Simon Albrecht wrote: On 15.10.19 14:33, Ben wrote: What version(s) are you using Simon? The same, basically… Are you loading modules using the ‘new’ syntax? i.e. \include "oll-core/package.i

Re: Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

Hi Robert, > Is there a “valid” possibility to insert into a normal 2-staff PianoStaff a > few bars with a 3-staff PianoStaff? Absolutely. [Note: In most traditional engraving, such a 3-staff section would usually fill the entire system, even if that meant having full-measure rests in measures

Inserting a few bars with a 3-staff PianoStaff into a normal 2-staff PianoStaff

Dear all, Is there a “valid” possibility to insert into a normal 2-staff PianoStaff a few bars with a 3-staff PianoStaff? I used some trick but the result is unsatisfactory since that 3-staff-segment does not fill the space available in that system and I have not been able to stretch it a bit