Jesse Engle wrote:
4.) There is no way to create an entire page of exercises (a feature
that would be incredibly useful for music teachers such as myself)
like this:
http://jengle.waferbaby.com/tmp/lp/exercises.png
Actually, you could do this too within LilyPond, since you can use
\markup
>
> cygwin.html and macos.html have not been updated for a while; macos.html
> is clearly outdated, but cygwin.html is still valuable (Cygwin provides
> 2.10.7), so it should't be renamed to windows.html. You're right it
> should be clearly mentioned there are 2 LilyPond flavours on Windows
> (n
Graham Percival wrote:
> For the backporting of docs, I'd just start by copying everything and
> trying to build it with stable. The skyline spacing docs obviously
> won't work (so remove them from the backported docs), but AFAIK there
> aren't any other new features in 2.11 that affect the doc
Le jeudi 04 janvier 2007 à 21:10 +0200, Till Rettig a écrit :
> I just found out that the installation advices for windows are not
> anymore cygwin, but windows.
Where have you seen that???
> So I renamed the file and created a patch.
> Seems git works now for me (this time with the git format
Jesse Engle wrote:
1) There is no way that I have yet discovered to notate rhythms for all
four limbs,
Where did you look?
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Percussion-staves
2) LilyPond does not provide ratio-notation for odd groupings. For
instance, if I notate a gro
Michael Welsh Duggan <[EMAIL PROTECTED]> writes:
> It looks to me like drummode is undocumented. You can use the listed
> example and the contents of .../ly/drumpitch-init.ly in order to
> figure out what is happening. In particular, use the value of
> drumPitchNames in order to figure out the n
With this code,
\relative c' {
\repeat unfold 6 { c4 c c c }
c1\glissando
d'1
\repeat unfold 7 { d4 d d d }
}
the \glissando occurs at a page break. Is there any way to
(automatically) force linebreaks to avoid this?
I currently have \glissando \noBreak everywhere in my music; I'm try
Jesse Engle <[EMAIL PROTECTED]> writes:
> I am a drummer, and while I love that I can finally use free notation
> software instead of Finale for many melodic instruments, I've realized
> that the percussion features of LilyPond are lacking.
>
> 1) There is no way that I have yet discovered to nota
Hi, Jesse!
add the following features that I've listed.
No need -- everything can, I believe, already be done. Just read the
relevant parts of the wonderful documentation.
For example
2) LilyPond does not provide ratio-notation for odd groupings.
Just use
\override TupletNumber #'te
Hi everyone. While I am a decent programmer, I have never been part of
a large project such as this, so I would not know where to begin in
attempting to add the following features that I've listed.
I am a drummer, and while I love that I can finally use free notation
software instead of Finale
Erik Sandberg escreveu:
> They are there for completeness. I think the reason they are never called, is
> that score contexts aren't explicitly destroyed. I think this is because
> contexts below Score are destroyed during iteration, while scores themselves
> aren't (probably because they contai
Hi,
I just found out that the installation advices for windows are not
anymore cygwin, but windows. So I renamed the file and created a patch.
Seems git works now for me (this time with the git format-patch HEAD^ --
shouldn't we add this also to the README, or does it only confuse people?).
Hi:
There's a link at the very bottom of the index file in the spanish web
site, which is the equivalent of the About automatic language
selection.
It appears:
Acerca deselección automática de idioma.
It should appear as:
Acerca de selección automática de idioma.
It's an error in the es.po fi
On Thursday 04 January 2007 14:43, Han-Wen Nienhuys wrote:
> Hi Erik,
>
> browsing the coverage reports, I see
>
> **
> uncovered chunk in out-cov/score-performer.cc.gcov
>#: 77:Score_performer::disconnect_from_context ()
>-: 78:{
>#: 79: Dispatcher *d = cont
Wilbert Berendsen wrote:
I have added some examples. I think it would be a nice improvement. It also
solves the beam collision, although that should be checked with other
articulation signs as well.
I agree; added as
http://code.google.com/p/lilypond/issues/detail?id=218
Could you monitor tha
[EMAIL PROTECTED]:
> > Tried cvs version [1] of texinfo/makeinfo
> >
> > $ makeinfo --version
> > makeinfo (GNU texinfo) 4.8.90
> >
> > But the warning persist. Well, never mind.
>
> Please report this to bug-texinfo, together with a small example (if
> possible).
Done.
Regards
/Karl
_
> Tried cvs version [1] of texinfo/makeinfo
>
> $ makeinfo --version
> makeinfo (GNU texinfo) 4.8.90
>
> But the warning persist. Well, never mind.
Please report this to bug-texinfo, together with a small example (if
possible).
Werner
___
Hi Erik,
browsing the coverage reports, I see
**
uncovered chunk in out-cov/score-performer.cc.gcov
#: 77:Score_performer::disconnect_from_context ()
-: 78:{
#: 79: Dispatcher *d = context ()->get_global_context
()->event_source ();
#: 80: d->re
Hi,
On Wed, 3 Jan 2007, Till Rettig wrote:
> so here comes the new German patch. As for now when making format-patch
> I get three patches.
If you want just the last one, "git format-patch HEAD^" is what you want.
Ciao,
Dscho
___
lilypond-devel mai
Hi,
On Wed, 3 Jan 2007, John Mandereau wrote:
> Till Rettig wrote:
>
> > Do I now understand right that when problems emerge the git pull will
> > save files under different names (or insert the problem signs, as you
> > had it) and then you have to change them and make git update-index on
>
[EMAIL PROTECTED]:
> Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit :
> > Hmm, when building I get:
> >
> > out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
...
> > Does anybody know where the makeinfo with utf-8 support is, a patch ?
>
> AFAIK Texinfo does no ch
21 matches
Mail list logo
