Re: Stanzas over staves

[Partitura Organum]

On 19-4-2018 22:19, Thomas Morley wrote:

The function expects `text' to be a string. So
(1) use wordwrap-string
(2) without {}


Thank you, now it works. And  I learned how to do calculations in scheme 
along the way as well. So the narrator function should be


narrator=#(define-music-function
  (dim text) (number? string?)
  #{
  s1^\markup
  \with-dimensions #(cons 0 (+ dim 2)) #'(0 . 0)
  \whiteout
  \override #(cons (quote line-width) dim)
  \translate #'(0 . -1.5)
  \wordwrap-string   #text
   #})

Regards,
Auke

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Make TOC entries available to LaTeX

[Thomas Morley]

2018-04-19 16:19 GMT+02:00 Urs Liska :
> Hi all,
>
> I'm preparing an automated edition process using LuaLaTeX, Pandoc and
> LilyPond.
>
> After some experimentation I have come to the conclusion that I'll have to
> insert the multi-movement score as a single PDF created by LilyPond (but
> through lyluatex to make use of caching and the layout mechanics).
>
> I first had used lyluatex's facility to include the score's system by system
> and print all the titles with LaTeX, but this didn't work out - for the
> first time I realized that lilypond-book-preamble.ly makes the vertical
> staff-staff spacing as tight as possible, which often makes the page layout
> pretty bad. Creating the movements separately is not an option either
> because not all movements will start on a new page.
>
> So now I have included a multi-movement score in the LaTeX document and
> don't know how to add TOC entries (in LaTeX) for the movements. I can see
> two possible ways, but don't know if they are really possible and if so how
> to approach them:
>
> Is it possible to insert something in the PDF output that LaTeX can pick up
> as TOC entries?
> (actually I doubt this is possible, but since it would be the easiest way I
> thought I'd ask anyway)
> Can I reliably retrieve the current page number of a given score's title
> block?
> With that information I could write them to a log file and read that later
> in LaTeX.
>
> TIA
> Urs
>
> PS: I don't know if it matters but the file is produced using
> ly:book-process etc.



Doesn't
http://lilypond.org/doc/v2.19/Documentation/usage-big-page#sharing-the-table-of-contents
do what you want?

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Karlin High]

On 4/19/2018 3:34 PM, David Kastrup wrote:

Correct me if I am wrong: I don't use Gmail.


Attached PNG has an annotated screenshot from the Gmail web interface.
--
Karlin High
Missouri, USA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dotted notes

[Thomas Morley]

Hi,

today I'm too tired to work on anything complicated ...
Though, some remarks:

2018-04-19 17:23 GMT+02:00 foxfanfare :
> foxfanfare wrote
> Anyway, I tried your code this morning, but I wasn't able to get the desired
> result. Maybe because I use the 2.19.80 version. I will try again later this
> afternoon.
>
> Okay I tested with the 2.19.81 version but the DotColumn.padding and
> details.dots-padding-factor doesn't seem to work.

Please post some code. so that we can debug what's wrong and why.
The code was developed with 2.19.81 so at least the example works for me.

> On the contrary, the dots
> doesn't collide with the stems anymore!

Really?
I still see a collision with

\paper {
  #(define fonts
(set-global-fonts
  #:music "beethoven"
  #:brace "beethoven"
  #:factor (/ staff-height pt 20)))
}

{ d'16.. }

> But don't worry Harm, since the
> solution seems to be very difficult to implement and as you said "fragile",

"Difficult" doesn't scare me, Au contraire. Anything else is boring :)

> I will probably let the default output for the dots-dots placement. Too bad,
> this was an option in Sibelius! I guess I'll wait for a next LilyPond
> version which may (or not!) implement this!

This code (\dotsAndDotColumnPadding) will most likely never been
implemented in the source.

Postprocessing a delivered stencil is a _method_ I sometimes use, when
no other method sounds doable.

What should be documented?
- get the stencil-expression
- do the wished modifications with appropriate procedures
- set 'stencil to a new stencil with this new stencil-expression and
appropriate extents
That's all :)

As said, it's a method. Of sort 'last resort' :)

Though, it would be nice to have some user-settable grob-properties :
Probably a padding-property to adjust the space between NoteColumn and
DotColumn and a dot-padding-property to adjust the space between the
dots themselves.


Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

> Correct me if I am wrong: I don't use Gmail.

Gmail completely hides previous messages by default, you have to
manually show them, which is not standard use or google would not hide
it.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[David Kastrup]

Robert Hickman  writes:

>> Also, the LilyPond mailing list rules frown on top-posting.  Please
>> use inline quoting instead.
>
> That is how gmail works by default,

If you mean that it leaves you with the cursor at the start of the fully
quoted material: sure, how else would it prepare you for inline quoting?

It would still appear to be a user choice to just type a reply there and
hit send without doing any editing.

Correct me if I am wrong: I don't use Gmail.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Stanzas over staves

[Thomas Morley]

2018-04-19 21:09 GMT+02:00 Partitura Organum :
>
>
> On 19-4-2018 00:30, Simon Albrecht wrote:
>>
>> You have to quote line-width because it’s a symbol, not a variable. That
>> can also be done in a verbose or in a practical way:
>> \override #(cons 'line-width dim)
>> or
>> \override #(cons (quote line-width) dim).
>> The two are exactly equivalent.
>
>
> The second is new for me, nice to learn. The first form I did try (after
> having found out about cons). It does compile, but it does not work.
> Somehow, inside a scheme function the 'line-width argument does not point to
> the actual line-width property of the markup being constructed.
>
> I.e. this does work as intended:
>
> scoreAUpperHarpI = \relative c'' {
> \once\override TextScript.extra-spacing-width = #'(0 . 0)
> s1^\markup
>  \with-dimensions #'(0 . 22) #'(0 . 0)
>  \whiteout \override #'(line-width . 20)
>  \translate #'(0 . 0)
>  \wordwrap   { Ah, how oft we read or hear of  Boys we almost stand in
> fear of!  For example, take these stories
>}
> }
>
> scoreALowerHarpI = \relative c' { s1  }
>
> scoreAHarpIPart = \new PianoStaff \with {
>   instrumentName = "Harfe I"
> } <<
>   \new Staff = "upper" \scoreAUpperHarpI
>   \new Staff = "lower" { \clef bass \scoreALowerHarpI }
>>>
>
> \score {
>   <<
> \scoreAHarpIPart
>   >>
>   \layout { }
> }
>
>
> However, when transforming this into a scheme function the line-width and
> wordwrap do not work as intended:
>
> narrator=#(define-music-function
>   (parser location dim text) (number? string?)
>
>#{
>   \override TextScript.extra-spacing-width = #'(0 . -0.50)
>  s1^\markup
>   \with-dimensions #(cons 0 dim) #'(0 . 0)
>   \whiteout
>   \override #(cons (quote line-width) dim)
>   \translate #'(0 . -1.5)
>   \wordwrap {  #text }

The function expects `text' to be a string. So
(1) use wordwrap-string
(2) without {}

