Re: Clef modifier vertical position

2017-01-09 Thread Pierre Perol-Schneider
+1, I'd use extra-offset too.

You could also do:

\version "2.18.2"
\layout {
  \context {
\Staff
\clef "F_8"
\override ClefModifier.staff-padding = #'()
%\override ClefModifier.padding = #.6
  }
} { c }

Cheers,
Pierre


2017-01-10 6:28 GMT+01:00 Urs Liska :

>
>
> Am 10. Januar 2017 04:26:01 MEZ schrieb Andrew Bernard <
> andrew.bern...@gmail.com>:
> >I am using clefs of type "bass_8". We would like to have the 8 directly
> >under the clef glyph rather than under the staff. Using the
> >clef-alignments
> >property of ClefModifier, there does not seem to be the ability to move
> >the
> >numeral up or down, only sideways, Any suggestions anybody?
>
> Isn't this a case for extra-offset?
>
> Urs
> >
> >Andrew
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.
>
> ___
> 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: Clef modifier vertical position

2017-01-09 Thread Urs Liska


Am 10. Januar 2017 04:26:01 MEZ schrieb Andrew Bernard 
:
>I am using clefs of type "bass_8". We would like to have the 8 directly
>under the clef glyph rather than under the staff. Using the
>clef-alignments
>property of ClefModifier, there does not seem to be the ability to move
>the
>numeral up or down, only sideways, Any suggestions anybody?

Isn't this a case for extra-offset?

Urs
>
>Andrew

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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


Re: Clef modifier vertical position

2017-01-09 Thread tisimst
On Mon, Jan 9, 2017 at 8:27 PM Andrew Bernard [via Lilypond] <
ml-node+s1069038n199048...@n5.nabble.com> wrote:

>
>
>
>
> I am using clefs of type "bass_8". We would like to have the 8 directly
> under the clef glyph rather than under the staff. Using the clef-alignments
> property of ClefModifier, there does not seem to be the ability to move the
> numeral up or down, only sideways, Any suggestions anybody?
>
> Andrew
>
I know it's not ideal, but extra-offset has worked for me.

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Clef-modifier-vertical-position-tp199048p199049.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Clef modifier vertical position

2017-01-09 Thread Andrew Bernard
I am using clefs of type "bass_8". We would like to have the 8 directly
under the clef glyph rather than under the staff. Using the clef-alignments
property of ClefModifier, there does not seem to be the ability to move the
numeral up or down, only sideways, Any suggestions anybody?

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


Re: init.ly, what does it do?

2017-01-09 Thread Thomas Morley
2017-01-09 4:29 GMT+01:00 David Wright :
> On Sun 08 Jan 2017 at 21:17:53 (-0500), Br. Samuel Springuel wrote:
>
>> With this file saved to the same folder as my test score,
>> `lilypond-dev --init="my_init.ly" test.ly` produces identical
>> results to `lilypond-dev test.ly`.  I would, therefore, guess that
>> while LilyPond has initialized enough for the code to make sense
>> (i.e. not cause errors the way putting this stuff in an `-e`
>> argument on the command-line does), my_init.ly is still getting
>> executed too early because the settings in it are being overwritten
>> by their default values.
>>
>> So, unless there is a hook somewhere accessible to either `-e` or
>> `--init` that I can use to get the code executed at the right time
>> (i.e. after LilyPond is finished setting the default values but
>> before she actually starts interpreting test.ly), or some way to
>> protect the settings in `my_init.ly` so that LilyPond doesn't/can't
>> change them later, I'm going to have to do something that requires
>> editing the source file before it can be used.
>>
>> Here's hoping someone can prove me wrong.
>
> Well, Simon gave an example where you invoke LP on the
> variable-contents file and include the fixed-contents file.
> Just as easy is to invert this: invoke LP on the fixed-contents file
> (your "source" file) but include a variable-contents file (your
> "my_init.ly" file).
>
> How to do this: just put
> \include "my_init.ly"
> at the start of your source file.
>
> Editing my_init.ly and reinvoking LP on the (unchanged) source file
> will produce a new version of the output using whatever is defined in
> my_init.ly.
>
> You wrote "With separate files, every time I play with the document
> settings, I have to create a new file which has the appropriately
> matched settings and redirect the document to the new file (assuming I
> want to be able to go back to the original settings at some point)."
>
> If you want to preserve previous settings that you've used in
> "my_init.ly" in the past, you can create each my_init.ly in a
> directory whose name is a timestamp like 2017-01-08-20-59-30.¹
>
> Your invocation would use   --include="path/to/2017-01-08-20-59-30"
> to make LP find and insert the appropriate version from that
> directory. Your source would remain unchanged.
>
> Just make sure that you don't put a file called my_init.ly in any
> other directory from which you pick up \include files, ie your
> repositories of LP/scheme code, so that it will only ever be found
> in the timestamped directory.
>
> You also wrote "When borrowing source from other people, however, the
> appropriate Scheme variables won't be there." I don't know what you
> mean by borrowing source. You'd have to explain how you incorporate
> this borrowed code into your projects.
>
> ¹ or any other systematic naming of the directories.
>
> Cheers,
> David.

