Re: pageNumber

[bobr...@centrum.is]

Thanks Micheal!

The '\unless \on-first-page' was what I went with on the first try.  It was the 
magic sauce.

-David

- Original Message -
> From: "Michael Werner" 
> To: "bobroff" 
> Cc: "Lillypond Users Mailing List" 
> Sent: Sunday, November 12, 2023 1:09:05 PM
> Subject: Re: pageNumber

> Hi David,
> 
> On Sun, Nov 12, 2023 at 7:18 AM bobr...@centrum.is 
> wrote:
> 
>> I have the following in my \paper block.  I want to eliminate the page
>> number on page 1.  I have 'print-first-page-number = ##f' but the
>> oddHeaderMarkup is overriding it.  Is there a way around this? Some sort of
>> conditional?
>>
> 
> Turns out you just need to swap two lines. The \if conditional will apply
> to the next item ... and just the next item. It prints the next item if
> true, and leaves it blank if false. But the next item is the empty quotes,
> so something that's already empty. So just swap the \if conditional line
> down one to put it right before the page number line and all should be well.
> 
>  oddHeaderMarkup = \markup {
>\fill-line {
>  "" \larger\bold "SCORE"
>  \if \should-print-page-number
>  \fromproperty #'page:page-number-string
>}
>  }
> 
> There's also an alternative you can use, that kind of does this from the
> opposite viewpoint. This will print the page number unless it's the first
> page. Either should work, just going at things in two different ways. In
> some circumstances (special cases? tricky layouts?) one might be preferable
> over the other. But there are options to explore.
> 
>  oddHeaderMarkup = \markup {
>\fill-line {
>  "" \larger\bold "SCORE"
>  \unless \on-first-page
>  \fromproperty #'page:page-number-string
>}
>  }
> 
> For more details on these, have a look at:
> http://lilypond.org/doc/v2.25/Documentation/notation/custom-layout-for-headers-and-footers
> and
> http://lilypond.org/doc/v2.25/Documentation/notation/conditional-markup
> --
> Michael

Re: pageNumber

[Michael Werner]

Hi David,

On Sun, Nov 12, 2023 at 7:18 AM bobr...@centrum.is 
wrote:

> I have the following in my \paper block.  I want to eliminate the page
> number on page 1.  I have 'print-first-page-number = ##f' but the
> oddHeaderMarkup is overriding it.  Is there a way around this? Some sort of
> conditional?
>

Turns out you just need to swap two lines. The \if conditional will apply
to the next item ... and just the next item. It prints the next item if
true, and leaves it blank if false. But the next item is the empty quotes,
so something that's already empty. So just swap the \if conditional line
down one to put it right before the page number line and all should be well.

  oddHeaderMarkup = \markup {
\fill-line {
  "" \larger\bold "SCORE"
  \if \should-print-page-number
  \fromproperty #'page:page-number-string
}
  }

There's also an alternative you can use, that kind of does this from the
opposite viewpoint. This will print the page number unless it's the first
page. Either should work, just going at things in two different ways. In
some circumstances (special cases? tricky layouts?) one might be preferable
over the other. But there are options to explore.

  oddHeaderMarkup = \markup {
\fill-line {
  "" \larger\bold "SCORE"
  \unless \on-first-page
  \fromproperty #'page:page-number-string
}
  }

For more details on these, have a look at:
http://lilypond.org/doc/v2.25/Documentation/notation/custom-layout-for-headers-and-footers
and
http://lilypond.org/doc/v2.25/Documentation/notation/conditional-markup
-- 
Michael

pageNumber

[bobr...@centrum.is]

I have the following in my \paper block.  I want to eliminate the page number 
on page 1.  I have 'print-first-page-number = ##f' but the oddHeaderMarkup is 
overriding it.  Is there a way around this? Some sort of conditional?  

Thanks,

David


