Hi,
> The current examples present the minimum information necessary to demonstrate
> the feature.
> This follows lilypond's approach, which is to invent everything needed that
> you didn't specify, like books, scores, staves, time signatues, clefs,
> barlines, etc.
This *is* a potential frust
> From: Kieren MacMillan
> Subject: Re: Understanding Lilypond
>
> Hi Peter,
>
> > many of us have struggled for many months to get to grips with the
> structure and philosophy of Lilypond.
>
> 1. Regarding the structure, what are you struggling with exactly?
>
&g
Am 17.01.2015 um 17:22 schrieb Kieren MacMillan:
Hi Peter,
I'm not sure that my response is suitable for the list
It *definitely* is!
Please feel free to critisize scorn or otherwise flame.
I’m sorry your default expectation is to be critisized, scorned, or flamed —
that hasn’t been my p
m... It would be interesting and maybe helpful to develop such a typology
of common techniques. What have I left out above?
(Also, my sense is that LilyPond may or may not have the kind of systematic
consistency that some are looking for?)
Cheers,
-Paul
--
View this message in context:
http://lilyp
Hi Peter,
> I'm not sure that my response is suitable for the list
It *definitely* is!
> Please feel free to critisize scorn or otherwise flame.
I’m sorry your default expectation is to be critisized, scorned, or flamed —
that hasn’t been my primary experience on this list (as a newbie more th
Am Samstag, 17. Januar 2015 14:13 CET, Richard Shann
schrieb:
> actually, Scheme syntax is incredibly simple - Scheme expressions are
> lists (a b c) with the first element being the procedure and the
> subsequent ones the parameters. So if you come across (if a b) you look
> up the procedu
Am 17.01.2015 um 14:13 schrieb Richard Shann:
On Sat, 2015-01-17 at 13:37 +0100, Urs Liska wrote:
Concretely I see the problem in a sequence of related issues:
- Scheme itself *is* difficult to get into
actually, Scheme syntax is incredibly simple - Scheme expressions are
lists (a b c) with t
On Sat, 2015-01-17 at 13:37 +0100, Urs Liska wrote:
> Concretely I see the problem in a sequence of related issues:
>
> - Scheme itself *is* difficult to get into
actually, Scheme syntax is incredibly simple - Scheme expressions are
lists (a b c) with the first element being the procedure and the
way to interact with LilyPond through Scheme is quite obscure
(and that's where better documentation would be needed most IMO)
Urs
-Original Message-
From: Kieren MacMillan [mailto:kieren_macmil...@sympatico.ca]
Sent: Friday, January 16, 2015 9:40 PM
To: Peter Gentry
Cc: Lilypond-Us
sts to reduce the feeling of
being lost in a sea of hieroglyphs.
>-Original Message-
>From: Kieren MacMillan [mailto:kieren_macmil...@sympatico.ca]
>Sent: Friday, January 16, 2015 9:40 PM
>To: Peter Gentry
>Cc: Lilypond-User Mailing List
>Subject: Re: Understanding
Dear David,
as a small addition and a partly similar answer to Urs’, I think the point is:
LilyPond tries to suggest (or even enforce as a default) conventions of classic
music notation. This comprises for example that clefs are repeated for each line
but the time signature isn’t.
In your case, t
Hi Peter,
> many of us have struggled for many months to get to grips with the structure
> and philosophy of Lilypond.
1. Regarding the structure, what are you struggling with exactly?
2. Regarding the philosophy, what are you struggling with exactly?
Hope I can help!
Kieren.
>Just let me repeat something I wrote a number of times here.
>If you manage to understand something with the help of this
>list that you think could be a not-so-uncommon issue for many
>please consider sharing your experience with a (little or big)
>tutorial, for which we have always "free sp
"Re: Contents of lilypond-user digest..."
Today's Topics:
1. Understanding Lilypond (David Sumbler)
2. Re:Re:bottom of EPS output cut off (+ size of PDF files)
(Jayaratna)
3. Re:small caps (tisimst)
4. Re:Understanding Lilypond
email, send a message with subject or body 'help' to
> lilypond-user-requ...@gnu.org
>
>You can reach the person managing the list at
> lilypond-user-ow...@gnu.org
>
>When replying, please edit your Subject line so it is more
>specific than "Re: C
Am 16.01.2015 um 13:35 schrieb David Sumbler:
As I start to gain experience in setting music in Lilypond I am trying
to understand more about how it works internally. As well as personal
satisfaction, this obviously has a practical aim: it will make it easier
for me to modify or correct things
As I start to gain experience in setting music in Lilypond I am trying
to understand more about how it works internally. As well as personal
satisfaction, this obviously has a practical aim: it will make it easier
for me to modify or correct things without having to ask so many
questions on this f
now what I mean?
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Understanding-Lilypond-language-tp161270p161321.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hello David,
Many thanks for your reply. :-)
I was giving the variable example as a kind of difficulty I have. I
appreciate the "fish" you are giving to me but I want to learn "how to
fish" :-)
For example you say
"Because \layout { ... } is not a music expression but rather an output
definitio
Harald Christiansen writes:
> Hello,
>
> Is there a manual for the lilypond language itself ?
>
> I don't get it ... is it a programming language ... a macro expander ...
> all of the above ?
It is a dynamically typed language. Not much programming in the
language itself, but a Scheme layer cat
Hello,
Is there a manual for the lilypond language itself ?
I don't get it ... is it a programming language ... a macro expander ...
all of the above ?
I cannot build a mental model of how it works.
For example, let's take variables. I take the notation reference, I look
at the index and I see
21 matches
Mail list logo