>#})
>
> scoreAUpperHarpII = \relative c'' {
>   \narrator#30 "Of named Max and Moritz, Who, instead of early turning
> etcetc"
>  }
>
> scoreALowerHarpII= \relative c' { s1  }
>
> scoreAHarpIIPart = \new PianoStaff \with {
>   instrumentName = "Harfe II"
> } <<
>   \new Staff = "upper" \scoreAUpperHarpII
>   \new Staff = "lower" { \clef bass \scoreALowerHarpII }
>>>
>
> \score {
>   <<
> \scoreAHarpIIPart
>   >>
>   \layout { }
> }
>
> How should the function be constructued toi make this work an intended?
>
> Regards,
> Auke
>



Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

> As described in the Learning Manual, which has been suggested that you read, 
> \once applies to everything happening at that musical moment; \tweak applies 
> to only the object containing the \tweak.
>
> http://lilypond.org/doc/v2.19/Documentation/learning/tweaking-methods
>
> You really *should* take the time to read carefully through the Learning 
> Manual, rather than just trying to figure things out by looking at examples.  
> It will save you time in both the short and the long run.
>

I have read the learning manual but was not clear on that issue.


> Also, the LilyPond mailing list rules frown on top-posting.  Please use 
> inline quoting instead.

That is how gmail works by default, and I was not aware of that rule.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Stanzas over staves

