Re: inconsistent bar number placement

On Fri 17 Mar 2017 at 15:54:24 (-0600), Juan Cristóbal Cerrillo wrote: > Hello Malte, > > Yes, my version is 2.18.2 > This is what the top of page 3 looks like with ragged-right and ragged-bottom > ##t > > Are you not seeing the same? Nope. How come your crochets are at the same pitch as the

Re: can we pass in header variables as CLI parameters?

On Fri 17 Mar 2017 at 21:10:29 (+), Ian Ring wrote: > Hi, sorry if this has been asked before... > > Is it possible to pass in header variables in via the CLI? > > For example, I would like to pass the copyright date in via a parameter, > instead of it being saved in the .LY file. > > This

Re: inconsistent bar number placement

Yes, exactly. Many thanks Jeffery. all best, jc > On Mar 17, 2017, at 5:49 PM, Jeffery Shivers wrote: > > If I understand, does making the following two changes do what you want? > > 1) remove bar numbers from the score: > \context {\Score >\accepts

Re: inconsistent bar number placement

On Fri, Mar 17, 2017 at 7:16 PM, Juan Cristóbal Cerrillo wrote: > Thank you Jeffery. > > If I change the TimeSignature.break-align-symbol override to #’staff-bar and > get rid of the after-line-breaking override, bar number placement is > consistent, but is too high. > >

Re: inconsistent bar number placement

Hi Juan, > If I change the TimeSignature.break-align-symbol override to #’staff-bar and > get rid of the after-line-breaking override, bar number placement is > consistent, but is too high. > Is there a way of specifying that the bar number should be placed just above > the StaffGroup bracket

Re: inconsistent bar number placement

Thank you Jeffery. If I change the TimeSignature.break-align-symbol override to #’staff-bar and get rid of the after-line-breaking override, bar number placement is consistent, but is too high. Is there a way of specifying that the bar number should be placed just above the StaffGroup bracket

Re: inconsistent bar number placement

On Fri, Mar 17, 2017 at 5:59 PM, Malte Meyn wrote: > > > Am 17.03.2017 um 22:54 schrieb Juan Cristóbal Cerrillo: >> Yes, my version is 2.18.2 >> This is what the top of page 3 looks like with ragged-right and >> ragged-bottom ##t > > The code you posted doesn’t contain

Re: inconsistent bar number placement

Am 17.03.2017 um 22:54 schrieb Juan Cristóbal Cerrillo: > Yes, my version is 2.18.2 > This is what the top of page 3 looks like with ragged-right and > ragged-bottom ##t The code you posted doesn’t contain these settings. > Are you not seeing the same? No, even if I add \paper {

Re: inconsistent bar number placement

Hello Malte, Yes, my version is 2.18.2 This is what the top of page 3 looks like with ragged-right and ragged-bottom ##t Are you not seeing the same? ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Partial

Am 17.03.2017 um 21:08 schrieb Joseph Austin: > First of all, although I did not see it in the documentation, > the form \partial DUR*NUM, such as \partial 8*5, seems to work, where NUM is > an integer multiplying DUR. > This seems to be sufficient to accommodate any arbitrary anacrusis, >

Re: inconsistent bar number placement

Am 17.03.2017 um 21:47 schrieb Juan Cristóbal Cerrillo: > the barnumber in measures 5, 6, 9 and 10 in the following example are placed > so differently as the other bar numbers. Cannot reproduce any inconsistencies. Are you sure you’re using LilyPond 2.18.2?

Re: Partial

David Kastrup writes: > u...@openlilylib.org writes: > >> Am 2017-03-17 21:48, schrieb David Kastrup: >>> Joseph Austin writes: >>> I've been experimenting with \partial, the command for scoring anacrusis, and discovered some apparently

can we pass in header variables as CLI parameters?

Hi, sorry if this has been asked before... Is it possible to pass in header variables in via the CLI? For example, I would like to pass the copyright date in via a parameter, instead of it being saved in the .LY file. This can be done in LaTeX, so I hope there is a way to do something similar

Re: Partial

u...@openlilylib.org writes: > Am 2017-03-17 21:48, schrieb David Kastrup: >> Joseph Austin writes: >> >>> I've been experimenting with \partial, the command for scoring >>> anacrusis, and discovered some apparently undocumented features. >>> >>> First of all, although I

Re: Partial

Joseph Austin writes: > I've been experimenting with \partial, the command for scoring > anacrusis, and discovered some apparently undocumented features. > > First of all, although I did not see it in the documentation, > the form \partial DUR*NUM, such as \partial 8*5,

inconsistent bar number placement

Dear all, I’m having trouble understanding why the barnumber in measures 5, 6, 9 and 10 in the following example are placed so differently as the other bar numbers. What causes this behaviour? Any help would be greatly appreciated. all best, jc \version "2.18.2" \layout { \context {\type

Partial

I've been experimenting with \partial, the command for scoring anacrusis, and discovered some apparently undocumented features. First of all, although I did not see it in the documentation, the form \partial DUR*NUM, such as \partial 8*5, seems to work, where NUM is an integer multiplying DUR.

Re: checking grob type

David Nalesnik writes: > On Fri, Mar 17, 2017 at 9:50 AM, Paul wrote: >> cc'ing lilypond-devel to move discussion there. >> >> On 03/17/2017 09:38 AM, David Nalesnik wrote: >> >>> You can get more info about public functions with the attached

Re: (Git users) Please test a Fresocbaldi Feature

Il giorno ven 17 mar 2017 alle 9:06, Urs Liska ha scritto: Hi all, there's a pull request for Frescobaldi, submitted by a new contributor (https://github.com/wbsoft/frescobaldi/pull/905), and I have a problem with it: The contributor states it works for him, I can't

Re: checking grob type

On Fri, Mar 17, 2017 at 9:50 AM, Paul wrote: > cc'ing lilypond-devel to move discussion there. > > On 03/17/2017 09:38 AM, David Nalesnik wrote: > >> You can get more info about public functions with the attached file. >> I was planning on getting documentation into the

Re: checking grob type

cc'ing lilypond-devel to move discussion there. On 03/17/2017 09:38 AM, David Nalesnik wrote: You can get more info about public functions with the attached file. I was planning on getting documentation into the manuals somehow, but I got hung up with getting the parameters of curried

Re: How to get ties between voices

- Original Message - From: "Gerard" To: Sent: Friday, March 17, 2017 12:51 PM Subject: How to get ties between voices Dear All, maybe you can help solving this problem. I've attached a code with two examples. Example 1 is the desired

Re: checking grob type

On Fri, Mar 17, 2017 at 8:38 AM, David Nalesnik wrote: > Hi, > > On Fri, Mar 17, 2017 at 7:18 AM, Urs Liska wrote: >> Hi Paul, >> >> >> Am 17.03.2017 um 13:12 schrieb Paul: >>> On 03/17/2017 07:37 AM, Urs Liska wrote: >>> I order to check

Re: checking grob type

Hi, On Fri, Mar 17, 2017 at 7:18 AM, Urs Liska wrote: > Hi Paul, > > > Am 17.03.2017 um 13:12 schrieb Paul: >> On 03/17/2017 07:37 AM, Urs Liska wrote: >> >>> I order to check arguments for its type I've written this shorthand >>> function: >>> >>> #(define (grob-type? grob

How to get ties between voices

Dear All, maybe you can help solving this problem. I've attached a code with two examples. Example 1 is the desired output, except for the missing ties in the right hand of the last quarter. Example 2 is an alternative. Now the ties are correct, but the beams between right and left hand are

Re: checking grob type

Hi Paul, Am 17.03.2017 um 13:12 schrieb Paul: > On 03/17/2017 07:37 AM, Urs Liska wrote: > >> I order to check arguments for its type I've written this shorthand >> function: >> >> #(define (grob-type? grob name) >> (eq? name (assq-ref (ly:grob-property grob 'meta) 'name))) >> >> which of

Re: checking grob type

On 03/17/2017 07:37 AM, Urs Liska wrote: I order to check arguments for its type I've written this shorthand function: #(define (grob-type? grob name) (eq? name (assq-ref (ly:grob-property grob 'meta) 'name))) which of course does what it's supposed to. But I wonder if there's a more

checking grob type

I order to check arguments for its type I've written this shorthand function: #(define (grob-type? grob name) (eq? name (assq-ref (ly:grob-property grob 'meta) 'name))) which of course does what it's supposed to. But I wonder if there's a more straightforward way, e.g. a built-in function

Re: Accessing a grob from within a music function

Hi Harm, thank you for your suggestions. I will definitely have a closer look but I've realized that I have to postpone this task because it massively interferes with a related one I'm currently at. So I'll probably only comment after some more time. Best Urs Am 17.03.2017 um 00:34 schrieb

(Git users) Please test a Fresocbaldi Feature

Hi all, there's a pull request for Frescobaldi, submitted by a new contributor (https://github.com/wbsoft/frescobaldi/pull/905), and I have a problem with it: The contributor states it works for him, I can't see anything wrong in the code, but it doesn't work for me. So I'd be happy if others