Well, I gotta say. I feel the same as the writer. LP is powerful and extremely
accurate. But some things are hard to find in the documents and I think that
was the point of the writer.
Sent from my iPhone
> On 2 Dec 2018, at 17:34, Sandro Santilli wrote:
>
>> On Sun, Dec 02, 2018 at
Am So., 2. Dez. 2018 um 19:47 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 04:53:58PM +0100, Thomas Morley wrote:
> >
> > The proposed _ly-syntax_ is
> > \parenthesize
> > \parenthesize #'left
> > \parenthesize #'right
> > No parens.
>
> To be honest I still find that syntax hard
David Sumbler writes:
> -Original Message-
> From: msk...@ansuz.sooke.bc.ca
> To: David Sumbler
> CC: David Kastrup , lilypond-user
> Subject: Re: Not Nice Review of the LilyPond
> Date: Sun, 2 Dec 2018 14:17:11 -0500 (EST)
>
> On Sun, 2 Dec 2018, David Sumbler
-Original Message-
From: msk...@ansuz.sooke.bc.ca
To: David Sumbler
CC: David Kastrup , lilypond-user
Subject: Re: Not Nice Review of the LilyPond
Date: Sun, 2 Dec 2018 14:17:11 -0500 (EST)
On Sun, 2 Dec 2018, David Sumbler wrote:
> > But MusiXTeX can do "if" stat
Sandro Santilli writes:
> On Sun, Dec 02, 2018 at 04:53:58PM +0100, Thomas Morley wrote:
>>
>> The proposed _ly-syntax_ is
>> \parenthesize
>> \parenthesize #'left
>> \parenthesize #'right
>> No parens.
>
> To be honest I still find that syntax hard to understand.
> Replace the 3 with A B
On Sun, 2 Dec 2018, David Kastrup wrote:
> Have you looked at tags?
Please read my messages before responding to them.
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before tribes.
http://ansuz.sooke.bc.ca/
___
lilypond-user mailing
msk...@ansuz.sooke.bc.ca writes:
> On Sun, 2 Dec 2018, David Sumbler wrote:
>> > But MusiXTeX can do "if" statements.
>
>> I felt that an "if" would be useful, so I eventually came up with:
>
> That is useful for conditional includes, but it can't be embedded in the
> data structure that LilyPond
On Sun, 2 Dec 2018, David Sumbler wrote:
> > But MusiXTeX can do "if" statements.
> I felt that an "if" would be useful, so I eventually came up with:
That is useful for conditional includes, but it can't be embedded in the
data structure that LilyPond calls "music" and stores in variables. As
On Sun, Dec 02, 2018 at 04:53:58PM +0100, Thomas Morley wrote:
>
> The proposed _ly-syntax_ is
> \parenthesize
> \parenthesize #'left
> \parenthesize #'right
> No parens.
To be honest I still find that syntax hard to understand.
Replace the 3 with A B and C, how would the
above code render
-Original Message-
From: David Kastrup
To: msk...@ansuz.sooke.bc.ca
CC: lilypond-user
Subject: Re: Not Nice Review of the LilyPond
Date: Sun, 02 Dec 2018 17:00:33 +0100
msk...@ansuz.sooke.bc.ca writes:
> On Sun, 2 Dec 2018, David Kastrup wrote:
> > is hard. At least
msk...@ansuz.sooke.bc.ca writes:
> On Sun, 2 Dec 2018, David Kastrup wrote:
>> is hard. At least LilyPond is a better starting point than MusiXTeX.
>
> But MusiXTeX can do "if" statements.
I have a hard time imagining how this is going to hold in a more
convincing manner than you could do it
Sandro Santilli writes:
> On Sun, Dec 02, 2018 at 03:26:44PM +0100, Thomas Morley wrote:
>> Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
>> >
>> > Very obscure way to put chords
>> > in parenthesis (I asked yesterday).
>>
>> I beg to differ.
>
> Really ? And right after this
Am So., 2. Dez. 2018 um 16:34 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 03:26:44PM +0100, Thomas Morley wrote:
> > Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
> > >
> > > Very obscure way to put chords
> > > in parenthesis (I asked yesterday).
> >
> > I beg to
On Sun, 2 Dec 2018, David Kastrup wrote:
> is hard. At least LilyPond is a better starting point than MusiXTeX.
But MusiXTeX can do "if" statements.
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before tribes.
http://ansuz.sooke.bc.ca/
On Sun, Dec 02, 2018 at 03:26:44PM +0100, Thomas Morley wrote:
> Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
> >
> > Very obscure way to put chords
> > in parenthesis (I asked yesterday).
>
> I beg to differ.
Really ? And right after this statement you post a 36 lines
snippet of
Thomas Morley writes:
> Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
>>
>> On Sun, Dec 02, 2018 at 11:01:36AM +, J Martin Rushton wrote:
>>
>> > "LilyPond source files appear to be written in a custom programming
>> > language whose grammar is never discussed."
>> > - I'm
Am So., 2. Dez. 2018 um 14:01 Uhr schrieb Sandro Santilli :
>
> On Sun, Dec 02, 2018 at 11:01:36AM +, J Martin Rushton wrote:
>
> > "LilyPond source files appear to be written in a custom programming
> > language whose grammar is never discussed."
> > - I'm afraid this one is bang on target.
>
>http://www.alethis.net/reference/lily/lily.html
Not being a native speaker the finer bashing of LP may have escaped me.
The article obviously is old referring to 2.12 documentation and 2.10.something
in the version statement of some examples.
Not sure why I should be upset though.
Kind
On Sun, Dec 02, 2018 at 11:01:36AM +, J Martin Rushton wrote:
> "LilyPond source files appear to be written in a custom programming
> language whose grammar is never discussed."
> - I'm afraid this one is bang on target.
Hey, I have the exact same feeling. Very obscure way to put chords
in
J Martin Rushton writes:
> On 02/12/18 11:31, David Kastrup wrote:
>> J Martin Rushton writes:
>>
>>> I'm not sure the single critical paragraph is that unfair. I've turned
>>> the tables on the reviewer and added my own comments as an amateur who
>>> came to Lily only a few years ago.
>>
>>
On 02/12/18 11:31, David Kastrup wrote:
> J Martin Rushton writes:
>
>> I'm not sure the single critical paragraph is that unfair. I've turned
>> the tables on the reviewer and added my own comments as an amateur who
>> came to Lily only a few years ago.
>
> [...]
>
>> "LilyPond source files
J Martin Rushton writes:
> I'm not sure the single critical paragraph is that unfair. I've turned
> the tables on the reviewer and added my own comments as an amateur who
> came to Lily only a few years ago.
[...]
> "LilyPond source files appear to be written in a custom programming
>
I'm not sure the single critical paragraph is that unfair. I've turned
the tables on the reviewer and added my own comments as an amateur who
came to Lily only a few years ago.
I did try to send a copy of this email to the company as a courtesy, but
all company information on their website is
Reggie writes:
> Has anyone else seen this do you know who the author is? Some complaints
> about gibberish and documentation and God knows what else. Is this a joke
> one or seriously critical of the program? Or in cheek.
> http://www.alethis.net/reference/lily/lily.html
Seems to me like an
Hi Reggie,
It's not a review, it's a guide. There's one paragraph mentioning the
documentation is difficult and it's well known that like UNIX manuals the
NR is reference not tutorial. Besides he says this:
"In spite of these difficulties, LilyPond is astoundingly powerful, and
produces very
Has anyone else seen this do you know who the author is? Some complaints
about gibberish and documentation and God knows what else. Is this a joke
one or seriously critical of the program? Or in cheek.
http://www.alethis.net/reference/lily/lily.html
--
Sent from:
26 matches
Mail list logo