[Partitura Organum]

On 19-4-2018 00:30, Simon Albrecht wrote:
You have to quote line-width because it’s a symbol, not a variable. 
That can also be done in a verbose or in a practical way:

\override #(cons 'line-width dim)
or
\override #(cons (quote line-width) dim).
The two are exactly equivalent. 


The second is new for me, nice to learn. The first form I did try (after 
having found out about cons). It does compile, but it does not work. 
Somehow, inside a scheme function the 'line-width argument does not 
point to the actual line-width property of the markup being constructed.


I.e. this does work as intended:

scoreAUpperHarpI = \relative c'' {
    \once\override TextScript.extra-spacing-width = #'(0 . 0)
    s1^\markup
 \with-dimensions #'(0 . 22) #'(0 . 0)
 \whiteout \override #'(line-width . 20)
 \translate #'(0 . 0)
 \wordwrap   { Ah, how oft we read or hear of  Boys we almost stand 
in fear of!  For example, take these stories

   }
}

scoreALowerHarpI = \relative c' { s1  }

scoreAHarpIPart = \new PianoStaff \with {
  instrumentName = "Harfe I"
} <<
  \new Staff = "upper" \scoreAUpperHarpI
  \new Staff = "lower" { \clef bass \scoreALowerHarpI }
>>

\score {
  <<
    \scoreAHarpIPart
  >>
  \layout { }
}


However, when transforming this into a scheme function the line-width 
and wordwrap do not work as intended:


