- Original Message -
From: "Jan Nieuwenhuizen" <[EMAIL PROTECTED]>
> "Chris Jackson" <[EMAIL PROTECTED]> writes:
>
> > Just having fun trying to build the current development version 1.7.21
on
> > Cygwin. I've managed to compile it now, after a few tweaks (e.g. install
>
> That must be f
The new ottava feature is nice! However I'm running into the occasional
problem..
The following causes lilypond to segfault, with the trace given below. This
is 1.7.21 compiled and running on Cygwin, with gcc-2.95.3, guile 1.6, etc.
It only crashes when the midi statement is included, and doesn'
"Chris Jackson" <[EMAIL PROTECTED]> writes:
> Just having fun trying to build the current development version 1.7.21 on
> Cygwin. I've managed to compile it now, after a few tweaks (e.g. install
> complained that /usr/local/share/omf did not exist. Also this time,
> configure could locate python2
Just having fun trying to build the current development version 1.7.21 on
Cygwin. I've managed to compile it now, after a few tweaks (e.g. install
complained that /usr/local/share/omf did not exist. Also this time,
configure could locate python2.2.dll, when it couldn't when I tried to build
1.7.20
[EMAIL PROTECTED] writes:
> On Mon, 16 Jun 2003 10:29:05 +0200
> Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] writes:
> > > At least for this case a warning should be suppressed.
> >
> > OK, i'll opt for the easy fix: removing the warning entirely.
>
> Is it possible to manu
Han-Wen Nienhuys wrote:
I wonder whether using counts is the right solution: it doesn't
reflect typesetting (who ever uses ! ?), nor musical meaning. It
seems like a quick hack. Can't we make up something neater for the
internal presentation?
Good point. Though, I don't have any ideas of a bet
On Mon, 16 Jun 2003 10:29:05 +0200
Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes:
> > At least for this case a warning should be suppressed.
>
> OK, i'll opt for the easy fix: removing the warning entirely.
Is it possible to manually suppress a warning in the ly file? F
[EMAIL PROTECTED] writes:
> Notice that I have not changed the new-accidental-engraver (sigh) so the
> patch does not compile the docu because it complains about the old
> properties. If one removes the new-accidental-engraver then it compiles.
>
> Should really find some better names for accide
Han-Wen Nienhuys wrote:
[stuff snipped]
(are we going to see a patch?)
Attached.
Notice that I have not changed the new-accidental-engraver (sigh) so the
patch does not compile the docu because it complains about the old
properties. If one removes the new-accidental-engraver then it compiles.
[EMAIL PROTECTED] writes:
> [stuff snipped]
(are we going to see a patch?)
> An easy way to implement invisible accidentals would be to add a
> "invisible"-style to the cautionary accidentals - so that one could turn
> accidentals invisible by setting cautionary-style to "invisible" and
> mark
[EMAIL PROTECTED] writes:
> > Phrasing slurs are done normal slur code, and normal slurs should not
> > cross rests.
>
> This is not correct. Consider this, played by a violin:
>
>/\
>O O r O
>| | |
>+--+-+
>
> At least for this case a warning sho
> OK, i'll opt for the easy fix: removing the warning entirely.
Fine with me :-)
Werner
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
> Phrasing slurs are done normal slur code, and normal slurs should not
> cross rests.
This is not correct. Consider this, played by a violin:
/\
O O r O
| | |
+--+-+
At least for this case a warning should be suppressed.
Werner
__
13 matches
Mail list logo
