On 11/02/2013 06:47 PM, sniv...@catesby.org wrote:
On 2013-11-02 13:24, David Nalesnik wrote:
This won't compile as
it's missing lots of backslashes and two comments have been broken
across lines.
--David
Oops. Here's tiny example again, this time
as an attachment.
Thanks for the c
On 2013-11-02 13:24, David Nalesnik wrote:
> This won't compile as
it's missing lots of backslashes and two comments have been broken
across lines.
>
> --David
Oops. Here's tiny example again, this time
as an attachment.
\version "2.16.0"
\score
{
\new PianoStaff
<<
\new Staff =
Vik Reykja writes:
> On Sun, Sep 22, 2013 at 8:31 PM, David Kastrup wrote:
>
>> Vik Reykja writes:
>>
>> > On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup wrote:
>> >
>> >> David Kastrup writes:
>> >>
>> >> Thanks for the report.
>> >>
>> >
>> > And thank you for your quick response. This doe
On Sat, Nov 2, 2013 at 11:36 AM, wrote:
>
>
> % here is a case where autochange weirdly sends the top note to the
> bass clef, using lots of ledger lines
>
> version "2.16.0"
> score
> {
> new
> PianoStaff
> <<
> new Staff = "up" {
> <<
> new Voice {
> voiceOne
>
> autochange
> relative c'
% here is a case where autochange weirdly sends the top note to the
bass clef, using lots of ledger lines
version "2.16.0"
score
{
new
PianoStaff
<<
new Staff = "up" {
<<
new Voice {
voiceOne
autochange
relative c'' {
r2 r4 e4 % problem case: both voices go to
base clef
% r2. e4 % wo
David Bariod writes:
>> I'm not top posting
>
> Hello,
>
> I have a set of partitions which used to build in 2.14 release.
> Basically the table-of-contents does not seem to work at all
> in the 2.16 release.
>
> Here is a tiny sample which build in 2.14 but not in 2.16:
[...]
> \markuplines \t
> I'm not top posting
Hello,
I have a set of partitions which used to build in 2.14 release.
Basically the table-of-contents does not seem to work at all
in the 2.16 release.
Here is a tiny sample which build in 2.14 but not in 2.16:
\version "2.14"
\paper {
print-first-page-number = ##t
