I am currently working on wikilily.org and realized that one thing
that could be very helpful when collaborating on Lilypond code, would
be a style guide. My question for all of you is: has any other project
drafted a style guide for Lilypond code?
The main things I imagine it wold cover would
1. LM 5 discusses general issues.
2. The doc policies on the GDP website discuss specific issues,
including indents and line breaks.
Cheers,
- Graham
On Tue, 5 Aug 2008 00:03:24 -0700
Jordan Eldredge [EMAIL PROTECTED] wrote:
I am currently working on wikilily.org and realized that one thing
I think an excellent place to look for inspiration would be LM 2.1.3
Am 05.08.2008 um 09:03 schrieb Jordan Eldredge:
I am currently working on wikilily.org and realized that one thing
that could be very helpful when collaborating on Lilypond code, would
be a style guide. My question for all of
Jordan Eldredge wrote:
I am currently working on wikilily.org and realized that one thing
that could be very helpful when collaborating on Lilypond code, would
be a style guide. My question for all of you is: has any other project
drafted a style guide for Lilypond code?
The main things I
On Tue, 2008-08-05 at 00:03 -0700, Jordan Eldredge wrote:
I am currently working on wikilily.org and realized that one thing
that could be very helpful when collaborating on Lilypond code, would
be a style guide. My question for all of you is: has any other project
drafted a style guide for
Mehmet Okonsar [EMAIL PROTECTED] writes:
To emacs users:
is there a way to stop emacs getting narrow which is somewhat annoying in
large scores...
Please explain what you mean. The term narrow means something
specific in Emacs terminology, but I suspect it's not what you are
talking about.
I see there's is some sort of tablature support in Mup, with bends and
slides...
http://www.arkkra.com/doc/uguide/tabstaff.html
Would be nice if we get it in Lilypond too.
Thanks in advance,
notesetter wrote:
I'd like to second rosea's sentiment about tablature. I'm just learning
I would perhaps not classify this as a pure bug, but definitely as a
limitation that deserves a feature request in the bug database.
As far as I can see, the same vertical position is used the for the left
end of the part of the glissando before the line break as for the part
after the line
James E. Bailey wrote:
Just out of curiousity, is there way to do either the clef or the time
signature for real?
Not that I know of!
/Mats
\version 2.11.52
{
\override Staff.Clef #'stencil = #ly:text-interface::print
\override Staff.Clef #'text = \markup {\musicglyph #clefs.G
Paul Scott wrote:
What are workable explicit names for either the lyrics or the voices to
connect the voices in the parallel part to some lyrics?
I'm surprised that nobody answered exactly this question. If you name
your main voice 1, then the upper voice of the {...} \\ {...}
construct
Karl Hammar wrote:
Ex1: { \A } \\ { \B }
creates TWO new voices, which get you into problems when doing \lyricsto,
where
Ex2: { \voiceOne \a } \new Voice { \voiceTwo \b } \oneVoice
only creates ONE new voice, \a belongs to the same voice as the surronding
music.
Ex1 is a dead end,
James E. Bailey wrote:
Am 17.07.2008 um 07:10 schrieb George_:
hi guys
I was wondering if there were a way to make articulation 'stick' to a
notehead, no matter where it is? I use 2.11.49 on XP, and I have a
two-part
melody, the lower voice is to be played staccato, like so:
On 5 Aug 2008, at 05:39, Jay Anderson wrote:
Kenny Stephens kfstephensii at yahoo.com writes:
Our church has a handbell group whose members are not all musically
literate. To
keep themselves from having to learn to read music, they mark their
notes using
differently colored highlighters.
Greetings -
I apologize for the trash, but I've stopped receiving the user list
mailings. I changed my subscription, and this is a test.
Ralph
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
I follow Joe Neeman's advice and it does the trick for me !
The manual for extra-spacing-width is here :
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Outside-staff-objects
I just added :
\layout {
\context {
\ChordNames
\override ChordName
Use the (cond) expression. Here's a simplified version of your
pitch-to-color function that colors all c's red and all f's blue:
#(define (pitch-to-color pitch)
(cond
((eqv? (ly:pitch-notename pitch) 0) (x11-color 'red))
((eqv? (ly:pitch-notename pitch) 3)
having trouble to do this
c4\sostenutoDown c4\sostenutoUp...
any tips?
thanks
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
ok ok...
it is on and off now... :)
josepadovani escreveu:
having trouble to do this
c4\sostenutoDown c4\sostenutoUp...
any tips?
thanks
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Read Piano pedals in section 2.2.2 of the Notation Reference.
Trevor
- Original Message -
From: josepadovani [EMAIL PROTECTED]
To: lilypond-user@gnu.org
Sent: Tuesday, August 05, 2008 9:36 PM
Subject: pedals on 2.11.53
having trouble to do this
c4\sostenutoDown c4\sostenutoUp...
thanks steven
cond - yes, i was trying to use case
kenny - can you figure it out from here?
if not i'll try tomorrow morning london time
d
On 5 Aug 2008, at 21:10, Steven Weber wrote:
Use the (cond) expression. Here's a simplified version of your
pitch-to-color function that colors all
I've received the test.
Cheers,
- Graham
On Tue, 5 Aug 2008 13:43:25 -0400
Palmer, Ralph [EMAIL PROTECTED] wrote:
Greetings -
I apologize for the trash, but I've stopped receiving the user list
mailings. I changed my subscription, and this is a test.
Ralph
rant
You have absolutely no idea how much chaos things like this cause for
people who are using Lilypond for major projects. You have absolutely
no idea how much of a problem this sort of thing is for archives like
Mutopia. You have no idea how the lack of input grammar stability
undermines
On Tue, Aug 5, 2008 at 3:33 PM, Steve Dunlop [EMAIL PROTECTED] wrote:
rant
You have absolutely no idea how much chaos things like this cause for
people who are using Lilypond for major projects. You have absolutely
no idea how much of a problem this sort of thing is for archives like
This has been discussed numerous times on the mailing list. Check the
archives.
Handling syntax changes such as \compressMusic -- \scaleDurations are
easily handled by convert-ly, since there is no change in structure of
the input file. Simply use the following command:
$ convert-ly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lasconic wrote:
| I follow Joe Neeman's advice and it does the trick for me !
| The manual for extra-spacing-width is here :
|
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Outside-staff-objects
|
| I just added :
| \layout {
|
2008/8/5 Mats Bengtsson [EMAIL PROTECTED]:
I'm surprised that nobody answered exactly this question. If you name your
main voice 1, then the upper voice of the {...} \\ {...} construct
will stay the same Voice context as the single voice.
That's true, it is explained in LM 3.2.1 I'm hearing
Wondering if anyone has experienced the following problem:
When creating new centered dynamics in a piano staff in ver. 2.11.55
(and several earlier versions) using \markup, three things happen:
1. the markup text created is significantly larger than the normal
dynamic size
2. the text
On Tue, Aug 5, 2008 at 4:05 PM, Steve Dunlop [EMAIL PROTECTED] wrote:
You don't get it. If you have an archive like Mutopia, where there are
thousands of files and dozens of contributors, and mixed dependencies on
versions, running conver-ly doesn't work.
It doesn't work because two people
Hi Folks,
I now have permission to release the articulation code
to improve MIDI output for lilypond. I've attached it as a
tar.bz2 file here. The code is copyright 2008 NICTA (my employer),
but released under GPL version 2.
The simple way to use it is to use
29 matches
Mail list logo
