Carl D. Sorensen wrote:
On 11/20/08 2:24 PM, Martin Tarenskeen [EMAIL PROTECTED] wrote:
On Thu, Nov 20, 2008 at 08:14:01AM -0600, Jonathan Kulp wrote:
Templates make Lilypond life a lot easier. Is there a place where I can
find the templates from the manual as separate files ? Copying
Great work. However, I find there is only one thing wrong with it:
it's for vim. :-)
2008/11/21 Eyolf Østrem [EMAIL PROTECTED]:
The most useful and simple tool I've had the pleasure to work on lilypond
files with, is Nicolas Sceaux's lyqi mode (lilypond quick insert). There is
only one thing
Mats Bengtsson wrote Friday, November 21, 2008 8:15 AM
Carl D. Sorensen wrote:
On 11/20/08 2:24 PM, Martin Tarenskeen [EMAIL PROTECTED] wrote:
On Thu, Nov 20, 2008 at 08:14:01AM -0600, Jonathan Kulp wrote:
Templates make Lilypond life a lot easier. Is there a place where I can
find the
Martin Tarenskeen wrote Thursday, November 20, 2008 9:24 PM
On Thu, Nov 20, 2008 at 08:14:01AM -0600, Jonathan Kulp wrote:
Try the template called piano-centered-lyrics (A.2.3) in the Learning
Manual.
Thank you, just what I was looking for.
One thing I don't understand about this (and some
On Fri, Nov 21, 2008 at 09:31:40AM -, Trevor Daniels wrote:
Martin Tarenskeen wrote Thursday, November 20, 2008 9:24 PM
I want to learn and not only use the templates but also
understand what I'm doing. Maybe some %comment lines should be added to
the templates in the learning manual ?
Trevor Daniels [EMAIL PROTECTED] writes:
Martin Tarenskeen wrote Thursday, November 20, 2008 9:24 PM
Why \new Staff = upper {...} and \new Staff = lower {...} ? I
use just \new Staff {...} with the same results.
[...] You're quite right though, the names are quite
unnecessary.
By giving
Also there is a quick insert mode work in progress for jEdit /
LilyPondTool. However, I could not make enough progress yet, but the
foundations are there, so in the after-the-next release it will be
available.
However, my quick insert mode will be really a virtual piano made from the
keyboard. I
Johan Vromans [EMAIL PROTECTED] writes:
By giving the Staff a name you can refer to its context later.
See sect. 5.1.2.
Also, the Staff name will be the track name used in the MIDI file.
-- Johan
___
lilypond-user mailing list
I've solved the (quite stupid) problem. So:
\slurDashed d16*(* a*)* a d d*(* a*)* *\slurSolid* a d d a a d d a a d
2008/11/20 Graham Percival [EMAIL PROTECTED]
Use \slurSolid. As you can see from the 2.11 docs, this works.
Try to construct a minimal example of your problem; this will
On 21.11.2008 (14:34), Bertalan Fodor wrote:
Also there is a quick insert mode work in progress for jEdit /
LilyPondTool.
That's the second reason why I found out I had to make something myself
(third, actually: after my sound contempt for emacs, and the desire to do
some learning-by-doing): I
Le 21 nov. 08 à 14:34, Bertalan Fodor a écrit :
In LilyPondTool you'll be able to type:
c g c s x c (try it!)
Much more natural. However, it makes it complicated, because the
software
must know the key. So for example is c minor it will be rendered as
c es c bes, b c
but in h major, it
This is a confirmation of my email for the lilypond mailing list.
Thanks,
Paul Grepps
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Then for sure I will include your layout as an option.
Bert
Nicolas Sceaux írta:
Le 21 nov. 08 à 14:34, Bertalan Fodor a écrit :
In LilyPondTool you'll be able to type:
c g c s x c (try it!)
Much more natural. However, it makes it complicated, because the
software
must know the key. So
Dear list,
I have the following two files:
includeError.ly:
\version 2.11.63
#(define RH rightHandFinger)
and
includedError.ly:
y\version 2.11.63
\include includedError.ly
And if I compile the second file, the parser tells me that the first
file is missing an '='.
includedError.ly:2:0:
Dear Arjan,
Your file includedError starts with the declaration of a variable: y
Hereafter lilypond expects an =
For example: y = test
I think the y is a typo.
When you remove this letter, your problem should be solved.
Kind regards,
Jan van Dijk.
Op Friday 21 November 2008 22:39:16 schreef
From: Arjan Bos [EMAIL PROTECTED]
Date: 21 november 2008 23:03:02 GMT+01:00
To: Jan van Dijk [EMAIL PROTECTED]
Subject: Re: Parser error when including file
Yes you are right, and I perfectly understand the error.
However, the error is signalled in the other file! And sadly, this is
not
Hi everyone
It seems that if I create a new context based on the Voice context, it
won't play with \RemoveEmptyStaffContext at all. Try the snippet below
as is, and then uncomment the commented block. A warning is generated
and lyrics are no longer rendered. Any ideas on how to get this to
work?
Arjan Bos [EMAIL PROTECTED] writes:
However, the error is signalled in the other file!
Not really.
LP processes the includeError.ly. It sees 'y', and starts looking for
and '='. I assume it processes the \version internally, and then
starts including the includedError.ly. Again, it processes
I have no argument with what you say about the documentation compared
with many kinds of technical documentation, as long as you stick close
to home.
The Lilypond folks work hard and do a lot of nice stuff, including
documentation.
However, that doesn't change the facts of what I say.
The
On 21.11.2008 (18:50), Nicolas Sceaux wrote:
I'm using the keyboard mapping suggested by a user and described here:
http://nicolas.sceaux.free.fr/index.php/2006/07/01/8
That's very close to my layout. The arrangement of the pitch keys is a
little different, but the principle is the same.
On 21.11.2008 (21:00), Bertalan Fodor wrote:
Then for sure I will include your layout as an option.
... and an option to customize the layout, I assume?
e
--
At Microsoft, quality is job 1.1 - Use Linux!
___
lilypond-user mailing list
Hi Daniel,
2008/11/17 Daniel Hulme [EMAIL PROTECTED]:
I have just got back from a band rehearsal, and tonight for the first
time I could see what bothers me about Lilypond's percent glyph: the
dots are too far out. I think they should be horizontally closer to the
centre, so that the space
On 11/21/08 4:56 PM, John Sellers [EMAIL PROTECTED] wrote:
I have no argument with what you say about the documentation compared with
many kinds of technical documentation, as long as you stick close to home.
The Lilypond folks work hard and do a lot of nice stuff, including
On Fri, Nov 21, 2008 at 11:20:23PM -0700, Carl D. Sorensen wrote:
On 11/21/08 4:56 PM, John Sellers [EMAIL PROTECTED] wrote:
The origin of the problem is that developers don't have to walk the path of
the newbies from beginning to end and it is very difficult to provide a
whole
24 matches
Mail list logo
