On Thu, Apr 12, 2012 at 8:28 PM, David Kastrup wrote:
> Jonathan Wilkes writes:
>
>> Well it's definitely a pain. My favorites are booleans, which require
>> one hash to denote scheme code, and one hash for the boolean. (Why
>> not one more hash, for good measure?)
>
> The character "#" would b
Jonathan Wilkes writes:
> Well it's definitely a pain. My favorites are booleans, which require
> one hash to denote scheme code, and one hash for the boolean. (Why
> not one more hash, for good measure?)
The character "#" would be written as ##\# when accessed from LilyPond.
So what?
--
Dav
Trevor Daniels wrote Thursday, April 12, 2012 9:55 PM
James Harkins wrote Thursday, April 12, 2012 5:08 PM
Still, it might be helpful to link to this page from some other places,
say, "Tweaking methods."
For instance,
~~~
The general syntax of this command is:
\override Context.LayoutO
James Harkins wrote Thursday, April 12, 2012 5:08 PM
Still, it might be helpful to link to this page from some other places,
say, "Tweaking methods."
For instance,
~~~
The general syntax of this command is:
\override Context.LayoutObject #'layout-property =
#value
This will set the
> Message: 1
> Date: Thu, 12 Apr 2012 21:32:28 +0800
> From: James Harkins
> To: lily-users
> Subject: Suggestion for documentation: Easy path to datatype reference
> Message-ID: <87iph5ulcj.wl%jamshar...@dewdrop-world.net>
> Content-Type: text/plain; charset=UTF-8
&
At Thu, 12 Apr 2012 16:55:24 +0100,
Trevor Daniels wrote:
> > Along with the existing documentation about overrides and tweaks, it would
> > be helpful to have a page -- which is easy to find -- listing all the data
> > types and the syntax to write them.
>
> This existing page seems to be what
James Harkins wrote Thursday, April 12, 2012 2:32 PM
Along with the existing documentation about overrides and tweaks, it would
be helpful to have a page -- which is easy to find -- listing all the data
types and the syntax to write them.
This existing page seems to be what you are requesti
Along with the existing documentation about overrides and tweaks, it would be
helpful to have a page -- which is easy to find -- listing all the data types
and the syntax to write them.
Example: Today, I was trying to write my own \override for the first time. To
make matters more challenging,