Samuel,

I'd likely go for --include as David recommended.

Nevertheless, you could store the following lines at top of the ly-file

#(use-modules (guile-user))

#(if (not (defined? 'my-settings))
 (define my-settings '()))

#(for-each
  (lambda (settings)
(ly:output-def-set-variable! $defaultpaper (car settings) (cdr settings)))
  my-settings)

Then you can call lilypond with
$ lilypond -e='(define my-settings (list (cons (quote indent) 10)(cons
(quote short-indent) 10)(cons (quote line-width) 80)))' file.ly

On windows use double quotes.

Ofcourse you now can use different key-value-pairs in my-settings.
Or even no settings:
$ lilypond file.ly
will still work.

Please note
(1) In terminal spell-out list, cons, quote don't use '-signs
(2) A warning is printed:
WARNING: #f: imported module (guile-user) overrides core binding
`%module-public-interface'
No clue about its severity.


Cheers,
  Harm

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


Re: text categories in scores

2017-01-09 Thread Simon Albrecht

On 09.01.2017 21:17, Noeck wrote:

Hi Simon, all,

next to the notes, there are usually these kinds of texts:

1 tempo: bold, above the staff
Above the top staff, that is, and maybe above other staves/staff groups 
in larger scorings or piano reductions.

Agogic marks may all be bold, only some, or none.

2 dynamics: in italics, below the staff (depends on the instrument etc.)
3 articulation
4 other

Examples:
1 Allegro, Tempo I, …
2 dolce, dim., cresc., …
3 dolce, staccato, …
4 m.d., simile, …

As mentioned in this thread, some tempo-related expressions are often
written in a different category from what would be logical:
rit. accel. a tempo written like category-2-expressions.

a) Why is that the case? Is there a historical reason for that?
First of all: historically as well as in one piece, those categories are 
(usually) difficult to entirely separate:
– Tempo markings as well as agogic markings may only appear on one 
staff/part and not the others.

– Is ‘smorzando’ agogic or dynamic? There are different opinions.
– As you wrote yourself: ‘dolce’ affects more than one parameter as well.


b) Would you recommend to stick to this (rit = category 2) or would you
recommend to separate tempo from other categories?
I think one should strive for a semantic differentiation, i.e. use 
MetronomeMark grobs for "rit." and the like, but within reason.

c) Are there correct/scientific categories and terms for these categories
close to mine above (1-4)?
I guess every typography teacher and every house style may have a 
slightly different system of categories…


Just my 2cts :-)

Best, Simon

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


text categories in scores (was: Changing midi-tempo within score)

2017-01-09 Thread Noeck
Hi Simon, all,

next to the notes, there are usually these kinds of texts:

1 tempo: bold, above the staff
2 dynamics: in italics, below the staff (depends on the instrument etc.)
3 articlulation
4 other

Examples:
1 Allegro, Tempo I, …
2 dolce, dim., cresc., …
3 dolce, staccato, …
4 m.d., simile, …

As mentioned in this thread, some tempo-related expressions are often
written in a different category from what would be logical:
rit. accel. a tempo written like category-2-expressions.

a) Why is that the case? Is there a historical reason for that?

b) Would you recommend to stick to this (rit = category 2) or would you
recommend to separate tempo from other categories?

c) Are there correct/scientific categories and terms for these categries
close to mine above (1-4)?

Cheers,
Joram

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


Re: help with frameEngraver-bars-and-boxes function

2017-01-09 Thread James.Correa
Thanks David and Holland!! It is working now.
All the best,

James










 Original Message 
Subject: Re: help with frameEngraver-bars-and-boxes function
Local Time: January 9, 2017 12:48 PM
UTC Time: January 9, 2017 2:48 PM
From: david.nales...@gmail.com
To: holl...@hollandhopson.com 
lilypond-user@gnu.org 

On Mon, Jan 9, 2017 at 8:32 AM, holl...@hollandhopson.com
 wrote:
>
> On Jan 8, 2017, at 5:39 PM, James.Correa 
> wrote:
>
> Hi,
>
> This is my first time writing on the list. I have using lilypond for a few
> months, and I find in the list archive a function written by David Nalesnik
> that is exactly what I need for my score. It compiles ok on Lilypond 2.18.2,
> but I am using 2.19.53 for my score and I am getting this warnings:
> Starting lilypond 2.19.53 [frameEngraver-boxes-and-repeats-example.ly]...
> Processing
> `/Users/jamescorrea/Downloads/frameEngraver-boxes-and-repeats-example.ly'
> Parsing...
> warning: type check for `FrameStub' failed; value `#' must
> be of type `list'
> warning: type check for `FrameBracket' failed; value `#'
> must be of type `list'
> warning: type check for `FrameExtender' failed; value `#'
> must be of type `list'
> warning: type check for `Frame' failed; value `#' must be
> of type `list'
> Interpreting music...
> Exited with exit status 1.
>
> My code skills aren't enough to fix it. Can someone help me?
> I am attaching the .ily file, I hope the author will be ok with.
> Thanks in advance!!!
>
>
> Hi James,
> Here’s a tidbit I filed away the last time frameEngraver was discussed:
> "
> ...should mention that this needs 2.18.x There is a single change which you
> need for current development versions. See the last line below:
>
> % ADD NEW GROB DEFINITIONS
> %
>
> #(define (add-grob-definition grob-name grob-entry)
> (let* ((meta-entry (assoc-get 'meta grob-entry))
> (class (assoc-get 'class meta-entry))
> (ifaces-entry (assoc-get 'interfaces meta-entry)))
> (set-object-property! grob-name 'translation-type? ly:grob-properties?)
> ;; NB!!
> “
>
> I think this was Nalesnik speaking. I don’t know enough to say that this
> will fix the problem, but I hope it helps. I've used frameEngraver
> extensively, so I want to see it continue to function!
> Best,
> Holland
>

Yes, me speaking :) This should fix the problem.

David

___
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: lilypond and rosegarden : control track (?) in midi output? (linux user)

2017-01-09 Thread Federico Bruni
Il giorno lun 9 gen 2017 alle 16:24, Dario Marrini 
 ha scritto:
I'm trying to create a orchester midi file using lilypond as source 
notation and rosegarden; I have some trouble using rosegarden jack 
and so on (I'm using linux), but I came to a working two strings 
tracks with two fluidsynth instances, so I can manage Violin I on the 
left and Violin II on the right.


I can't figure out the presence of a 'control track' when I import 
the midi files (outputted by lilypond) in rosegarden, as there is a 
staff only in lilypond, so do I have a single midi channel, right? I 
dont' know if it is a lilypond or rosegarden way of working.

Please help


What you see is the sequence name. In 2.18.2 "control track" was the 
default:


$ timidity test.midi
Playing test.midi
MIDI file: test.midi
Format: 1 Tracks: 2 Divisions: 384
Sequence: control track
Text: creator:
Text: GNU LilyPond 2.18.2

If you use the last development version (2.19), you'll see the text 
assigned to the title in your \header (you won't see anything if it's 
not set).


As you can read in the Changes:
http://lilypond.org/doc/v2.19/Documentation/changes/index.html

"When outputting MIDI, LilyPond will now store the title defined in a 
score’s \header block (or, if there is no such definition on the 
\score level, the first such definition found in a \header block of the 
score’s enclosing \bookpart, \book, or top-level scope) as the name 
of the MIDI sequence in the MIDI file. Optionally, the name of the MIDI 
sequence can be overridden using the new midititle \header field 
independently of title (for example, in case title contains markup code 
which does not render as plain text in a satisfactory way 
automatically)."


Don't know how to work around this in version 2.18.2.
This was the discussion which lead to the patch:
http://lists.gnu.org/archive/html/lilypond-user/2015-08/msg00062.html




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


lilypond and rosegarden : control track (?) in midi output? (linux user)

2017-01-09 Thread Dario Marrini
Hi everybody,

I'm trying to create a orchester midi file using lilypond as source
notation and rosegarden; I have some trouble using rosegarden jack and so
on (I'm using linux), but I came to a working two strings tracks with two
fluidsynth instances, so I can manage Violin I on the left and Violin II on
the right.

I can't figure out the presence of a 'control track' when I import the midi
files (outputted by lilypond) in rosegarden, as there is a staff only in
lilypond, so do I have a single midi channel, right? I dont' know if it is
a lilypond or rosegarden way of working.
Please help
thanks
bye

dario

here is a screenshot's link :

https://drive.google.com/open?id=0B83dBSxPEiOoUmxXcUR4QnQwbms
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Extracting symbol location

2017-01-09 Thread David Nalesnik
Lukas,

On Mon, Jan 9, 2017 at 8:43 AM, David Nalesnik  wrote:

> The new output-attibutes property allows you to create multiple
> attributes, so why not adapt the labeling routines to return something
> like
>
> value of output-attributes = '((name . someGrob) (moment . whenIAm)
> (x-pos . xCoordinate) (y-pos . yCoordinate))

A way to do this is attached.

An excerpt from the SVG:



-David
\version "2.19.49"

% angle brackets cause SVG error so reformat:
% # becomes [Mom 1]
#(define (reformat-moment mom)
   (let* ((mom (format #f "~a" mom))
  (mom (string-drop mom 2))
  (mom (string-drop-right mom 1)))
 (string-concatenate (list "[" mom "]"

% grob name + absolute moment + (system) coordinates should be enough for a unique id...
#(define (get-unique-id grob)
   (let ((sys (ly:grob-system grob)))
 (list
  (cons 'name
(symbol->string (grob::name grob)))
  (cons 'when
(reformat-moment (grob::when grob)))
  (cons 'x-pos
(number->string (ly:grob-relative-coordinate grob sys X)))
  (cons 'y-pos
(number->string (ly:grob-relative-coordinate grob sys Y))

assignIDs =
#(let ((grob-names (map car all-grob-descriptions)))
   #{
 #@(map (lambda (x) #{
   \override #(list 'Score x 'output-attributes) = #get-unique-id
   #})
 grob-names)
   #})
{
  \assignIDs
  a1
  \break
  a
  \break
  a
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Extracting symbol location

2017-01-09 Thread David Nalesnik
On Mon, Jan 9, 2017 at 4:55 AM, Lukas Tuggener  wrote:
> Hi David
>
> When I tried to use your very useful script on a fresh installation it didnt
> work anymore. I suspect it is due to the change you already mentioned in
> your first message:
>
> There's a patch being reviewed which replaces the 'id property with
> 'output-properties and this will need to be updated accordingly
> (https://sourceforge.net/p/testlilyissues/issues/4974/).
>
>
> I tried to uptdate the script, but didnt get it to work so far. I assume the
> updated assignIDs function should look something like this:
>
> assignIDs = #(let ((grob-names (map car all-grob-descriptions)))
>#{
>  #@(map (lambda (x)#{ \override #(list 'Score x (assoc-get 'id
> output-attributes) = #get-unique-id #})
>  grob-names)
>#})
>
> For any hint where I went wrong i would be very grateful.

Before I give a solution, two observations:

(1) you're missing a close parenthesis before the equals.

(2) there is no variable called "output-attributes" which you can
treat as an alist by applying assoc-get: it is a symbol (needing a
single-quote to reference).

The \override command we would model to change an "id" property nested
in an "output-attributes" property is:

\override Score.someGrob.output-attributes.id = #get-unique-id

and that translates to this definition of assignIDs:

assignIDs =
#(let ((grob-names (map car all-grob-descriptions)))
   #{
 #@(map (lambda (x) #{
   \override #(list 'Score x 'output-attributes 'id) = #get-unique-id
   #})
 grob-names)
   #})

%%%

The new output-attibutes property allows you to create multiple
attributes, so why not adapt the labeling routines to return something
like

value of output-attributes = '((name . someGrob) (moment . whenIAm)
(x-pos . xCoordinate) (y-pos . yCoordinate))

Would this be something you could use in your post-processing?

HTH,
David

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


Re: help with frameEngraver-bars-and-boxes function

2017-01-09 Thread David Nalesnik
On Mon, Jan 9, 2017 at 8:32 AM, holl...@hollandhopson.com
 wrote:
>
> On Jan 8, 2017, at 5:39 PM, James.Correa 
> wrote:
>
> Hi,
>
> This is my first time writing on the list. I have using lilypond for a few
> months, and I find in the list archive a function written by David Nalesnik
> that is exactly what I need for my score. It compiles ok on Lilypond 2.18.2,
> but I am using 2.19.53 for my score and I am getting this warnings:
> Starting lilypond 2.19.53 [frameEngraver-boxes-and-repeats-example.ly]...
> Processing
> `/Users/jamescorrea/Downloads/frameEngraver-boxes-and-repeats-example.ly'
> Parsing...
> warning: type check for `FrameStub' failed; value `#' must
> be of type `list'
> warning: type check for `FrameBracket' failed; value `#'
> must be of type `list'
> warning: type check for `FrameExtender' failed; value `#'
> must be of type `list'
> warning: type check for `Frame' failed; value `#' must be
> of type `list'
> Interpreting music...
> Exited with exit status 1.
>
> My code skills aren't enough to fix it. Can someone help me?
> I am attaching the .ily file, I hope the author will be ok with.
> Thanks in advance!!!
>
>
> Hi James,
> Here’s a tidbit I filed away the last time frameEngraver was discussed:
> "
> ...should mention that this needs 2.18.x  There is a single change which you
> need for current development versions.  See the last line below:
>
> % ADD NEW GROB DEFINITIONS
> %
>
> #(define (add-grob-definition grob-name grob-entry)
>(let* ((meta-entry   (assoc-get 'meta grob-entry))
>   (class(assoc-get 'class meta-entry))
>   (ifaces-entry (assoc-get 'interfaces meta-entry)))
>  (set-object-property! grob-name 'translation-type? ly:grob-properties?)
> ;; NB!!
> “
>
> I think this was Nalesnik speaking. I don’t know enough to say that this
> will fix the problem, but I hope it helps. I've used frameEngraver
> extensively, so I want to see it continue to function!
> Best,
> Holland
>

Yes, me speaking :)  This should fix the problem.

David

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


Re: help with frameEngraver-bars-and-boxes function

2017-01-09 Thread holl...@hollandhopson.com

> On Jan 8, 2017, at 5:39 PM, James.Correa  wrote:
> 
> Hi,
> 
> This is my first time writing on the list. I have using lilypond for a few 
> months, and I find in the list archive a function written by David Nalesnik 
> that is exactly what I need for my score. It compiles ok on Lilypond 2.18.2, 
> but I am using 2.19.53 for my score and I am getting this warnings:
> Starting lilypond 2.19.53 [frameEngraver-boxes-and-repeats-example.ly]...
> Processing 
> `/Users/jamescorrea/Downloads/frameEngraver-boxes-and-repeats-example.ly'
> Parsing...
> warning: type check for `FrameStub' failed; value `#' must 
> be of type `list'
> warning: type check for `FrameBracket' failed; value `#' 
> must be of type `list'
> warning: type check for `FrameExtender' failed; value `#' 
> must be of type `list'
> warning: type check for `Frame' failed; value `#' must be of 
> type `list'
> Interpreting music...
> Exited with exit status 1.
> 
> My code skills aren't enough to fix it. Can someone help me?
> I am attaching the .ily file, I hope the author will be ok with.
> Thanks in advance!!!

Hi James,
Here’s a tidbit I filed away the last time frameEngraver was discussed:
"
...should mention that this needs 2.18.x  There is a single change which you 
need for current development versions.  See the last line below:

% ADD NEW GROB DEFINITIONS %

#(define (add-grob-definition grob-name grob-entry)
   (let* ((meta-entry   (assoc-get 'meta grob-entry))
  (class(assoc-get 'class meta-entry))
  (ifaces-entry (assoc-get 'interfaces meta-entry)))
 (set-object-property! grob-name 'translation-type? ly:grob-properties?) ;; 
NB!!
“

I think this was Nalesnik speaking. I don’t know enough to say that this will 
fix the problem, but I hope it helps. I've used frameEngraver extensively, so I 
want to see it continue to function!
Best,
Holland___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Extracting symbol location

2017-01-09 Thread Lukas Tuggener
Hi David

When I tried to use your very useful script on a fresh installation it
didnt work anymore. I suspect it is due to the change you already mentioned
in your first message:



*There's a patch being reviewed which replaces the 'id property
with'output-properties and this will need to be updated
accordingly(https://sourceforge.net/p/testlilyissues/issues/4974/
).*


I tried to uptdate the script, but didnt get it to work so far. I assume
the updated assignIDs function should look something like this:

assignIDs = #(let ((grob-names (map car all-grob-descriptions)))
   #{
 #@(map (lambda (x)#{ \override #(list 'Score x (assoc-get 'id
 output-attributes) = #get-unique-id #})
 grob-names)
   #})

For any hint where I went wrong i would be very grateful.

Regards
Lukas

David Nalesnik  schrieb am Di., 27. Sep. 2016 um
22:33 Uhr:

> Hi Urs,
>
> On Tue, Sep 27, 2016 at 3:58 AM, Urs Liska  wrote:
> >
> >
> > Am 26.09.2016 um 20:13 schrieb David Nalesnik:
> >> The link you cite mentions looking at SVG output, and I suppose that
> >> would be the best way.  I can't think of another method to get the
> >> actual print positions of objects.
> >>
> >
> > Hm, but at some point LilyPond *has* to know where objects are placed,
> > isn't it?
> > Isn't there anything like a parent hierarchy that could be walked up
> > like a breadcrumb navigation that eventually leads to coordinates
> > relative to a page corner?
>
> Don't know how helpful this is, but I see the command-line option
> -dbackend=scm which dumps the stencil output of a file as a Scheme
> expression.  It includes entries for "grob-cause".
>
> I've tried to create a function which takes a score argument and
> produces a corresponding stencil expression to work with, but I'm
> having no luck.
>
> It would be nice to do something like this:
>
>  \version "2.19.46"
>
> #(use-modules (scm page))
>
> #(define (of paper-book)
>(for-each
> (lambda (page)
>   (display (ly:stencil-expr page))
>   (newline))
> (map page-stencil (ly:paper-book-pages paper-book
>
> but I can't get the Paper_book object needed.
>
> ly:book-process does create a Paper_book, but it isn't returned...
>
> >
> > (Of course this is closely related to my question
> > http://lists.gnu.org/archive/html/lilypond-user/2016-09/msg00655.html)
> >
>
> Seems like a tall order, but who knows!
>
> David
>
> ___
> 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