Hi k\Kevin and All,
It ranks as one of the most bizarre bugs I have ever seen (and I speak as a
software developer of many decades). It's only with Frescobaldi. Command
line compilation is fine. It's only dynamic markings, which is puzzling -
whatever is going on? Running sync of course I tried, t
> Didn't seem to help unfortunately. So far it really seems that LilyPond
> behaves inconsistently in this case when run as a subprocess of Frescobaldi.
How bizarre. I wonder what difference there could possibly be that
would make files appear to have different content. Does this issue
occur in Fr
Am 12.11.18 um 22:15 schrieb Graham King:
On 9 Nov 2018, at 14:07, Andrew Bernard wrote:
I do not know
how to get the lilypond command for compiling out of Frescobaldi to examine.
...but you might be able to get it out of the process table by using the Linux command
"ps" with a suitable fla
On 9 Nov 2018, at 14:07, Andrew Bernard wrote:
> I do not know
> how to get the lilypond command for compiling out of Frescobaldi to examine.
...but you might be able to get it out of the process table by using the Linux
command "ps" with a suitable flag (see "man ps" on your distro). This ne
Am Mo., 12. Nov. 2018 um 19:28 Uhr schrieb Malte Meyn :
>
>
>
> Am 12.11.18 um 18:07 schrieb Torsten Hämmerle:
> > Hi Malte,
> >
> > That's strange, but it seems to be related to the *3 (length factor) used in
> > g1*3.
> > Restricting the use of these multipliers to full measure rests (i.e. writin
Am 12.11.18 um 18:07 schrieb Torsten Hämmerle:
Hi Malte,
That's strange, but it seems to be related to the *3 (length factor) used in
g1*3.
Restricting the use of these multipliers to full measure rests (i.e. writing
g1 s1*2) I couldn't reproduce the effect.
Can you confirm this?
I can confi
Hi Malte,
That's strange, but it seems to be related to the *3 (length factor) used in
g1*3.
Restricting the use of these multipliers to full measure rests (i.e. writing
g1 s1*2) I couldn't reproduce the effect.
Can you confirm this?
Thanks
Torsten
--
Sent from: http://lilypond.1069038.n5.nabb
Am 12.11.18 um 17:05 schrieb Malte Meyn:
Hi list,
the following code produces measures of different length: The measures
containing a ChordName are narrower than the others. That’s a bug, isn’t
it?
%
\version "2.19.82"
Same for 2.12.3 t
Hi list,
the following code produces measures of different length: The measures
containing a ChordName are narrower than the others. That’s a bug, isn’t it?
%
\version "2.19.82"
<<
\chords {
s1*4 % try also s1*3 and see the line break
