On Monday 19 June 2006 16:02, Erik Sandberg wrote:
> On 6/19/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > Erik Sandberg schreef
> > > BTW: May I change Sequential_iterator::get_music_list to return
> > > something like scm_call_1 (get_music ()->get_property
> > > ("child-list-callback"), get
On Monday 26 June 2006 18:43, Han-Wen Nienhuys wrote:
> Erik Sandberg schreef:
> > On Monday 26 June 2006 10:33, Graham Percival wrote:
> >> On Mon, 26 Jun 2006 08:34:21 +0200
> >>
> >> Erik Sandberg <[EMAIL PROTECTED]> wrote:
> >>> .. and the following works fine in both cases:
> >>> \featherDura
Erik Sandberg schreef:
On Monday 26 June 2006 18:41, Han-Wen Nienhuys wrote:
How's the complete picture now? (reg test compiles etc.?)
regtest compiles nicely.
ok, please apply.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for M
On Monday 26 June 2006 18:41, Han-Wen Nienhuys wrote:
>
> How's the complete picture now? (reg test compiles etc.?)
regtest compiles nicely.
--
Erik
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypo
For a while I've been musing on how to make LSR more visible/useful,
and now I have some time to play with it.
I also don't think it's Google indexable, at least in the snippets. Is
there some way to make it more visible in that respect as well?
Geoff
_
On Mon, Jun 26, 2006 at 12:29:24PM +0200, Karl Hammar wrote:
> > ps: do we really still have to use backticks instead of $(...)?
> > Anyone running LilyPond on old systems with rotten shells?
>
> configure is about portability, why not keep the backticks?
> The same goes for shells with 32bit int
Erik Sandberg schreef:
On Monday 26 June 2006 10:33, Graham Percival wrote:
On Mon, 26 Jun 2006 08:34:21 +0200
Erik Sandberg <[EMAIL PROTECTED]> wrote:
.. and the following works fine in both cases:
\featherDurations
#(ly:make-moment 5 4)
{ c16 c c c c c c }
I've modified the example in
Erik Sandberg schreef:
On Monday 26 June 2006 16:49, Erik Sandberg wrote:
On 6/26/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Erik Sandberg schreef:
I guess this is an academic music representation issue: Do you think
that there is a fundamental difference (non-syntactically) between
event
On Monday 26 June 2006 16:49, Erik Sandberg wrote:
> On 6/26/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > Erik Sandberg schreef:
> > > I guess this is an academic music representation issue: Do you think
> > > that there is a fundamental difference (non-syntactically) between
> > > events wi
On Monday 26 June 2006 10:33, Graham Percival wrote:
> On Mon, 26 Jun 2006 08:34:21 +0200
>
> Erik Sandberg <[EMAIL PROTECTED]> wrote:
> > .. and the following works fine in both cases:
> > \featherDurations
> > #(ly:make-moment 5 4)
> > { c16 c c c c c c }
>
> I've modified the example in the
On 6/26/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Erik Sandberg schreef:
> I guess this is an academic music representation issue: Do you think that
> there is a fundamental difference (non-syntactically) between events with
> postfix syntax, and other events?
No, and that's why I oppose
[EMAIL PROTECTED]:
...
> Unfortunately, configure completely bails out then using something like
>
> $ PYTHON=/usr/local/bin/python2.4 ./configure ...
>
> The problem is in STEPMAKE_GETVERSION, since it takes the first
> line that looks like it contains a version number of the output
> from [Pat
Erik Sandberg schreef:
Something strange is happening in that code; I don't think it's my fault: If
you add another note, it crashes both with and without my patch, and the
graphical output when using only 8 notes is incorrect without my patch.
More concretely, the following works poorly witho
Erik Sandberg schreef:
The attached patch solves this problem: a music class 'post-event is added,
which contains events such as GlissandoEvent, that have no duration
and that should be attached to notes. That way, there is a way to distinguish
between music identifiers and post-event-identifi
Bruce McIntyre schreef:
You will find that in most usual cases, Lilypond matches this Score utility.
Where Lilypond falls behind is in the treatment of crazy-big clusters and in off
the staff chords where the accidentals fall halfway on the leger-lines.
Werner once posted a better solution to
On Mon, 26 Jun 2006 08:34:21 +0200
Erik Sandberg <[EMAIL PROTECTED]> wrote:
> .. and the following works fine in both cases:
> \featherDurations
> #(ly:make-moment 5 4)
> { c16 c c c c c c }
I've modified the example in the NEWS file to only use 7 notes;
everything else compiles cleanly.
Ch
16 matches
Mail list logo
