If it fixes it at all, it would do so upon a recompile of Lilypond
*after* installing the new mftrace. But it looks like that is what
you've done, and still have problems. You saved me the trouble
of trying to build 2.5.14 when I get home. The last problem-free
version for me was 2.5.10.
-
[EMAIL PROTECTED] writes:
> I've got version 2.5.14 up and running (with the exception of the emacs
> mode issue I posted to the user list) and I found something odd. In
> this example:
>
> \version "2.5.14"
>
> \score{
> \relative c{
> \time 3/4
> \set Score.skipBars = ##t
>
Well, on your advice earlier I upgraded to mftrace 1.1.5 when you told
me I needed potrace or autotrace. So, no, I don't think mftrace 1.1.5
fixes this.
On Mon, 2005-03-07 at 17:10 -0800, Daniel Johnson wrote:
> I've heard that mftrace-1.1.5 may fix this. Is this correct?
>
> David Bobroff wrot
I've heard that mftrace-1.1.5 may fix this. Is this correct?
David Bobroff wrote:
I've got version 2.5.14 up and running (with the exception of the emacs
mode issue I posted to the user list) and I found something odd. In
this example:
\version "2.5.14"
\score{
\relative c{
\time
I've got version 2.5.14 up and running (with the exception of the emacs
mode issue I posted to the user list) and I found something odd. In
this example:
\version "2.5.14"
\score{
\relative c{
\time 3/4
\set Score.skipBars = ##t
R2.*2
}
}
I'm getting an i
It seems that the properties are reset at the end of each
(de)crescendo, so it seems you have to specify it again
every time. However, you can save same key strokes by using the
predefined macro \cresc. For example
\cresc c d e f \!
is equivalent to
c \setTextCresc \< d e f \!
Question to the bug-l