\paper {
  print-page-number = ##t
  first-page-number = 1
  print-first-page-number = ##f
  evenHeaderMarkup = \markup {
\fill-line {
  \if \should-print-page-number
  \fromproperty #'page:page-number-string
  \larger\bold "SCORE" ""
}
  }
  oddHeaderMarkup = \markup {
\fill-line {
  \if \should-print-page-number
  "" \larger\bold "SCORE" ""
  \fromproperty #'page:page-number-string
}
  }
}

Re: Use "#f" instead of "false" in manuals (was: OT: pagenumber)

[Palmer Ralph]

On Sat, Mar 5, 2016 at 4:11 AM, Urs Liska  wrote:

>
>
> Am 05.03.2016 um 09:51 schrieb Blöchl Bernhard:
> > I would recommend to add the options a user has to any item in the
> > chapter (maybe in other chapters as well)
> > 4.1.6 Other \paper variables
> > in the actual example that would mean
> >  print-page-number
> > default is ##true. If set to false (##f), page numbers are not
> > printed. Example of use:
> >  print-page-number = ##f
> >
> > Is there any adress to send this as a recommendation to the manual
> > editors? It is not a bug so I think the bug list is not the correct
> > address?
> >
>
> I agree that the use of the words "true" and "false" in that context is
> suboptimal and will confuse users who are still struggling with "false",
> "#f" and "##f".
> I'm not completely sure what the best resolution is.
>
> The bug-lilypond list is the right address for such issues, therefore I
> CC to that list with a modified subject.
>
> Urs
>

Thanks. This has been submitted as Issue #4792 :
https://sourceforge.net/p/testlilyissues/issues/4792/
Ralph
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OT: pagenumber

[David Kastrup]

Simon Albrecht  writes:

> On 04.03.2016 22:53, Blöchl Bernhard wrote:
>
>> A much better solution might be (just as a question/recommendation)
>> not to strain a simple minded user like me with such subtleties.
>
> This is not a ‘subtlety’ but a fundamental design principle; as a
> matter of fact, one cannot make thorough use of LilyPond without
> escaped Scheme expressions.  And IMO it’s better to give an honest and
> clear explanation here, to avoid later confusion.

