On Sat, Sep 12, 2009 at 11:37:37AM +0200, Valentin Villenave wrote:
> On Sat, Sep 12, 2009 at 2:54 AM, Graham Percival
> wrote:
> > Those are extremely good points. In the interests of a full
> > discussion (on a separate mailist, to avoid cluttering -devel),
>
> May I suggest http://lists.lilyn
On Sat, Sep 12, 2009 at 2:54 AM, Graham Percival
wrote:
> Those are extremely good points. In the interests of a full
> discussion (on a separate mailist, to avoid cluttering -devel),
May I suggest http://lists.lilynet.net/proposals/ ?
Cheers,
Valentin
On Sun, Sep 06, 2009 at 10:08:02PM +0100, Neil Puttock wrote:
> 2009/9/4 Carl Sorensen :
>
> > setInstrumentName =
> > #(define-music-function (parser location instrument-name) (string?)
> > #{
> > \set Staff.instrumentName = $instrument-name
> > #})
>
> I'm not in favour of this type of sub
2009/9/4 Carl Sorensen :
> And perhaps we should avoid the \set Staff.instrumentName tweaks by defining
> a \setInstrumentName command
>
> setInstrumentName =
> #(define-music-function (parser location instrument-name) (string?)
> #{
> \set Staff.instrumentName = $instrument-name
> #})
>
> Th
On 9/4/09 10:37 AM, "Joseph Wakeling" wrote:
> Trevor Daniels wrote:
>>> In order to have a
>>> meaningful manual, this may require the addition of some new LilyPond
>>> commands, which is *not* a problem.
>>
>> And is to be recommended if it results in an
>> easier user interface.
>
> I do
Carl Sorensen wrote Friday, September 04, 2009 11:57 PM
On 9/4/09 10:27 AM, "Trevor Daniels"
wrote:
Carl Sorensen wrote" Friday, September 04,
2009
3:06 PM
Also, as you plan sections, remember that anything using \set or
\override
belongs in a snippet, not in the main text body.
This
Mark Polesky wrote Saturday, September 05, 2009 1:22 AM
my Windows hard drive
tragically fried last week, and I won't be able to do any
LilyPond work until next Wednesday at the earliest, and
that's when my work starts up again, so I may be delayed
quite a bit.
That's a bummer - I was wonder
Mark Polesky wrote:
> I've already done a ton of work on keyboard tone-clusters
> and percussion pictograms, but my Windows hard drive
> tragically fried last week, and I won't be able to do any
> LilyPond work until next Wednesday at the earliest, and
> that's when my work starts up again, so I ma
Joseph Wakeling wrote:
> (i) Would people be interested in having this in the docs?
>
> (ii) Any requests or suggestions for topics that should be covered?
>
>(iii) What are the restrictions on including examples from actual
> contemporary scores? I'm not thinking huge ext
On Fri, Sep 04, 2009 at 04:57:11PM -0600, Carl Sorensen wrote:
>
> On 9/4/09 10:27 AM, "Trevor Daniels" wrote:
> > Carl Sorensen wrote" Friday, September 04, 2009
> > 3:06 PM
> >> Also, as you plan sections, remember that anything using \set or
> >> \override
> >> belongs in a snippet, not in th
On 9/4/09 10:27 AM, "Trevor Daniels" wrote:
>
>
> Carl Sorensen wrote" Friday, September 04, 2009
> 3:06 PM
>>
>> Also, as you plan sections, remember that anything using \set or
>> \override
>> belongs in a snippet, not in the main text body.
>
> This certainly is a rule for NR 1, but is
Trevor Daniels wrote:
>> In order to have a
>> meaningful manual, this may require the addition of some new LilyPond
>> commands, which is *not* a problem.
>
> And is to be recommended if it results in an
> easier user interface.
I do have some concrete ideas here, which I'll lay out in an email
Carl Sorensen wrote" Friday, September 04, 2009
3:06 PM
Also, as you plan sections, remember that anything using \set or
\override
belongs in a snippet, not in the main text body.
This certainly is a rule for NR 1, but is not
absolutely essential for NR 2. But in general
you're right - s
On Fri, Sep 4, 2009 at 12:37 PM, Joseph
Wakeling wrote:
> On that note ... does the Pirate Party have any kind of official
> response to this article by Richard Stallman?
> http://www.gnu.org/philosophy/pirate-party.html
Yes we do (as a matter of fact I am the Pirate member he refers to in
the nex
Carl Sorensen wrote:
> Also, as you plan sections, remember that anything using \set or \override
> belongs in a snippet, not in the main text body. In order to have a
> meaningful manual, this may require the addition of some new LilyPond
> commands, which is *not* a problem.
Do you mean in the
On 9/4/09 3:36 AM, "Joseph Wakeling" wrote:
> Graham Percival wrote:
>> Those "actual contemporary scores" must be placed in the public
>> domain, licensed under Creative Commons, or licensed under the GNU
>> FDL. If you're thinking about an exerpt of Shostakovich or Glass,
>> then forget abo
Valentin Villenave wrote:
> [off-topic] btw: French Pirate Party's first election is in two weeks
> here, and since I'm the campaign manager that (partly) explains my
> lack of time to work on LilyPond ;-)
On that note ... does the Pirate Party have any kind of official
response to this article by
On Fri, Sep 4, 2009 at 5:57 AM, Graham Percival wrote:
> Oh, and make sure you vote for your country's Pirate Party.
> Branches started recently in the UK and Canada, so I've got my
> next elections' votes lined up. ;)
[off-topic] btw: French Pirate Party's first election is in two weeks
here, an
Graham Percival wrote:
> Those "actual contemporary scores" must be placed in the public
> domain, licensed under Creative Commons, or licensed under the GNU
> FDL. If you're thinking about an exerpt of Shostakovich or Glass,
> then forget about it. Blame copyright law[1], not me.
Actually I was
On Thu, Sep 03, 2009 at 02:15:50PM +0200, Joseph Wakeling wrote:
>(iii) What are the restrictions on including examples from actual
> contemporary scores? I'm not thinking huge extracts, but maybe
> a couple of bars from a known work just to illustrate how a
> partic
Trevor Daniels wrote:
> Stubs are fine, but make them visible rather than commented out,
> perhaps followed by "TBC" (to be completed). You could do this
> in the Turkish section too - I'm sure that's what Graham meant.
Sure. In that case I just removed stuff because I was fairly sure I
wasn't m
Joseph Wakeling wrote Thursday, September 03, 2009 7:13 PM
Trevor Daniels wrote:
BTW, slightly tangential, but have you seen section 4.5.5 on
Proportional
notation, written by Trevor Bača? There would be no need to
repeat this.
Sure -- I've even tried using that functionality in one or two
Trevor Daniels wrote:
> BTW, slightly tangential, but have you seen section 4.5.5 on Proportional
> notation, written by Trevor Bača? There would be no need to repeat this.
Sure -- I've even tried using that functionality in one or two pieces.
:-) Incidentally, what's described there is only a s
Joseph Wakeling wrote Thursday, September 03, 2009 1:15 PM
Following my fun experience writing some documentation for
makam.ly and Turkish classical music, I'm thinking of writing a
section on contemporary music for the Notation Reference. This
would join the existing sections of Chapter 2
Bryan Stanbridge wrote:
> One thing that's always been a pain to me are the "box" score notations
> where a small snippet of music is enclosed in a box, then a dark line
> with or without an arrow will run for the duration that the performer is
> to repeat the box. I've stayed away from typesetting
Hello all,
Following my fun experience writing some documentation for makam.ly and Turkish
classical music, I'm thinking of writing a section on contemporary music for
the Notation Reference. This would join the existing sections of Chapter 2 on
various other forms of specialist notation.
The
26 matches
Mail list logo
