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
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user