Kieren MacMillan wrote:
So, where am I needed? I can start on some AllAbouts, or whatever. Just
say the word!
In a few days the technical backend should be ready, but start looking
at the "tricks and tips" examples. Some of them are broken, others may
have been made obsolete by recent featur
Hello, all!
I propose using the rendered "Examples" section of the documentation
(now empty) to post a series of AllAbouts, prepared by users,
each being an in-depth example of a narrow set of features [...]
Well, my "little project" is now finally over -- well, at least the
*premiere* is ov
Charles Cave wrote:
I think this is a FANTASTIC suggestion and I am willing to contribute
some examples.
Great! We're still working out some technical issues, but rest assured
that I'll let you know when it's ready.
I am really struggling to learn enough about Lilypond to create
a simple c
Why not look at all the full examples available at mutopia
(http://www.mutopiaproject.org/) ? The general principles
of setting up files for a score plus instrumental parts is described
in an example in the Tutorial.
/Mats
Charles Cave wrote:
Graham,
I think this is a FANTASTIC suggestion a
Graham,
I think this is a FANTASTIC suggestion and I am willing to contribute
some examples.
I am really struggling to learn enough about Lilypond to create
a simple cello + piano accompaniment score. The resulting output would
be the cello part, and the piano part.
The Lilypond has a lot of de
Sent: Monday, June 26, 2006 6:21 AM
To: Fairchild
Cc: 'Sebastiano Vigna'; 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples
See http://lists.gnu.org/archive/html/lilypond-user/2005-09/msg00373.html
and http://lists.gnu.org/archive/html/lilypond-user/2005-11/msg002
;'^\markup { "abc" \char #65 } }
>
>didn't.
>
>- Bruce
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf
>Of Fairchild
>Sent: Sunday, June 25, 2006 5:26 PM
>To: 'Sebastiano Vi
nal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fairchild
Sent: Sunday, June 25, 2006 5:26 PM
To: 'Sebastiano Vigna'
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples
I believe the "port" problem was caused by using \char
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fairchild
Sent: Sunday, June 25, 2006 5:26 PM
To: 'Sebastiano Vigna'
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples
I believe the "port" problem was caused by using \char in a \markup.
I believe the "port" problem was caused by using \char in a \markup.
- Bruce
-Original Message-
From: Sebastiano Vigna [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 25, 2006 5:21 PM
To: Fairchild
Cc: 'lilypond-user Mailinglist'
Subject: RE: Al
But see http://lilypond.org/doc/v2.8/Documentation/
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 25, 2006 4:06 PM
To: Graham Percival
Cc: Fairchild; 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples
Quoting Graham Perciv
On Sun, 2006-06-25 at 17:05 -0500, Fairchild wrote:
> Back to LSR posting.
>
> Since my AllAbout was not acceptable, tried a smaller thing thought to be
> version insensitive. LSR didn't like the \version "2.4.6" line, so deleted
The current version is 2.8.4, now it's also state in the "Contribu
Back to LSR posting.
Since my AllAbout was not acceptable, tried a smaller thing thought to be
version insensitive. LSR didn't like the \version "2.4.6" line, so deleted
it. LSR demanded \version "2.8.4" then complained cryptically about a port
problem. Submitted a trivial file; LSR flips out o
Quoting Graham Percival <[EMAIL PROTECTED]>:
On Sat, 24 Jun 2006 11:37:08 -0500
"Fairchild" <[EMAIL PROTECTED]> wrote:
...
that haven't made the cut for
Tips and Tricks or Regression Tests.
Actually, currently LSR is a mish-mash of lots of small things. I
think it includes some examples fro
mailto:[EMAIL PROTECTED]
Sent: Saturday, June 24, 2006 8:42 PM
To: Fairchild
Cc: 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples
On Sat, 24 Jun 2006 17:38:43 -0500
"Fairchild" <[EMAIL PROTECTED]> wrote:
> Seems that LSR won't accept 2.4.6.
I've made
> > What about `ly-convert'?
>
> If we're changing the name, what about "ly-update" ?
This is fine with me, as long as it starts with `ly-'.
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypo
On Sun, 25 Jun 2006 11:37:34 +0200 (CEST)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > If you haven't heard about convert-ly, look it up in the manual.
>
> BTW, I'm not happy about the name `convert-ly', for various reasons.
> What about `ly-convert'?
If we're changing the name, what about "ly-
> If you haven't heard about convert-ly, look it up in the manual.
BTW, I'm not happy about the name `convert-ly', for various reasons.
What about `ly-convert'?
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mai
Quoting Trevor Bača <[EMAIL PROTECTED]>:
...
error: Incorrect lilypond version: 2.4.6 (2.7.38, 2.9.9)
error: Consider updating the input with the convert-ly script
warning: deprecated function called: ly:set-point-and-click
ERROR: Unbound variable: def-music-function
... which must be because th
On Sat, 24 Jun 2006 11:37:08 -0500
"Fairchild" <[EMAIL PROTECTED]> wrote:
> The LSR entries seem to be short things
They're mostly short, but it can have long things as well.
> that haven't made the cut for
> Tips and Tricks or Regression Tests.
Actually, currently LSR is a mish-mash of lots of
On Sat, 24 Jun 2006 17:38:43 -0500
"Fairchild" <[EMAIL PROTECTED]> wrote:
> Seems that LSR won't accept 2.4.6.
I've made enquiries about LSR (I think it's still on 2.6), but we
cannot accept anything into the docs if it requires 2.4. I remember
that you had some problems with 2.6; do they still
ailinglist
Subject: Re: AllAbout Examples
On 6/24/06, Fairchild <[EMAIL PROTECTED]> wrote:
> Graham -
>
> AllAbout examples usually will be much larger than the LSR entries and
> too big for the manual. Think about an AllAbout that displays all
> font sets, one to demonstrat
On 6/24/06, Fairchild <[EMAIL PROTECTED]> wrote:
Graham -
AllAbout examples usually will be much larger than the LSR entries and too
big for the manual. Think about an AllAbout that displays all font sets,
one to demonstrate vertical layout options for a multipage score, one
showing lots of way
: Saturday, June 24, 2006 11:37 AM
To: 'Graham Percival'
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples
AllAboutAlternateScaling.ly is attached, a work in progress but maybe useful
enough to post as is. I'll try uploading to LSR.
_
7;ll try uploading to LSR.
- Bruce
-Original Message-
From: Graham Percival [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 24, 2006 12:48 AM
To: Fairchild
Cc: 'Kieren MacMillan'; 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples
On Thu, 22 Jun 2006
On Thu, 22 Jun 2006 13:34:43 -0500
"Fairchild" <[EMAIL PROTECTED]> wrote:
> However, based in my own experience and many postings on
> lilypond-user@gnu.org, I perceive a need for information that falls
> between content of tutorial and reference documentation -- more
> detailed than the tutorial
I've started writing something on noteheads. This seems to be where it
would fit in perfectly. (I probably ought to add stems and rests to it,
but that can wait :-)
I do feel something like this would be useful. As you say, we currently
have the User Manual (great for getting started) and the Prog
> However, based in my own experience and many postings on
> lilypond-user@gnu.org, I perceive a need for information that falls between
> content of tutorial and reference documentation -- more detailed than the
> tutorial material and less cryptic than the internals reference.
I completely agree
28 matches
Mail list logo
