On Tue, 20 Aug 2019 at 12:26, Aaron Hill wrote:
>
> On 2019-08-19 6:50 pm, Vaughan McAlley wrote:
> > Hi everyone,
> >
> > The manual says:
> >
> > “To set the staff size globally for all scores in a file (or in a \book
> > block, to be precise), use set-global-staff-size”
> >
> > What am I doing
On 2019-08-19 6:50 pm, Vaughan McAlley wrote:
Hi everyone,
The manual says:
“To set the staff size globally for all scores in a file (or in a \book
block, to be precise), use set-global-staff-size”
What am I doing wrong here? The size 8 one is large and the size 50 one
is
normal (20 probably
>>> On 27/01/2019 04:52, David F. wrote:
>>> I can specify the font for my score to use with #(define fonts … ), but
>>> calling #(set-global-staff-size) undoes the font definition.
I seem to recall that’s documented somewhere but I can’t find where.
>> Why do you insist on the order, anyway? I
On Jan 27, 2019, at 9:09 PM, Martin Neubauer wrote:
> On 27/01/2019 04:52, David F. wrote:
>> I can specify the font for my score to use with #(define fonts … ), but
>> calling #(set-global-staff-size) undoes the font definition.
>>
>> In the snippet below, Times New Roman will be used as the
On 27/01/2019 04:52, David F. wrote:
> I can specify the font for my score to use with #(define fonts … ), but
> calling #(set-global-staff-size) undoes the font definition.
>
> In the snippet below, Times New Roman will be used as the font for the whole
> document. But if line 6 is uncommented
On Jan 26, 2019, at 8:52 PM, David F. wrote:
> I can specify the font for my score to use with #(define fonts … ), but
> calling #(set-global-staff-size) undoes the font definition.
>
> In the snippet below, Times New Roman will be used as the font for the whole
> document. But if line 6 is
Il giorno gio 25 ott 2018 alle ore 20:18 Thomas Morley
ha scritto:
> Davide wrote me a similiar mail, asking whether it's a bug in the
> docs. cc-ing him
I'm sorry, I meant to send my message to the list with you in cc, but
I hit the wrong button...
> "To set the staff size globally for all scor
Am Do., 25. Okt. 2018 um 19:03 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi Thomas,
>
> > Yep, set-global-staff-size _must_ be set at top-level, outside of \book.
>
> That's good to know.
> The documentation got me going on using-it inside \book{}s.
> http://lilypond.org/doc/v2.19/Documentation/notatio
Hi Thomas,
> Yep, set-global-staff-size _must_ be set at top-level, outside of \book.
That's good to know.
The documentation got me going on using-it inside \book{}s.
http://lilypond.org/doc/v2.19/Documentation/notation/setting-the-staff-size
> #(set-global-staff-size x)
> \book {}
> #(set-globa
Hi Pierre-Luc,
Am Mi., 24. Okt. 2018 um 16:01 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Is this a bug?
>
> \version "2.21.0"
> %#(set-global-staff-size 4)
> \book {
> #(set-global-staff-size 4)
> \score {
> {\tempo 4=120 c4}
> \layout {}
> }
> }
>
> I'm trying to set the gl
Hello Simon,
Thanks!
JM
> Le 25 sept. 2016 à 18:52, Simon Albrecht a écrit :
>
> On 25.09.2016 18:38, Menu Jacques wrote:
>> Hello folks,
>>
>> The NR as of 2.19 is not restrictive regarding where a command such as:
>>
>> #(set-global-staff-size 26)
>>
>> can be placed, but I remember
On 25.09.2016 18:38, Menu Jacques wrote:
Hello folks,
The NR as of 2.19 is not restrictive regarding where a command such as:
#(set-global-staff-size 26)
can be placed, but I remember someone on this list saying that it should be
before the \paper block.
What is the exact recommendat
Try :
tagline = \markup\fontsize #-5 "My Tagline"
See also :
http://lilypond.org/doc/v2.18/Documentation/notation/setting-the-staff-size
\score{
…
\layout{
#(layout-set-staff-size 15)
}
}
and for v2.19 :
http://lilypond.org/doc/v2.19/Documentation/notation/setting-the-staff-size
If you do something like:
\header {
tagline = \markup { \fontsize #-2 YourTagLine }
}
...it should probably work.
-David
- Original Message -
From: "Stephen MacNeil"
To: lilypond-user@gnu.org
Sent: Saturday, January 31, 2015 5:22:19 PM
Subject: #(set-global-staff-size 40)
I would like
Hi Urs,
the last statement the include returns is not music:
#(ly:set-option 'preview #t)
so the parser complains.
Those warnings can be avoided with void-functions, which wrap the statement.
(A bit in a hurry, so no example for noew ;) )
Cheers, Jan-Peter
Am 16.05.2014 12:05, schrieb Urs Lisk
- Original Message -
From: "Urs Liska"
To: "lilypond-user"
Sent: Friday, May 16, 2014 9:42 AM
Subject: set-global-staff-size from inside Scheme function
Hi,
I have been there already, but I can't find the corresponding email, and
I don't recall if they actually contained a solution
Am 16.05.2014 10:54, schrieb Jan-Peter Voigt:
Hi Urs,
this constellation compiles, if you wrap the scheme-call to
set-global-staff-size into a void-function. But if it is called, when
the book is already opened, the staff-size is already initialized and
can't be changed (for this book).
It proba
Hi Urs,
this constellation compiles, if you wrap the scheme-call to
set-global-staff-size into a void-function. But if it is called, when
the book is already opened, the staff-size is already initialized and
can't be changed (for this book).
It probably works, if you place #(set-global-staff-size
In data lun 3 mar 2014 23:57:40, hai scritto:
If you use two \book {} contexts, each can contain its own
set-global-staff-size command.
*_\version "2.19.2"_*
*_\language "english"_*
*_\header {_*
*_ title = "Titolo"_*
*_}_*
*_\paper {_*
*_ #(set-paper-size "a4")_*
*_}_*
*_global = {_*
*_
-Eluze writes:
> Francisco Vila wrote:
>>
>> 2011/12/7 Xavier Scheuer :
>>
>> It is a way but the problem I find is that the file won't compile with
>> that commandline option.
>>
>> Say your file is
>>
>> % this is example.ly
>> #(use-modules (guile-user))
>> #(set-global-staff-size size)
>>
Francisco Vila wrote:
>
> 2011/12/7 Xavier Scheuer :
>
> It is a way but the problem I find is that the file won't compile with
> that commandline option.
>
> Say your file is
>
> % this is example.ly
> #(use-modules (guile-user))
> #(set-global-staff-size size)
> \repeat unfold 20 { c'1 }
>
2011/12/7 Francisco Vila :
> lilypond -e '(define-public size 40)' a.ly
And of course there were more typos. It is not a.ly but example.ly in
my example above.
Sorry!
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypo
2011/12/7 Francisco Vila :
> It is a way but the problem I find is that the file won't compile with
> that commandline option.
Oh sorry, I meant the file won't compile _without_ that commandline option.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
2011/12/7 Xavier Scheuer :
> Hi,
>
> Is it possible to set global staff size as command line option?
> Like it is possible to specify paper size with
>
> lilypond -dpaper-size=\"letter\" myfile.ly
>
> I'd like a similar command line option for #(set-global-staff-size 14) .
> Is there a way to ach
On Wed 06 Oct 2010, 17:29 Christopher Meredith wrote:
> I noticed that the values for set-global-staff-size are usually given
> in non-whole increments. If I were to use one in between these
> suggested increments, will it cause scaling irregularities? In other
> words, if 14.14 is too small and 15
On 8/20/08, Tom Cloyd <[EMAIL PROTECTED]> wrote:
> \paper {
> #(set-default-paper-size "letter" 'portrait)
> ragged-last-bottom = ##t % turns off vertical justify
> left-margin = 0.6\in
> line-width = 7\in % works better than specifying R-margin
> bottom-margin = .7\in
>
2008/8/20 Tom Cloyd <[EMAIL PROTECTED]>:
> As for the staff spacing problem - if someone can just give me a clue
> where to go in the documentation, that would likely suffice. Google's
> doing nothing for me, and cruising the 2.11 docs contents list didn't
> help either.
Usually I try adjust betwee
Hi.
> If I have
>
> "#(set-global-staff-size 20)"
>
> in my code, I get 6 staffs spread across 1.5 pages (#6 is all that's on
> page 2). If I set the size to 18, I get the crowded onto one page with
> 2" at the bottom.
>
> I cannot figure out what's happening, or how to get better control of
Please ignore the "top-margin" problem. I wasn't reading my own code
correctly. Problem solved.
As for the staff spacing problem - if someone can just give me a clue
where to go in the documentation, that would likely suffice. Google's
doing nothing for me, and cruising the 2.11 docs contents lis
It isn't simple.
Chapter 4, Spacing Issues is (for me) a difficult read, and somewhat
complex. Also, I read the email thread from a couple of months ago
about this every couple of weeks, I don't understand it all fully, but
I understand a little more each time I read it.
http://lists.gnu.or
Hi Valentin,
On 7/27/07, Valentin Villenave <[EMAIL PROTECTED]> wrote:
>
> 2007/7/27, Valentin Villenave <[EMAIL PROTECTED]>:
>
> > (maybe it was a .27 bug, or something in my previous installation was
> > corrupted...).
>
> It's definitely a .27 bug; I was able to reproduce it with another
> inst
2007/7/27, Valentin Villenave <[EMAIL PROTECTED]>:
> (maybe it was a .27 bug, or something in my previous installation was
> corrupted...).
It's definitely a .27 bug; I was able to reproduce it with another
installation of .27, on a different OS.
V.V.
__
2007/7/27, Ledocq-Boccart <[EMAIL PROTECTED]>:
> I have just done a "cut and try" test as I (i.e. newbie) cannot do
> otherwise as yet.
Thank you for testing. Everything works fine since I installed 2.11.28
(maybe it was a .27 bug, or something in my previous installation was
corrupted...).
Re
Hello Valentin,
Valentin Villenave a écrit :
...However, I've just discovered that when I specify a different
global-staff-size, the compilation goes fine, no error messages... but
the .pdf (as well as the .ps) output is just one empty page!
I have just done a "cut and try" test as I (i.e. n
2007/7/26, Dominic Neumann <[EMAIL PROTECTED]>:
strange ... on my 2.10.25 system i get output in both variants (13 or
14). there are some errors but this could also come from using a 2.10
version instead of 2.11.
OK, I made some tests
It works with 2.10.25
It works with 2.11.28
It *doesn't* wo
35 matches
Mail list logo
