Knut Petersen writes:
> Am 19.09.2016 um 14:29 schrieb Simon Albrecht:
>> Sorry, Knut, but this is a totally inacceptable report. It’s not
>> clear what you want, and you come up with an example of 300+ lines
>> of code.
>
> There are times where you cannot see the wood for the trees. I posted
>
Am 19.09.2016 um 14:29 schrieb Simon Albrecht:
Sorry, Knut, but this is a totally inacceptable report. It’s not clear what you
want, and you come up with an example of 300+ lines of code.
There are times where you cannot see the wood for the trees. I posted the
original mail because
I was una
Am 19.09.2016 um 14:29 schrieb Simon Albrecht:
Sorry, Knut, but this is a totally inacceptable report. It’s not clear what you want, and you come up with an example of 300+ lines of code.
There are times where you cannot see the wood for the trees. I posted the
original mail because
I was unab
On 20/09/16 10:58, Simon Albrecht wrote:
> On 19.09.2016 17:12, Wols Lists wrote:
>> On 19/09/16 13:29, Simon Albrecht wrote:
>>> On 19.09.2016 14:17, Knut Petersen wrote:
Hi everybody!
As far as I understand after \bar "" a \break is permitted in the
middle of a bar.
Lilyp
On 19.09.2016 17:12, Wols Lists wrote:
On 19/09/16 13:29, Simon Albrecht wrote:
On 19.09.2016 14:17, Knut Petersen wrote:
Hi everybody!
As far as I understand after \bar "" a \break is permitted in the
middle of a bar.
Lilypond is supposed to engrave the next barline at the proper place.
At t
2016-09-19 14:17 GMT+02:00 Knut Petersen :
> Hi everybody!
>
> As far as I understand after \bar "" a \break is permitted in the middle of
> a bar.
> Lilypond is supposed to engrave the next barline at the proper place.
>
> At the marked places ( FIXME/ BUG) in the attached score lilypond needs to
sorry for the noise.
2016. szept. 19. 18:46 ezt írta ("David Kastrup" ):
> Benkő Pál writes:
>
> >> c2 \bar "" \break c2 c4
> >>
> >> That should be two bars with a barline in the middle.
> >
> > I think not; \bar "" starts a new bar (after issuing a warning for the
> > incomplete bar).
>
> Seri
Benkő Pál writes:
>> c2 \bar "" \break c2 c4
>>
>> That should be two bars with a barline in the middle.
>
> I think not; \bar "" starts a new bar (after issuing a warning for the
> incomplete bar).
Seriously, does anybody these days bother testing stuff before making
statements? First this min
At 17:39 on 19 Sep 2016, Benkő Pál wrote:
>> c2 \bar "" \break c2 c4
>>
>> That should be two bars with a barline in the middle.
>
>I think not; \bar "" starts a new bar (after issuing a warning for the
>incomplete bar).
Is it really so hard to test something before sending an email
asserting th
On 19/09/16 16:39, Benkő Pál wrote:
>> c2 \bar "" \break c2 c4
>>
>> That should be two bars with a barline in the middle.
>
> I think not; \bar "" starts a new bar (after issuing a warning for the
> incomplete bar).
>
Ummm ... but if that's the case, that's his problem.
HOWEVER. Has lily's beha
> c2 \bar "" \break c2 c4
>
> That should be two bars with a barline in the middle.
I think not; \bar "" starts a new bar (after issuing a warning for the
incomplete bar).
p
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/ma
On 19/09/16 13:29, Simon Albrecht wrote:
> On 19.09.2016 14:17, Knut Petersen wrote:
>> Hi everybody!
>>
>> As far as I understand after \bar "" a \break is permitted in the
>> middle of a bar.
>> Lilypond is supposed to engrave the next barline at the proper place.
>>
>> At the marked places ( FIX
On 19.09.2016 14:17, Knut Petersen wrote:
Hi everybody!
As far as I understand after \bar "" a \break is permitted in the
middle of a bar.
Lilypond is supposed to engrave the next barline at the proper place.
At the marked places ( FIXME/ BUG) in the attached score lilypond
needs to be
force
Hi everybody!
As far as I understand after \bar "" a \break is permitted in the middle of a
bar.
Lilypond is supposed to engrave the next barline at the proper place.
At the marked places ( FIXME/ BUG) in the attached score lilypond needs to be
forced to print a barline ... I think this is a bu
14 matches
Mail list logo
