On 8-Feb-06, at 8:05 PM, Carl D. Sorensen wrote:
Quoting Mats Bengtsson:
I think that it's fine to have { c } as an easy-to-use syntax.
However,
somewhere in the documentation it ought to mention what { c } will
expand to, when the defaults are put in.
That's what the new docs do. It's al
Quoting Mats Bengtsson:
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
>> We have lots of optional constructs in the syntax, { c } is actually
>> a short-cut for \book{\score{\new Staff{\new Voice{ c (maybe I
>> missed something).
> yes, you can add a \new Score inbetween also, and empty la
Quoting Graham Percival <[EMAIL PROTECTED]>:
On 4-Feb-06, at 1:59 AM, Mats Bengtsson wrote:
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
Then I'd propose this instead:
\new Lyrics { \lyricsto mytune { ... } }
because it feels relevant to me to consequently create contexts as
top-level
as pos
On Tuesday 07 February 2006 05.47, Graham Percival wrote:
> On 4-Feb-06, at 1:59 AM, Mats Bengtsson wrote:
> > Quoting Erik Sandberg <[EMAIL PROTECTED]>:
>
> I agree with Erik -- now the highest view of the music expression is
> {
>\new Staff { vocal }
>\new Lyrics \lyricsto vocalstaff { \l
On 4-Feb-06, at 1:59 AM, Mats Bengtsson wrote:
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
Then I'd propose this instead:
\new Lyrics { \lyricsto mytune { ... } }
because it feels relevant to me to consequently create contexts as
top-level
as possible. (hm.. the outer {} in my example are stil
On Friday 03 February 2006 21.12, Mats Bengtsson wrote:
> Quoting Erik Sandberg <[EMAIL PROTECTED]>:
> I would say the opposite, since in all other situations \new is used like
> \new Lyrics {...} or \new Lyrics \with {...} {...}. If you insert
> \lyricsto inbetween, people might get the the impres
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
On Friday 03 February 2006 21.12, Mats Bengtsson wrote:
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
I would say the opposite, since in all other situations \new is used like
\new Lyrics {...} or \new Lyrics \with {...} {...}. If you insert
\lyricsto inb
Quoting Erik Sandberg <[EMAIL PROTECTED]>:
> (I think there's a minor pedagogical point in saying \new Lyrics before
> \lyricsto, since the \new Lyrics really isn't a relevant argument of
> the
> music function, and because all other contexts start with context
> names)
I would say the opposite
On Wednesday 01 February 2006 21.13, Graham Percival wrote:
> On 31-Jan-06, at 12:55 AM, Erik Sandberg wrote:
> > - The following is a bit misleading:
> > \context Staff = singer <<
> > \context Voice = vocal { \melody }
> > \lyricsto vocal \new Lyrics { \text }
> >
> > The ly
Quoth Graham Percival:
> On 31-Jan-06, at 12:55 AM, Erik Sandberg wrote:
> > (I think there's a minor pedagogical point in saying \new Lyrics before
> > \lyricsto, since the \new Lyrics really isn't a relevant argument of
> > the music function, and because all other contexts start with
> > context
On 31-Jan-06, at 12:55 AM, Erik Sandberg wrote:
BTW, is the meaning of the word 'indent' well-known among
non-programmers? In
Excellent point! I think I'll reformat the whole chapter 4 with this
distinction (programmers vs. non-programmers) in mind.
- The outer braces should be << >> (usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Blaheta wrote:
> Quoth Graham Percival:
>
>>On 29-Jan-06, at 10:26 PM, Don Blaheta wrote:
>>
>>>In 4.4 and 4.5, would it be better to say "A \score must contain
>>>exactly one music expression (possibly complex)"? Saying it must
>>>"begin with"
Quoth Graham Percival:
> On 29-Jan-06, at 10:26 PM, Don Blaheta wrote:
> > In 4.4 and 4.5, would it be better to say "A \score must contain
> > exactly one music expression (possibly complex)"? Saying it must
> > "begin with" a music expression isn't saying quite enough.
>
> The \score must _beg
On Monday 30 January 2006 23.53, Graham Percival wrote:
> On 29-Jan-06, at 10:26 PM, Don Blaheta wrote:
> > Speaking of indents, you need to grep on "indent|ident"; you have a
> > tendency to confuse the two (I noticed an error one direction in 4.2
> > and
> > the other in 5.8).
>
> Thanks.
BTW, i
On 29-Jan-06, at 10:26 PM, Don Blaheta wrote:
In 4.4 and 4.5, would it be better to say "A \score must contain
exactly
one music expression (possibly complex)"? Saying it must "begin with"
a
music expression isn't saying quite enough.
The \score must _begin_ with the expression, and the wh
Quoth Graham Percival:
> I've written some more docs about file structure and writing lilypond
> files. I've glossed over some issues in the interest of simplicity.
> Before I advertise this on -user, could a few people take a look at the
> docs? As I said, I've glossed over some issues --
On 29-Jan-06, at 1:12 AM, Cameron Horsburgh wrote:
Overall it's a great addition to the manual.
Thanks! I've added your suggestions. I also added Han-Wen's
suggestions; I'll advertise it on -user when .30 comes out.
I'm a little put out
because I was starting to put together a few note
Cameron Horsburgh wrote:
> Graham Percival wrote:
>
>>>Hi guys,
>>>
>>>I've written some more docs about file structure and writing lilypond
>>>files. I've glossed over some issues in the interest of simplicity.
>>>Before I advertise this on -user, could a few people take a look at the
>>>doc
Graham Percival wrote:
Hi guys,
I've written some more docs about file structure and writing lilypond
files. I've glossed over some issues in the interest of simplicity.
Before I advertise this on -user, could a few people take a look at the
docs? As I said, I've glossed over some issue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Graham Percival wrote:
> Hi guys,
>
> I've written some more docs about file structure and writing lilypond
> files. I've glossed over some issues in the interest of simplicity.
> Before I advertise this on -user, could a few people take a look at
Hi guys,
I've written some more docs about file structure and writing lilypond
files. I've glossed over some issues in the interest of simplicity.
Before I advertise this on -user, could a few people take a look at the
docs? As I said, I've glossed over some issues -- did I omit anything
21 matches
Mail list logo
