David Kastrup writes:
> David Kastrup writes:
>
>> "m...@apollinemike.com" writes:
>>
>>> Le Dec 10, 2011 à 9:18 PM, David Kastrup a écrit :
>>>
>
Why don't we have \footnote \default for autonumbering (just like with
\mark),
>>>
>>> We could...I don't understand how \defau
David Kastrup writes:
> "m...@apollinemike.com" writes:
>
>> Le Dec 10, 2011 à 9:18 PM, David Kastrup a écrit :
>>
>>>
>>> Why don't we have \footnote \default for autonumbering (just like with
>>> \mark),
>>
>> We could...I don't understand how \default works, so I'm not sure how
>> to m
"m...@apollinemike.com" writes:
> Le Dec 10, 2011 à 9:18 PM, David Kastrup a écrit :
>
>>>
>>
>> Why don't we have \footnote \default for autonumbering (just like with
>> \mark),
>
> We could...I don't understand how \default works, so I'm not sure how
> to make it work here, but a tutorial wou
Le Dec 10, 2011 à 9:18 PM, David Kastrup a écrit :
>>
>
> Why don't we have \footnote \default for autonumbering (just like with
> \mark),
We could...I don't understand how \default works, so I'm not sure how to make
it work here, but a tutorial would get me on my way!
> and why can't \footn
Hi David,
2011/12/9 David Nalesnik :
> Hi Harm,
>
> (...) looking
> with fresh eyes at the file I just attached, I really should have condensed
> that list of nearly identical offset calculations. (See attached for the
> way I came up with.)
thanks for doing this! I did the next step to simplify
Hi George,
On Sat, Dec 10, 2011 at 11:56 AM, George_ wrote:
Only...I can't figure out how to make it move up or down. If someone could
> help me with this I'd really appreciate it.
This adds another argument to the function which will move the markup up or
down:
\version "2.15.16"
dwn =
#(d
George_ writes:
> pkx166h-2 wrote:
>>
>> George,
>>
>> On 30 November 2011 22:16, George Xu wrote:
>>
>>> Oops, sorry. 2.14.2. I guess that explains why \auto-footnote doesn't
>>> work, but it doesn't help much...
>>>
>>>
>> In the latest 'development' version
>>
>> http://lilypond.org/doc/v
2011/12/9 Matthew Collett :
>
> On 9/12/2011, at 2:27 pm, David Kastrup wrote:
>
>>> On 8/12/2011, at 10:48 pm, David Kastrup wrote:
>>>
Please, *never*, *never*, *never* send a "courtesy copy" of a public
answer as a private mail when answering on a mailing list unless you
have been
The snippet that David linked to was too complicated for me to edit
effectively, so what I've done as a temporary solution is I've combined a
couple other snippets and used the mensural custos as a fill-in glyph:
http://lsr.dsi.unimi.it/LSR/Item?id=4
http://lsr.dsi.unimi.it/LSR/Item?id=378
to ma
pkx166h-2 wrote:
>
> George,
>
> On 30 November 2011 22:16, George Xu wrote:
>
>> Oops, sorry. 2.14.2. I guess that explains why \auto-footnote doesn't
>> work, but it doesn't help much...
>>
>>
> In the latest 'development' version
>
> http://lilypond.org/doc/v2.15/Documentation/notation/cr
Xavier Scheuer wrote:
>
> I think the \pageBreak at the end of the score *is* interfering (I did
> not check, maybe I would have if the code was self-compilable without
> I have to "imagine" a way to complete the missing variables).
>
> Why are you using \pageBreak at the end of the score and n
- Original Message -
From: "Kris Van Bruwaene"
To:
Sent: Saturday, December 10, 2011 12:00 PM
Subject: Re: Clashing note columns
Here is an example.
Kris
http://old.nabble.com/file/p32951130/lilytest.ly lilytest.ly
If you'd cut even more of the code out, you would have seen that
Kris Van Bruwaene writes:
>> David Kastrup wrote:
>>>
>>> Kris Van Bruwaene writes:
>>>
I am typesetting a choral piece wich has two voices coming in unisono on
a
single staff, one with a whole note (g1), the other with two half notes
(g2
g2). The whole note and the fi
Here is an example.
Kris
http://old.nabble.com/file/p32951130/lilytest.ly lilytest.ly
David Kastrup wrote:
>
> Kris Van Bruwaene writes:
>
>> I am typesetting a choral piece wich has two voices coming in unisono on
>> a
>> single staff, one with a whole note (g1), the other with two half not
George_ wrote:
>
> Oh, and I should also say that with the parts added in, there are no
> errors in the log. According to the program, everything is working as it
> should...except that it isn't.
>
> The reason I'm using both ragged-last and ragged-last-bottom is so that
> the lines on the last
George,
On 30 November 2011 22:16, George Xu wrote:
> Oops, sorry. 2.14.2. I guess that explains why \auto-footnote doesn't
> work, but it doesn't help much...
>
>
In the latest 'development' version
http://lilypond.org/doc/v2.15/Documentation/notation/creating-footnotes
This is explained in m
On 10 December 2011 00:45, Carl Sorensen wrote:
>
> I cannot display it, either.
>
> In scm/define-grobs.scm, the SpacingSpanner grob is set with a
> base-shortest-duration of 3/16, and shortest-duration-space is set to 2.0
IIUC common-shortest-duration is different from base-shortest-duration.
b
On 10 December 2011 03:54, George_ wrote:
>
> […]
>
> Every one of them is good *apart from* the ragged-last-bottom, i.e. setting
> it to true doesn't make it ragged at all. I've tried replacing it with
> ragged-bottom, which works fine.
>
> I've written in a \pageBreak at the end of the score, bu
2011/12/10 George_ :
> The thing is, that setting ragged-last-bottom = ##t doesn't do anything to
> the layout of the score, but setting ragged-bottom = ##t does.
ragged-last-bottom is #t by default % best for shorter scores
ragged-bottom is #f by default
--
Francisco Vila. Badajoz (Spain)
w
On 10/12/2011, at 3:54 pm, George_ wrote:
> \paper {
> ragged-last-bottom = ##t
> ragged-last = ##t
> left-margin = 10\mm
> right-margin = 7\mm
> top-margin = 5\mm
> bottom-margin = 5\mm
> }
> Every on
Oh, and I should also say that with the parts added in, there are no errors
in the log. According to the program, everything is working as it
should...except that it isn't.
George_ wrote:
>
> It shouldn't compile, I left the parts out to keep it reasonably short. As
> far as the \paper block is
It shouldn't compile, I left the parts out to keep it reasonably short. As
far as the \paper block is concerned, though, that is exactly what I am
using at the moment, and that is exactly what doesn't work.
The reason I'm using both ragged-last and ragged-last-bottom is so that the
lines on the l
George_ wrote:
>
> For a piece I'm writing out, this is what I have at the moment:
>
> Every one of them is good *apart from* the ragged-last-bottom, i.e.
> setting it to true doesn't make it ragged at all. I've tried replacing it
> with ragged-bottom, which works fine.
>
> I've written in a \
23 matches
Mail list logo
