- Original Message -
From: "Kevin Tough"
To: "LilypondMailingListGenUser"
Sent: Sunday, January 25, 2015 7:51 AM
Subject: Learning Manual 2.18 2.41 Organizing pieces with variables
Hi Folks,
I'm trying to get up to speed with variables but I am missing
Hi Kevin,
see:
http://www.lilypond.org/doc/v2.18/Documentation/extending/lilypond-variables.html
Not enough time to go into details.
Cheers,
Pierre
2015-01-25 8:51 GMT+01:00 Kevin Tough :
> Hi Folks,
> I'm trying to get up to speed with variables but I am missing something
> obvious or the docu
Hi Folks,
I'm trying to get up to speed with variables but I am missing something
obvious or the documentation is not clear.
In the example the escaped \cm generates an escaped character not
recognized error message. If I stick it in a layout block it is
recognized. Then however the variable is no
nks!
> Mark
>
> On Sat, Aug 25, 2012 at 4:19 PM, james wrote:
>
>> Section 1.1.4 of the Learning Manual has version 2.14.2 instead of
>> 2.16.0. It's not a big problem, and it's probably not difficult to fix, but
>> it's there.
>>
james,
I've forwarded this to the Bug Squad (so they know) and will add it to the
Issues Tracker. Thanks!
Mark
On Sat, Aug 25, 2012 at 4:19 PM, james wrote:
> Section 1.1.4 of the Learning Manual has version 2.14.2 instead of 2.16.0.
> It's not a big problem, and it's prob
Section 1.1.4 of the Learning Manual has version 2.14.2 instead of 2.16.0. It's
not a big problem, and it's probably not difficult to fix, but it's there.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/m
Hello,
Commits fc1946c290e5f253769a306efff1b0224178aaa5 and
9e1b534c81e101c449acfa176f923be57cbcaea5 have added a patch in to the Learning
Manual.
The NR still needs to be done.
Tracker opened http://code.google.com/p/lilypond/issues/detail?id=1197 (thanks
Phil)
James
-Original
Submitted as http://code.google.com/p/lilypond/issues/detail?id=1197
--
Phil Holmes
- Original Message -
From: "James"
To: "Trevor Daniels"
Cc: "Lily-Devel List" ; ;
Sent: Friday, July 30, 2010 7:00 PM
Subject: Re: tempo commands not in learning m
Hello,
On 29/07/2010 23:31, Trevor Daniels wrote:
Dan Wilckens wrote Thursday, July 29, 2010 2:47 PM
My suggestion is to include the \tempo "Allegro" 4=160 type command in
the Rhythms section of the Learning Manual, since tempo is fundamental
to rhythm, and I didn't find it a
blems before with 2.12 doc's) and I
actually couldn't find the command at all in the learning manual
in a couple minutes of clicking around the section headings.
(Admittedly, in the index it is easy to find.)
My suggestion is to include the \tempo "Allegro" 4=160 type
comma
#x27;t find the command at all in the learning manual in a couple
minutes of clicking around the section headings. (Admittedly, in the
index it is easy to find.)
My suggestion is to include the \tempo "Allegro" 4=160 type command in
the Rhythms section of the Learning Manual, since
Dan,
On 25/07/2010 02:59, Dan Wilckens wrote:
> Something so fundamental as tempo should be clearly explained
somewhere easy to
> find in the documentation, and it seems to be difficult to find at
all in the
> learning manual (looking at 2.12 documentation and briefly at 2.13).
I
Something so fundamental as tempo should be clearly explained somewhere easy to
find in the documentation, and it seems to be difficult to find at all in the
learning manual (looking at 2.12 documentation and briefly at 2.13). In my view
this is something fundamental enough to be in most pieces
On Fri, Aug 21, 2009 at 01:57:29PM +0200, John Mandereau wrote:
> Le vendredi 21 août 2009 à 08:54 +0100, Graham Percival a écrit :
> > LM 5 is being moved into the AU,
>
> What's the rationale for this? I must have missed in some discussion on
> the lists, but I couldn't find it in Git commit me
Le vendredi 21 août 2009 à 08:54 +0100, Graham Percival a écrit :
> LM 5 is being moved into the AU,
What's the rationale for this? I must have missed in some discussion on
the lists, but I couldn't find it in Git commit message as I might have
expected.
Cheers,
John
signature.asc
Description
On Thu, Aug 20, 2009 at 11:43:24AM -0400, Ralph Palmer wrote:
> Is the GDP dead?
Yes, but there's always room for more doc work. Also, GDP2 might
start in a month or two.
> If not, is there anything ready for indexing? If not,
> should I start working on reviewing something? I would be willing t
Greetings -
Is the GDP dead? If not, is there anything ready for indexing? If not,
should I start working on reviewing something? I would be willing to make a
start on LM 5 Working, but I don't feel qualified to make substantive
changes. I can look for grammar and organization and make sure stuff
Robin Bannister wrote:
Robin Bannister wrote
A: 21 hits for "\context Staff"
B: 14 hits for "\context { \Staff"
I think I get it now. It must be that "\context" is overloaded, does
two quite different things. Upon meeting a "\context" you must
categorise it as A or B.
The uninitiated a
or more to the point, the Learning Manual was talking
about B.
Cheers,
Robin
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
xplain this that is on my TODO list.
For now, I'm just adding an extra paragraph or two to
the Learning Manual, but more will need to be done
later.
Cheers,
Robin
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Robin Bannister wrote
A: 21 hits for "\context Staff"
B: 14 hits for "\context { \Staff"
I think I get it now.
It must be that "\context" is overloaded,
does two quite different things.
Upon meeting a "\context" you must categorise it as A or B.
The uninitiated attach no particular sig
Trevor Daniels wrote
Thanks, Robin
Well, you're welcome. Glad to be of some use.
But also disappointed,
because I thought I had understood something (from reading the manual!),
and now it seems I hadn't.
Statistics for NR (pdf dated 2008-08-09, only slightly stale):
A: 21 hits for "\co
Mats Bengtsson wrote
Robin Bannister wrote:
Trevor Daniels wrote
I learned you can have digits in context names! --- as long as the
names are in quotation marks.
which I regard as slightly more confirmation of my fragile suspicion that
in (the current GDP) Learning Manual 3.1.1 - In
Robin Bannister wrote:
Trevor Daniels wrote
I learned you can have digits in context names! --- as long as the
names are in quotation marks.
which I regard as slightly more confirmation of my fragile suspicion that
in (the current GDP) Learning Manual 3.1.1 - In summary there
shouldn&#
Trevor Daniels wrote
I learned you can have digits in context names! --- as long as the
names are in quotation marks.
which I regard as slightly more confirmation of my fragile suspicion that
in (the current GDP) Learning Manual 3.1.1 - In summary
there shouldn't be a backslash in fro
John Mandereau wrote Tuesday, August 12, 2008 5:42 PM
2008/8/10 Trevor Daniels <[EMAIL PROTECTED]>:
Absolutely. When the LM was written the appropriate sections in the
NR did not exist, or at least the headings were expected to change.
Now the headings have stabilised (more or less) the refs c
2008/8/11 Graham Percival <[EMAIL PROTECTED]>:
> On Sat, 9 Aug 2008 23:54:44 +0200
> "Valentin Villenave" <[EMAIL PROTECTED]> wrote:
>> Actually, this is a Johnism (I don't know why he keeps asking us to
>> remove parentheses).
>
> Parentheses are discouraged in highly formal writing, but they add
2008/8/10 Trevor Daniels <[EMAIL PROTECTED]>:
> Absolutely. When the LM was written the appropriate sections in the
> NR did not exist, or at least the headings were expected to change.
> Now the headings have stabilised (more or less) the refs can be added.
>
> Could you please make a new patch,
On Sat, 9 Aug 2008 23:54:44 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/8/9 Graham Percival <[EMAIL PROTECTED]>:
>
> > This must be a Frenchism; I winced when I saw it in some of
> > Valentin's text.itely changes. Why on earth remove the
> > parentheses? They help clarify the s
John, you wrote Saturday, August 09, 2008 5:15 PM
I proofread chapter 3 of the Learning Manual up to 3.1.4 'Modifying
context properties'. This is globally great work, I wish I could read
such docs instead of spending hours in trial-and-error and reading
Mats' explanations o
On Sat, 09 Aug 2008 22:39:09 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote:
>
> >I disagree. Shoving \header outside of a \book or \score is a
> >shorthand, and I'd rather keep the "basic" example as basic as
> >(reasonably) possibly. Also, having a \header on its own
2008/8/9 Graham Percival <[EMAIL PROTECTED]>:
> This must be a Frenchism; I winced when I saw it in some of
> Valentin's text.itely changes. Why on earth remove the
> parentheses? They help clarify the structure of the sentence.
Actually, this is a Johnism (I don't know why he keeps asking us t
Graham Percival wrote:
On Sat, 9 Aug 2008 18:15:35 +0200
"John Mandereau" <[EMAIL PROTECTED]> wrote:
In 'Introduction to the LilyPond file structure':
by default, \header does not use the same fields depending on its
scope (\book or \score), so IMO it's better to show the more standard
file
On Sat, 9 Aug 2008 18:15:35 +0200
"John Mandereau" <[EMAIL PROTECTED]> wrote:
> In 'Introduction to the LilyPond file structure':
> by default, \header does not use the same fields depending on its
> scope (\book or \score), so IMO it's better to show the more standard
> file structure with a \hea
Hi Trevor,
I proofread chapter 3 of the Learning Manual up to 3.1.4 'Modifying
context properties'. This is globally great work, I wish I could read
such docs instead of spending hours in trial-and-error and reading
Mats' explanations on -user, when I started with LilyPond 4 ye
On Fri, 01 Feb 2008 17:07:24 +0100
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Trevor Daniels wrote:
> > Hmm. It seems like the first # is optional for
> > a text string, but not for other types, which explains
> > why the example worked. I'll add the # to the example
> > to avoid this confusio
Trevor Daniels wrote:
3.3.4 I was confused about the hash signs (#).
The statement about why
they are needed before all values in a \set
statement is very clear,
but then the subsequent example has
\set Staff.instrumentName = "Soprano"
without a hash sign. Is this because "Soprano" is
a
> > 4.5.2 Regarding moving beams, I have a
> > typographical question. I
> > understand that the end of a beam is normally
> > positioned such that its
> > top edge, centre, or bottom edge is aligned on a
> > staff line. When
> > manually setting the positions, what fractions of
> > a line space wo
Andrew Hawryluk wrote 27 January 2008 02:09
>
> I just finished reading the Learning Manual for
> the first time and I
> am really impressed. Nice work everyone! As a
> relatively new user,
> chapters 3 and 4 were excellent. I am starting to
> figure out why
> co
I just finished reading the Learning Manual for the first time and I
am really impressed. Nice work everyone! As a relatively new user,
chapters 3 and 4 were excellent. I am starting to figure out why
commands belong in various places, and I now see how simple some of
the tweaks are. Thanks
On Wed, 16 Jan 2008 12:55:02 -
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> It is available now in PDF format. Click on the Learning
> Manual (LM) link on the development documentation page and
> look at the top of the page which comes up. I don't know
>
Albert
It is available now in PDF format. Click on the Learning
Manual (LM) link on the development documentation page and
look at the top of the page which comes up. I don't know
why this is different for the LM. It would be good if
someone could change it...
Trevor
> -Original
Hello,
I assume this will be on its way soon, but in case it's not I'd like to request
the new Learning Manual in PDF format. Even having the development version
available for printing now would be helpful!
Many thanks,
Albert
___
lil
Another poorly-explained idea is the split between the Learning Manual
and the Notation Reference. I've expanded parts of the LM now, so it
should hopefully be a bit more clear. As always, the latest docs are there:
http://opihi.cs.uvic.ca/~gperciva/
Please note that I am not lookin
44 matches
Mail list logo
