We've started cleaning up input/test/ , and run into a problem: some
snippets are used in the manual. For example, input/test/bar-lines.ly
I don't see the point in maintaining these examples as separate files,
instead of sticking them directly into the .itely files, but I could be
missing som
> "Juergen" == Juergen Reuter <[EMAIL PROTECTED]> writes:
Juergen> I am not sure, if line breaks by default should be
Juergen> allowed only on true bar lines or also on pseudo bar
Juergen> lines.
In general, a repeat sign is one of the better places for a page
break.
--
Laura (m
Oh, true. Yes, I remember having seen these double bar-like lines in the
middle of a bar, now that you are mentioning it.
So, summarizing, we actually have two totally different types of "bar"
lines:
* Pseudo "bar" lines, which are actually sectioning marks ("||",
repeat signs). Virtual
On 7/10/06, Anthony Youngman <[EMAIL PROTECTED]> wrote:
Will \makebar handle
\makebar { d4 d \bar "||" d d }
which is a SINGLE bar?
Yes, barlines and measures are separate concepts in lily (Timing
contexts insert bar lines between measures).
Erik
___
Will \makebar handle
\makebar { d4 d \bar "||" d d }
which is a SINGLE bar?
Cheers,
Wol
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
u.org] On Behalf Of Erik Sandberg
Sent: 07 July 2006 16:49
To: lilypond-devel@gnu.org
Cc: Juergen Reuter
Subject: Re: Prob
The repeat sign probably should include a double bar line ...
In my type of music (concert, brass band) it is quite normal to put a
double bar line in the middle of a bar when there is a major section
change, eg at the Trio. I've never come across a repeat in the middle of
a bar, though...
Cheers
On 7/10/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Erik Sandberg schreef:
>> Use C++ names in C++, and scheme names in scheme, i.e.
>>
>>Foo_bar::bla_bla
>>
>> for handling a bla-bla-event.
>
> so do you also think that all stream-event classes should be named
> like 'arpeggio-event' ra
Erik Sandberg schreef:
Use C++ names in C++, and scheme names in scheme, i.e.
Foo_bar::bla_bla
for handling a bla-bla-event.
so do you also think that all stream-event classes should be named
like 'arpeggio-event' rather than 'ArpeggioEvent'?
Regarding bla_bla for classes, it makes me ne
On 7/10/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Erik Sandberg schreef:
> First, I would prefer to make the second parameter of
> IMPLEMENT_TRANSLATOR the exact method identifier; i.e., somethign
> like
> IMPLEMENT_TRANSLATOR_LISTENER (Arpeggio_engraver, arpeggio_event);
> void Arpeggio_e
On 7/9/06, Graham Percival <[EMAIL PROTECTED]> wrote:
Erik Sandberg wrote:
> On Friday 07 July 2006 16:34, Graham Percival wrote:
I'm convinced as far as proper notation goes. But I'd still like to
have a "add time" command to avoid some bugs. I agree that it's a bad
reason, but unless there's
10 matches
Mail list logo