If we can avoid the confusion by other means at reasonable cost
(explaining ##f every time it is used would not be reasonable), nothing
wrong with redundancy.

However, all suggestions take effort of various kinds to implement.  The
more work someone hoping to see a change invests into outlining this
change (with the optimum being a submitted patch), the better is
the probability that it will be picked up and implemented according to
his plan.

Finding all occurences and proposing exact text replacements would
already be a big help since that "only" requires use of editor and other
tools for a developer rather than his own creativity.

The more vague a proposal is, the less probable it is that someone will
actually act on it.  Of course, the more work one invests, the more
frustrating it might be when _still_ nobody acts on it.  While there are
no guarantees, I continue being impressed at the amount of developers
who actually do pick up documentation suggestions and create patches for
them.

-- 
David Kastrup

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

Re: OT: pagenumber

[Simon Albrecht]

On 04.03.2016 22:53, Blöchl Bernhard wrote:
But please do not forget that the manual is not addressed to 
programmers in first place but simple minded users like me. As a 
simple minded user I am only just interested how to get it work!


I don’t want LilyPond to be ‘esoteric’, but…

At least I would recommend to move that section above from "appendix" 
to "prefix". That would ease the use of the manual. By practical 
experience I know that no one really reads a manual (or even a section 
of a manual) from beginning to end.


We tell new users that it’s required to read the entire Learning Manual, 
and that’s a good thing, since it will much ease subsequent work with 
LilyPond.




A much better solution might be (just as a question/recommendation) 
not to strain a simple minded user like me

with such subtleties.


This is not a ‘subtlety’ but a fundamental design principle; as a matter 
of fact, one cannot make thorough use of LilyPond without escaped Scheme 
expressions.  And IMO it’s better to give an honest and clear 
explanation here, to avoid later confusion.


Best, Simon

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

Re: OT: pagenumber

[David Kastrup]

Thomas Morley  writes:

> 2016-03-05 9:55 GMT+01:00 David Kastrup :
>> Blöchl Bernhard  writes:
>>
>>> I would recommend to add the options a user has to any item in the
>>> chapter (maybe in other chapters as well)
>>> 4.1.6 Other \paper variables
>>> in the actual example that would mean
>>>  print-page-number
>>> default is ##true. If set to false (##f), page numbers are not
>>> printed. Example of use:
>>>  print-page-number = ##f
>>
>> ##true is not workable as long we are on Guile-1.8:

[...]

> And if I'm not mistaken that would mean the guilev2-expression #true
> would need to become ##true to be used in LilyPond-syntax.

Yes.

-- 
David Kastrup

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

Re: OT: pagenumber

[Thomas Morley]

2016-03-05 9:55 GMT+01:00 David Kastrup :
> Blöchl Bernhard  writes:
>
>> I would recommend to add the options a user has to any item in the
>> chapter (maybe in other chapters as well)
>> 4.1.6 Other \paper variables
>> in the actual example that would mean
>>  print-page-number
>> default is ##true. If set to false (##f), page numbers are not
>> printed. Example of use:
>>  print-page-number = ##f
>
> ##true is not workable as long we are on Guile-1.8:
>
> dak@lola:/usr/local/tmp/lilypond$ guile-1.8
> guile> #true
> #t
> ERROR: Unbound variable: rue
> ABORT: (unbound-variable)
> guile> #false
> #f
> ERROR: Unbound variable: alse
> ABORT: (unbound-variable)
> guile> dak@lola:/usr/local/tmp/lilypond$ guile-2.0
> GNU Guile 2.0.11
> Copyright (C) 1995-2014 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> #true
> $1 = #t
> scheme@(guile-user)> #false
> $2 = #f
> scheme@(guile-user)>
>
> --
> David Kastrup

And if I'm not mistaken that would mean the guilev2-expression #true
would need to become ##true to be used in LilyPond-syntax.

Aliasing true and #t in LilyPond is not a good idea either.
This was discussed already:
http://lilypond.1069038.n5.nabble.com/LilyPond-boolean-syntax-true-and-false-td185547.html#none

Example:

true = ##t
false = ##f

myListI = #'(false)
myListII = #(list false)

#(if (car myListI)
 (display "\n(car myListI) is #t")
 (display "\n(car myListI) is #f"))

#(if (car myListII)
 (display "\n(car myListI) is #t")
 (display "\n(car myListI) is #f"))


Otoh, it's always nice to improve the docs, but how to?
Any guile-expression used in LilyPond _needs_ to be prepended with a hash.

And there are more complex things than #t or #f:
#(#t #t #f) is a guile-vector, which would be used as ##(#t #t #f) for
break-visibility in LilyPond.
Well, we do some aliasing there, because it's very unlikely someone
uses 'end-of-line-invisible elsewhere.