narrator=#(define-music-function
  (parser location dim text) (number? string?)

   #{
  \override TextScript.extra-spacing-width = #'(0 . -0.50)
 s1^\markup
  \with-dimensions #(cons 0 dim) #'(0 . 0)
  \whiteout
  \override #(cons (quote line-width) dim)
  \translate #'(0 . -1.5)
  \wordwrap {  #text }
   #})

scoreAUpperHarpII = \relative c'' {
  \narrator#30 "Of named Max and Moritz, Who, instead of early turning 
etcetc"

 }

scoreALowerHarpII= \relative c' { s1  }

scoreAHarpIIPart = \new PianoStaff \with {
  instrumentName = "Harfe II"
} <<
  \new Staff = "upper" \scoreAUpperHarpII
  \new Staff = "lower" { \clef bass \scoreALowerHarpII }
>>

\score {
  <<
    \scoreAHarpIIPart
  >>
  \layout { }
}

How should the function be constructued toi make this work an intended?

Regards,
Auke


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dotted notes

[foxfanfare]

foxfanfare wrote
> Anyway, I tried your code this morning, but I wasn't able to get the
> desiredresult. Maybe because I use the 2.19.80 version. I will try again
> later thisafternoon.

Okay I tested with the 2.19.81 version but the DotColumn.padding and
details.dots-padding-factor doesn't seem to work. On the contrary, the dots
doesn't collide with the stems anymore! But don't worry Harm, since the
solution seems to be very difficult to implement and as you said "fragile",
I will probably let the default output for the dots-dots placement. Too bad,
this was an option in Sibelius! I guess I'll wait for a next LilyPond
version which may (or not!) implement this!



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Make TOC entries available to LaTeX

[Jan-Peter Voigt]

Hi Urs, I don't know either how to extract the toc from the PDF. But it should 
be easy to write the toc into some text file. Recently I did something similar 
to provide that info to those who compiled a book in inDesign.
I will extract it later, when I am back at my Workstation.

Jan-Peter 

Am 19. April 2018 16:19:49 MESZ schrieb Urs Liska :
>Hi all,
>
>I'm preparing an automated edition process using LuaLaTeX, Pandoc and 
>LilyPond.
>
>After some experimentation I have come to the conclusion that I'll have
>
>to insert the multi-movement score as a single PDF created by LilyPond 
>(but through lyluatex to make use of caching and the layout mechanics).
>
>I first had used lyluatex's facility to include the score's system by 
>system and print all the titles with LaTeX, but this didn't work out - 
>for the first time I realized that lilypond-book-preamble.ly makes the 
>vertical staff-staff spacing as tight as possible, which often makes
>the 
>page layout pretty bad. Creating the movements separately is not an 
>option either because not all movements will start on a new page.
>
>So now I have included a multi-movement score in the LaTeX document and
>
>don't know how to add TOC entries (in LaTeX) for the movements. I can 
>see two possible ways, but don't know if they are really possible and
>if 
>so how to approach them:
>
>  * Is it possible to insert something in the PDF output that LaTeX can
>pick up as TOC entries?
>(actually I doubt this is possible, but since it would be the
>easiest way I thought I'd ask anyway)
>  * Can I reliably retrieve the current page number of a given score's
>title block?
>   With that information I could write them to a log file and read that
>later in LaTeX.
>
>TIA
>Urs
>
>PS: I don't know if it matters but the file is produced using 
>ly:book-process etc.

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Make TOC entries available to LaTeX

[Urs Liska]

Hi all,

I'm preparing an automated edition process using LuaLaTeX, Pandoc and 
LilyPond.


After some experimentation I have come to the conclusion that I'll have 
to insert the multi-movement score as a single PDF created by LilyPond 
(but through lyluatex to make use of caching and the layout mechanics).


I first had used lyluatex's facility to include the score's system by 
system and print all the titles with LaTeX, but this didn't work out - 
for the first time I realized that lilypond-book-preamble.ly makes the 
vertical staff-staff spacing as tight as possible, which often makes the 
page layout pretty bad. Creating the movements separately is not an 
option either because not all movements will start on a new page.


So now I have included a multi-movement score in the LaTeX document and 
don't know how to add TOC entries (in LaTeX) for the movements. I can 
see two possible ways, but don't know if they are really possible and if 
so how to approach them:


 * Is it possible to insert something in the PDF output that LaTeX can
   pick up as TOC entries?
   (actually I doubt this is possible, but since it would be the
   easiest way I thought I'd ask anyway)
 * Can I reliably retrieve the current page number of a given score's
   title block?
   With that information I could write them to a log file and read that
   later in LaTeX.

TIA
Urs

PS: I don't know if it matters but the file is produced using 
ly:book-process etc.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Carl Sorensen]

On 4/19/18, 3:52 AM, "Robert Hickman"  wrote:

Thanks, as far as I can see lilyponds modification system is based on
a stack based state machine, \override permanently changes that state
while \tweak only changes it once. Where would you use \tweak vs \once
as they appear to do the same thing?

As described in the Learning Manual, which has been suggested that you read, 
\once applies to everything happening at that musical moment; \tweak applies to 
only the object containing the \tweak.

http://lilypond.org/doc/v2.19/Documentation/learning/tweaking-methods

You really *should* take the time to read carefully through the Learning 
Manual, rather than just trying to figure things out by looking at examples.  
It will save you time in both the short and the long run.

Also, the LilyPond mailing list rules frown on top-posting.  Please use inline 
quoting instead.

Thanks,

Carl


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Trouble with trill spanner avoiding slur

[Kieren MacMillan]

Hi Knute,

> Is this a bug, or is the intended behavior that the slur be shaped?

Looks like a bug to me…

Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Trouble with trill spanner avoiding slur

[Knute Snortum]

I'll only bump this once, I promise.

Is this a bug, or is the intended behavior that the slur be shaped?


---
Knute Snortum
(via Gmail)

On Tue, Apr 17, 2018 at 5:05 PM, Knute Snortum  wrote:

> In this example...
>
> %%% Start
> \version "2.19.81"
> \language "english"
>
> {
>   \override TrillSpanner.avoid-slur = #'inside
>   \override TrillSpanner.outside-staff-priority = ##f
>   c''1( | c''2. \startTrillSpan c''4 \stopTrillSpan | c''1) |
> }
> %%% End
>
> ...the slur doesn't avoid the trill spanner.  Do I need to adjust the slur
> with \shape or is the slur supposed to adjust its position automatically?
>
> ---
> Knute Snortum
> (via Gmail)
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[David Kastrup]

Robert Hickman  writes:

> Thanks, as far as I can see lilyponds modification system is based on
> a stack based state machine, \override permanently changes that state
> while \tweak only changes it once. Where would you use \tweak vs \once
> as they appear to do the same thing?





-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Robert Hickman]

Thanks, as far as I can see lilyponds modification system is based on
a stack based state machine, \override permanently changes that state
while \tweak only changes it once. Where would you use \tweak vs \once
as they appear to do the same thing?

On 19 April 2018 at 07:55, Mark Knoop  wrote:
> At 17:38 on 18 Apr 2018, Robert Hickman wrote:
>>Tried using "\override TextScript.staff-padding" to move the text
>>annotations in the attached image up but it also moves the Larson
>>articulation symbols up as well. I want these to stay in the same
>>place and the text to move up a bit away from them. Is lilypond
>>treating the articulation symbols as text?
>>
>>\header {tagline = ""}
>>
>>{
>>\override TextScript.staff-padding = #5
>>\numericTimeSignature
>>\time 3/8
>>
>>g'4.\cut^\markup {\tiny Cut } |  g'4.\strike^\markup {\tiny
>> Strike } |
>>}
>
> Use \tweak instead of \override, viz:
>
> {
> \numericTimeSignature
> \time 3/8
>
> g'4.\cut -\tweak staff-padding #5 ^\markup {\tiny Cut } |
> g'4.\strike -\tweak staff-padding #5 ^\markup {\tiny Strike } |
> }
>
> --
> Mark Knoop
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lyLuaTeX, still troubles

[David Kastrup]

Federico Bruni  writes:

> Il giorno mer 18 apr 2018 alle 18:37, Urs Liska
>  ha scritto:
>>
>> When you write \begin{lilypond}[] (note the square brackets) your
>> second example compiles.
>>
>> This recalls two separate issues we were struggling with (both of
>> which I haven't understood or touched):
>> a need to add an empty optional argument.
>> This has reportedly been fixed, but it seems not for every case.
>> Having some LaTeX keywords in the LilyPond code, IIRC \repeat was
>> among them.
>> I have the impression these two "work" together here.
>>
>> It would be good if you'd create an issue  on the tracker with the
>> examples.
>>
>
> I confirm your analysis: \repeat causes the error, unless [] is used.
>
> I found this issue:
> https://github.com/jperon/lyluatex/issues/51
>
> which was supposed to be fixed by this commit:
> https://github.com/jperon/lyluatex/pull/53/commits/01b9cd10aed6c118d19e337db29e049f20bc21af
>
> I've opened a new issue here:
> https://github.com/jperon/lyluatex/issues/194

The problem is that \repeat is equivalent to \fi in TeX/LaTeX in order
to allow for things like

\iffalse \loop \ifnum 3<2 ... \repeat \fi

to have matched conditionals.  That means that likely your lylatex code
uses something like

\if...  LilyPond code  \fi

somewhere.  The LilyPond code now contains an unmatched \fi and stuff
goes haywire.  The solution is to _never_ put it into conditionals.
Instead you use something like

\if... \expandafter \@firstoftwo \else \expandafter \@secondoftwo \fi
{LilyPond code} {alternative code}

and thus neither skipping or using the LilyPond code relies on matches
conditionals inside.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dotted notes

[foxfanfare]

Thomas Morley-2 wrote
> Hi,
> 
> obviously the flags from the beethoven-font have less y-extent.
> Sometimes too less, so DotColumn doesn't notice there's flag which
> should be avoided.
> (I've cc-ed the original author of the font. Maybe he joins the
> discussion.)
> 
> To watch the values uncomment
> \printFontFlagYExtent
> in the test-code below.
> 
> Additionally I wrote some procedures to deal with this problem as well
> as to get access and manipulate the dots of a DotColumn.
> Per default most work is done in C++ and locked from the user, though
> with a little trickery there's a way.
> 
> (1) The too short flags form beethoven-font may be corrected with
> \tallerBeethovenFlags
> (2) Alternatively you can move the DotColumn with \moveBeethovenDotColumn
> 
> Both functions are limited to beethoven-font, they will have no impact
> on other fonts
> 
> (3) \dotsAndDotColumnPadding is the most generic one.
> Put it in layout and add
> \override Staff.DotColumn.padding = 
> 
> and/or
> \override Staff.DotColumn.details.dots-padding-factor = 
> 
> where you want.
> Both properties will influence each other.
> 
> Be aware, although it's the most generic one, it is also the most fragile
> one:
> Because Dots in DotColumn are processed in C++ and only very few
> grob-properties are accessible we have little chance to customize it,
> apart from post-processing the ready stencil. A tedious and involved
> work. This also means: if LilyPond internals change,
> \dotsAndDotColumnPadding may break.

... :O 
Amazing... First, thank you very much for the time you spent working on this
issue. When I asked my question, I thought I'll receive a simple answer :
yes it is possible with this command... or no, not possible. 

Since I've started learn LilyPond, it would appear that almost evry details
can be personalized. That's why I am currently tring to get more in depth
with all the commands in order to make my output as clean as it was when I
used other major softwares.

That's why I was surprised that no commands existed for this customization.
But I didn't even imagined someone could just create a new one! I hope it
didn't ask you too much time... Once again, a simple "no, not possible for
the moment" would already have been enough!

Anyway, I tried your code this morning, but I wasn't able to get the desired
result. Maybe because I use the 2.19.80 version. I will try again later this
afternoon.

This kind of feature, especially \dotsAndDotColumnPadding, now that it is
written, could it be now implemented in a future version or is it something
a lot more complicated than that?

Thank you again,
Cheers.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: temporarily disable Dot_column_engraver?

[foxfanfare]

Thomas Morley-2 wrote
> It's not possible to consist/remove engraver temporarily, but you can
> have several named Voices (keep them alive) with and without the
> engraver:

Thank you for your answer. That's too bad this feature isn't available it
would obviously get things easier!

Anyway, thank you for this exemple, it's a good thing to know it is doable.
However, I wonder if in a score, I'll prefer this voicing solution or if it
wouldn't be faster to just move the dots...



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lyLuaTeX, still troubles

[Federico Bruni]

Il giorno mer 18 apr 2018 alle 18:37, Urs Liska  
ha scritto:



Am 18.04.2018 um 18:20 schrieb Urs Liska:


Am 18. April 2018 18:10:13 MESZ schrieb Federico Bruni 
:

Hi folks

I'm still having a problem with lyluatex...
I've installed native TeX Live 2017 on Fedora 27. I've compiled
successfully a few examples, including the test files and the 
manual in


lyluatex repository.

Any idea of why testing.tex compiles fine while broken.tex fails?

Does using the nofragment option make a difference?




When you write \begin{lilypond}[] (note the square brackets) your 
second example compiles.


This recalls two separate issues we were struggling with (both of 
which I haven't understood or touched):

a need to add an empty optional argument.
This has reportedly been fixed, but it seems not for every case.
Having some LaTeX keywords in the LilyPond code, IIRC \repeat was 
among them.

I have the impression these two "work" together here.

It would be good if you'd create an issue  on the tracker with the 
examples.




I confirm your analysis: \repeat causes the error, unless [] is used.

I found this issue:
https://github.com/jperon/lyluatex/issues/51

which was supposed to be fixed by this commit:
https://github.com/jperon/lyluatex/pull/53/commits/01b9cd10aed6c118d19e337db29e049f20bc21af

I've opened a new issue here:
https://github.com/jperon/lyluatex/issues/194




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Moving just text, leaving articulations in place?

[Mark Knoop]

At 17:38 on 18 Apr 2018, Robert Hickman wrote:
>Tried using "\override TextScript.staff-padding" to move the text
>annotations in the attached image up but it also moves the Larson
>articulation symbols up as well. I want these to stay in the same
>place and the text to move up a bit away from them. Is lilypond
>treating the articulation symbols as text?
>
>\header {tagline = ""}
>
>{
>\override TextScript.staff-padding = #5
>\numericTimeSignature
>\time 3/8
>
>g'4.\cut^\markup {\tiny Cut } |  g'4.\strike^\markup {\tiny
> Strike } |
>}

Use \tweak instead of \override, viz:

{
\numericTimeSignature
\time 3/8

g'4.\cut -\tweak staff-padding #5 ^\markup {\tiny Cut } |  
g'4.\strike -\tweak staff-padding #5 ^\markup {\tiny Strike } |
}

-- 
Mark Knoop

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user