Summarizing, I see no reasonable way to do the _coding_ different. The
_description_ in LM:
http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties
is pretty clear I'd say:
"
where a Boolean is either True (#t) or False (#f), an Integer is a
positive whole number, a Real is a positive or negative decimal
number, and text is enclosed in double apostrophes. Note the
occurrence of hash signs, (#), in two different places – as part of
the Boolean value before the t or f, and before value in the \set
statement. So when a Boolean is being entered you need to code two
hash signs, e.g., ##t.
"

Well, it's about context-properties, but the LM is recommended to be
read entirely (as opposed to the NR).

Is there really need to repeat it for
grob-properties
paper
layout
etc?


Cheers,
  Harm

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

Re: OT: pagenumber

[David Kastrup]

Blöchl Bernhard  writes:

> I would recommend to add the options a user has to any item in the
> chapter (maybe in other chapters as well)
> 4.1.6 Other \paper variables
> in the actual example that would mean
>  print-page-number
> default is ##true. If set to false (##f), page numbers are not
> printed. Example of use:
>  print-page-number = ##f

##true is not workable as long we are on Guile-1.8:

dak@lola:/usr/local/tmp/lilypond$ guile-1.8 
guile> #true
#t
ERROR: Unbound variable: rue
ABORT: (unbound-variable)
guile> #false
#f
ERROR: Unbound variable: alse
ABORT: (unbound-variable)
guile> dak@lola:/usr/local/tmp/lilypond$ guile-2.0 
GNU Guile 2.0.11
Copyright (C) 1995-2014 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)> #true
$1 = #t
scheme@(guile-user)> #false
$2 = #f
scheme@(guile-user)> 

-- 
David Kastrup

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

Use "#f" instead of "false" in manuals (was: OT: pagenumber)

[Urs Liska]

Am 05.03.2016 um 09:51 schrieb Blöchl Bernhard:
> Setting myself into the situation of a maybe user wanting to switch
> off the pagenumber I would google "lilypond pagenumber". Google is
> correcting me to page number (in correct English written separately).
>
> The first hit is
> LilyPond Notation Reference: 4.1.6 Other \paper variables
> http://lilypond.org/doc/v2.18/Documentation/notation/other-paper-variables
>
> and there I can find
> \paper variables for page numbering
> and eventually land at
>
>  print-page-number
> If set to false, page numbers are not printed.
>
> What to do now as a simple minded user?
>  print-page-number = false
>  print-page-number = "false"
> etc. .
>
> The second google hit is
> 3.2.4 Reference to page numbers
> http://lilypond.org/doc/v2.18/Documentation/notation/reference-to-page-numbers
>
> Being familiar with lilypond ##f might find my attention - or not. But
> that link is not really helpful. To get the syntax I would have to
> google again 
>
> I would recommend to add the options a user has to any item in the
> chapter (maybe in other chapters as well)
> 4.1.6 Other \paper variables
> in the actual example that would mean
>  print-page-number
> default is ##true. If set to false (##f), page numbers are not
> printed. Example of use:
>  print-page-number = ##f
>
> Is there any adress to send this as a recommendation to the manual
> editors? It is not a bug so I think the bug list is not the correct
> address?
>

I agree that the use of the words "true" and "false" in that context is
suboptimal and will confuse users who are still struggling with "false",
"#f" and "##f".
I'm not completely sure what the best resolution is.

The bug-lilypond list is the right address for such issues, therefore I
CC to that list with a modified subject.

Urs

>
> Am 04.03.2016 22:53, schrieb Blöchl Bernhard:
>> I know that thing with "read carefully" and RTFM very well and read a
>> lot of programming manuals as I was active working in that field - as
>> I was active ...
>>
>> You refer to the section
>> " ...
>> Note the occurrence of hash signs, (#), in two different places – as
>> part of the Boolean value before the t or f, and before value in the
>> \set statement. So when a Boolean is being entered you need to code
>> two hash signs, e.g., ##t.
>> .."
>>
>> But please do not forget that the manual is not addressed to
>> programmers in first place but simple minded users like me. As a
>> simple minded user I am only just interested how to get it work! At
>> least I would recommend to move that section above from "appendix" to
>> "prefix". That would ease the use of the manual. By practical
>> experience I know that no one really reads a manual (or even a section
>> of a manual) from beginning to end.
>>
>> A much better solution might be (just as a question/recommendation)
>> not to strain a simple minded user like me
>> with such subtleties. KISS: there must be set two hash signs.
>>
>>
>> Am 04.03.2016 22:31, schrieb Trevor Daniels:
>>> Blöchl Bernhard wrote Friday, March 04, 2016 9:11 PM
>>>
>>>
>>>> "false is ##f " really always?
>>>>
>>>> Please check
>>>> http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties
>>>>
>>>>
>>>> Seriously, is this an exception? Should one throw a bug report or
>>>> may be
>>>> a suggestion for harmonization? That would ease the use of lilypond
>>>> for
>>>> simple minded user like me. So a simple minded user is no longer
>>>> dependent on guesses.
>>>
>>> Please read the section you quote more carefully.  In particular the
>>> bit that
>>> says:
>>>
>>> "Note the occurrence of hash signs, (#), in two different places – as
>>> part of the
>>> Boolean value before the t or f, and before value in the \set
>>> statement. So when
>>> a Boolean is being entered you need to code two hash signs, e.g., ##t."
>>>
>>> Trevor
>>
>> ___
>> 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


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

Re: OT: pagenumber

[Noeck]

Hi Andrew,

Am 05.03.2016 um 01:11 schrieb Andrew Bernard:
> Hello Joram,
> 
> Just for the record, I was not proposing this as your reply indicates. 

I know. I was quoting from the wrong mail, sorry.

Joram

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

Re: OT: pagenumber

[Andrew Bernard]

Hi Blöchl,

Although I am a programmer, I found the initial learning to have to use ##f and 
##t for booleans, as a user wanting to get on and engrave music, obscure, 
difficult to remember, and easy to get wrong, what with the has escaped hash, 
even if you do read the manual carefully. Using booleans false and true is very 
much a programmers view of the world, but ‘civilians' generally don’t think in 
terms of boolean values to turn things on or off. [Set toaster operation mode 
to ##t.] I have been reflecting on this a little lately and it seems to me that 
in many cases where we are forced to specify a boolean the choice is between 
having something ‘on’ and having it ‘off’ - not having it. I am led to 
speculate if the possibility of providing off and on values would make it more 
intuitive for users not inclined to a programming mindset as much as Scheme and 
LISP pro’s.

Perhaps we could keep ##f and ##t for things like page numbering, but be 
generous minded and offer users some alternate ways of saying that as well. Yes 
I can see the arguments against this in the lilypond context, but is is a topic 
of some worth.

Andrew


On 5/03/2016, 19:51, "Blöchl Bernhard" 
<lilypond-user-bounces+andrew.bernard=gmail@gnu.org on behalf of 
b_120902342...@telecolumbus.net> wrote:

Setting myself into the situation of a maybe user wanting to switch off the 
pagenumber…

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

Re: OT: pagenumber

[Blöchl Bernhard]

Setting myself into the situation of a maybe user wanting to switch off 
the pagenumber I would google "lilypond pagenumber". Google is 
correcting me to page number (in correct English written separately).


The first hit is
LilyPond Notation Reference: 4.1.6 Other \paper variables
http://lilypond.org/doc/v2.18/Documentation/notation/other-paper-variables
and there I can find
\paper variables for page numbering
and eventually land at

 print-page-number
If set to false, page numbers are not printed.

What to do now as a simple minded user?
 print-page-number = false
 print-page-number = "false"
etc. .

The second google hit is
3.2.4 Reference to page numbers
http://lilypond.org/doc/v2.18/Documentation/notation/reference-to-page-numbers
Being familiar with lilypond ##f might find my attention - or not. But 
that link is not really helpful. To get the syntax I would have to 
google again 


I would recommend to add the options a user has to any item in the 
chapter (maybe in other chapters as well)

4.1.6 Other \paper variables
in the actual example that would mean
 print-page-number
default is ##true. If set to false (##f), page numbers are not 
printed. Example of use:

 print-page-number = ##f

Is there any adress to send this as a recommendation to the manual 
editors? It is not a bug so I think the bug list is not the correct 
address?



Am 04.03.2016 22:53, schrieb Blöchl Bernhard:

I know that thing with "read carefully" and RTFM very well and read a
lot of programming manuals as I was active working in that field - as
I was active ...

You refer to the section
" ...
Note the occurrence of hash signs, (#), in two different places – as
part of the Boolean value before the t or f, and before value in the
\set statement. So when a Boolean is being entered you need to code
two hash signs, e.g., ##t.
.."

But please do not forget that the manual is not addressed to
programmers in first place but simple minded users like me. As a
simple minded user I am only just interested how to get it work! At
least I would recommend to move that section above from "appendix" to
"prefix". That would ease the use of the manual. By practical
experience I know that no one really reads a manual (or even a section
of a manual) from beginning to end.

A much better solution might be (just as a question/recommendation)
not to strain a simple minded user like me
with such subtleties. KISS: there must be set two hash signs.


Am 04.03.2016 22:31, schrieb Trevor Daniels:

Blöchl Bernhard wrote Friday, March 04, 2016 9:11 PM



"false is ##f " really always?

Please check
http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties

Seriously, is this an exception? Should one throw a bug report or may 
be
a suggestion for harmonization? That would ease the use of lilypond 
for

simple minded user like me. So a simple minded user is no longer
dependent on guesses.


Please read the section you quote more carefully.  In particular the 
bit that

says:

"Note the occurrence of hash signs, (#), in two different places – as
part of the
Boolean value before the t or f, and before value in the \set
statement. So when
a Boolean is being entered you need to code two hash signs, e.g., 
##t."


Trevor


___
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: OT: pagenumber

[Andrew Bernard]

Hello Joram,

Just for the record, I was not proposing this as your reply indicates. I was 
merely sending back code to Xavier with a suggestion on a different matter. 
Once can’t correct everything!

Andrew


On 5/03/2016, 07:11, "Noeck" 
<lilypond-user-bounces+andrew.bernard=gmail@gnu.org on behalf of 
noeck.marb...@gmx.de> wrote:

Hi,

Am 04.03.2016 um 13:57 schrieb Andrew Bernard:
 \layout {
   pagenumber = no
   ...
 }

Sorry for diverging from the original topic, but what is pagenumber =
no? I couldn't find it in the documentation and I doubt that no is a
valid value. I see no effect of this statement. On the other hand,
lilypond is not printing any warning.

Cheers,
Joram

___
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: OT: pagenumber

[Blöchl Bernhard]

I know that thing with "read carefully" and RTFM very well and read a 
lot of programming manuals as I was active working in that field - as I 
was active ...


You refer to the section
" ...
Note the occurrence of hash signs, (#), in two different places – as 
part of the Boolean value before the t or f, and before value in the 
\set statement. So when a Boolean is being entered you need to code two 
hash signs, e.g., ##t.

.."

But please do not forget that the manual is not addressed to programmers 
in first place but simple minded users like me. As a simple minded user 
I am only just interested how to get it work! At least I would recommend 
to move that section above from "appendix" to "prefix". That would ease 
the use of the manual. By practical experience I know that no one really 
reads a manual (or even a section of a manual) from beginning to end.


A much better solution might be (just as a question/recommendation) not 
to strain a simple minded user like me

with such subtleties. KISS: there must be set two hash signs.


Am 04.03.2016 22:31, schrieb Trevor Daniels:

Blöchl Bernhard wrote Friday, March 04, 2016 9:11 PM



"false is ##f " really always?

Please check
http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties

Seriously, is this an exception? Should one throw a bug report or may 
be
a suggestion for harmonization? That would ease the use of lilypond 
for

simple minded user like me. So a simple minded user is no longer
dependent on guesses.


Please read the section you quote more carefully.  In particular the 
bit that

says:

"Note the occurrence of hash signs, (#), in two different places – as
part of the
Boolean value before the t or f, and before value in the \set
statement. So when
a Boolean is being entered you need to code two hash signs, e.g., ##t."

Trevor


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

Re: OT: pagenumber

[Trevor Daniels]

Blöchl Bernhard wrote Friday, March 04, 2016 9:11 PM


> "false is ##f " really always?
> 
> Please check
> http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties
> 
> Seriously, is this an exception? Should one throw a bug report or may be 
> a suggestion for harmonization? That would ease the use of lilypond for 
> simple minded user like me. So a simple minded user is no longer 
> dependent on guesses.

Please read the section you quote more carefully.  In particular the bit that
says:

"Note the occurrence of hash signs, (#), in two different places – as part of 
the 
Boolean value before the t or f, and before value in the \set statement. So 
when 
a Boolean is being entered you need to code two hash signs, e.g., ##t."

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

Re: OT: pagenumber

[Noeck]

We are talking about a ly-syntax environment here and Malte is right
that ##f is false there. The first # is switching to scheme and the #f
is false in scheme. This is directly (and better) explained in the link
you sent.

Cheers,
Joram

Am 04.03.2016 um 22:11 schrieb Blöchl Bernhard:
> "false is ##f " really always?
> 
> Please check
> http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties

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

Re: OT: pagenumber

[Blöchl Bernhard]

"false is ##f " really always?

Please check
http://www.lilypond.org/doc/v2.19/Documentation/learning/modifying-context-properties

Seriously, is this an exception? Should one throw a bug report or may be 
a suggestion for harmonization? That would ease the use of lilypond for 
simple minded user like me. So a simple minded user is no longer 
dependent on guesses.


Am 04.03.2016 21:47, schrieb Malte Meyn:

...
That’s not ‘more correct’; false is ##f, not #f in LilyPond
...
So maybe try out before guessing ;)

___
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: OT: pagenumber

[Malte Meyn]

Am 04.03.2016 um 21:54 schrieb Noeck:

   myfoo = "ok" % but
   mybar = bliblablup % why is that allowed?


Because LilyPond allows strings without quotes as long as they contain 
only certain characters (alphabet and probably some others). Good for 
lyrics for example, but also when using \clef etc.


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

Re: OT: pagenumber

[Noeck]

Thanks Malte,

Am 04.03.2016 um 21:47 schrieb Malte Meyn:
>   print-page-number = ##f

Yes, so coming back to the original post of Xavier: You probably mean
print-page-number = ##f instead of pagenumber = no. It was not your
question but perhaps it helps nonetheless.

And concerning lilypond, would it be possible to raise an error on such
an assignment? I assume the left hand side can be freely chosen to
define new variables in the paper block but could the right hand side be
checked somehow? The following file compiles just fine:

\version "2.19.36"

\paper {
  myfoo = "ok" % but
  mybar = bliblablup % why is that allowed?
}

{ a1 }

Joram

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

Re: OT: pagenumber

[Malte Meyn]

Am 04.03.2016 um 21:42 schrieb Blöchl Bernhard:

Just a guess, try
pagenumber = #f


That’s not ‘more correct’; false is ##f, not #f in LilyPond … Besides of 
that, what you mean is


\paper {
  print-page-number = ##f
}

So maybe try out before guessing ;)

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

Re: OT: pagenumber

[Blöchl Bernhard]

Just a guess, try
pagenumber = #f

Am 04.03.2016 21:11, schrieb Noeck:

Hi,

Am 04.03.2016 um 13:57 schrieb Andrew Bernard:

\layout {
  pagenumber = no
  ...
}


Sorry for diverging from the original topic, but what is pagenumber =
no? I couldn't find it in the documentation and I doubt that no is a
valid value. I see no effect of this statement. On the other hand,
lilypond is not printing any warning.

Cheers,
Joram

___
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

OT: pagenumber

[Noeck]

Hi,

Am 04.03.2016 um 13:57 schrieb Andrew Bernard:
> \layout {
>   pagenumber = no
>   ...
> }

Sorry for diverging from the original topic, but what is pagenumber =
no? I couldn't find it in the documentation and I doubt that no is a
valid value. I see no effect of this statement. On the other hand,
lilypond is not printing any warning.

Cheers,
Joram

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

Re: Suggestion for spacing pagenumber and barnumber

[Andrew Bernard]

Hi All,

How do you get the extra spacing under the page number? This has been eluding 
me.

Andrew


On 25/11/2015, 02:27, "Urs Liska" 
 wrote:

 I think it looks much better now. Somehow imagination evaded me ...


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

Re: Suggestion for spacing pagenumber and barnumber

[Kieren MacMillan]

Hi Andrew,

> How do you get the extra spacing under the page number? This has been eluding 
> me.

top-system-spacing

Hope this helps!
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: Suggestion for spacing pagenumber and barnumber

[Kieren MacMillan]

Hi Urs,

> how would you suggest to handle this unpleasant situation
> between the barnumber and the pagenumber?

Bar number italic + page number bold + more spacing, e.g.,



That seems very clear to me (which is why I do it that way).

Hope this helps!
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

Suggestion for spacing pagenumber and barnumber

[Urs Liska]

Hi list,

how would you suggest to handle this unpleasant situation between the
barnumber and the pagenumber?

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

Re: Suggestion for spacing pagenumber and barnumber

[Urs Liska]

Thanks,

I think it looks much better now. Somehow imagination evaded me ...

Best
Urs

Am 24.11.2015 um 15:26 schrieb Kieren MacMillan:
> Hi Urs,
>
>> how would you suggest to handle this unpleasant situation
>> between the barnumber and the pagenumber?
>
> Bar number italic + page number bold + more spacing, e.g.,
>
> ...
>
> That seems very clear to me (which is why I do it that way).
>
> Hope this helps!
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info <http://www.kierenmacmillan.info>
> ‣ email: i...@kierenmacmillan.info <mailto:i...@kierenmacmillan.info>
>

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

strange problem whith pagenumber

[Wolfgang Mechsner]

Hi,

the setting of pagenumber = no has no effects. In the contrary: I get
two numbers in top and the bottom of the site. Any ideas?

[lilypond 2.3.3. / Linux]
Wolfgang


Wolfgang Mechsner
Email [EMAIL PROTECTED]
URL www.wolfgang-mechsner.de
-


___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: strange problem whith pagenumber

[Jim Sabatke]

I couldn't get pagenumber = no to work with 2.3 either.  I 
also had lots of layout problems.  I went back to 2.2.1 and 
everything worked.

Wolfgang Mechsner wrote:
Hi,
the setting of pagenumber = no has no effects. In the contrary: I get
two numbers in top and the bottom of the site. Any ideas?
[lilypond 2.3.3. / Linux]
Wolfgang

Wolfgang Mechsner
Email [EMAIL PROTECTED]
URL www.wolfgang-mechsner.de
-
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user


--
Jim Sabatke
Hire Me!! - See my resume at http://my.execpc.com/~jsabatke
Do not meddle in the affairs of Dragons, for you are crunchy 
and good with ketchup.

___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user

pagenumber = no

[Peter Lutek]

greetings!

this was asked back in sept 2002 and was never answered the issue
still exists:

pagenumber = no
also turns off the head field in \header

is this intentional?

more to the point, is there a way of turning of the page number on ONLY
the first page, WITHOUT losing any other headers? i would like to use
the head field for instrument names on parts, but don't want page one
numbered.

thanks!

-p



___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: pagenumber = no

[Graham Percival]

On Fri, 28 Nov 2003 16:42:15 -0500
Peter Lutek [EMAIL PROTECTED] wrote:
 more to the point, is there a way of turning of the page number on ONLY
 the first page, WITHOUT losing any other headers? i would like to use
 the head field for instrument names on parts, but don't want page one
 numbered.

I don't believe you can do that directly in LilyPond, but you can certainly
do it using lilypond-book and LaTeX.

Cheers,
- Graham


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user

pagenumber = no

[Simon Bailey]

hi all,


\score {
  \notes {a b c d}
  \header {
title = A piece by me
head = Flute in C
instrument = Flute in C
  }
  \paper {
pagenumber = no
  }
}


setting pagenumber = no will also turn off head = Flute in C using
1.6.3. is this intentional?

thanks,
simon.
-- 
Don't be irreplaceable, if you can't be replaced, you can't be promoted.


___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user