Hi list,
it’s possible to write something like
%
ambitus = \layout {
\context {
\Voice
\consists Ambitus_engraver
}
}
\score {
\relative { c' d e f g a b c }
\ambitus
}
%
or put the \layout variable in a \layout block:
%%
2018-07-15 9:24 GMT+02:00 Malte Meyn :
> Hi list,
>
> it’s possible to write something like
>
> %
> ambitus = \layout {
> \context {
> \Voice
> \consists Ambitus_engraver
> }
> }
>
> \score {
> \relative { c' d e f g a b c }
> \ambitus
> }
> %
Am 15.07.2018 um 09:24 schrieb Malte Meyn:
Hi list,
it’s possible to write something like
%
ambitus = \layout {
\context {
\Voice
\consists Ambitus_engraver
}
}
\score {
\relative { c' d e f g a b c }
\ambitus
}
%
or put the \l
Urs Liska writes:
> Am 15.07.2018 um 09:24 schrieb Malte Meyn:
>
>> Currently, that gives an “error: bad expression type” for
>> \musicaFicta. If not putting \ambitus and \musicaFicta in another
>> \layout layer, that will give two scores, one with Ambitus_engraver
>> and one with suggestAccident
On 15.07.2018 16:48, David Kastrup wrote:
What? Being able to specify two conflicting \layout definitions at once
and having LilyPond magically merge them by guessing correctly how the
user wants every conflict to be resolved?
Magic is always a great thing to wish for. Until it does stuff you
Am 15.07.2018 um 17:36 schrieb Simon Albrecht:
On 15.07.2018 16:48, David Kastrup wrote:
What? Being able to specify two conflicting \layout definitions at once
and having LilyPond magically merge them by guessing correctly how the
user wants every conflict to be resolved?
Magic is always a
Simon Albrecht writes:
> On 15.07.2018 16:48, David Kastrup wrote:
>> What? Being able to specify two conflicting \layout definitions at once
>> and having LilyPond magically merge them by guessing correctly how the
>> user wants every conflict to be resolved?
>>
>> Magic is always a great thing
Hello everybody,
this combination of a custom music function that combines the music
simultaneously with itself and a \once\offset command causes LilyPond to
crash (exit with return code 11):
\version "2.19.82"
test =
#(define-music-function (parser location mus) (ly:music?)
#{
On 2018-07-15 18:21, Simon Albrecht wrote:
Hello everybody,
this combination of a custom music function that combines the music
simultaneously with itself and a \once\offset command causes LilyPond
to crash (exit with return code 11):
\version "2.19.82"
test =
#(define-music-functi
Hello,
On Sun, 15 Jul 2018 09:24:22 +0200, Malte Meyn wrote:
> Hi list,
>
> it’s possible to write something like
>
>
> Cheers,
> Malte
I created https://sourceforge.net/p/testlilyissues/issues/5382/ for this
request.
James
___
bug-lilypond
Hello,
On Sun, 15 Jul 2018 20:09:52 -0700, Aaron Hill wrote:
> On 2018-07-15 18:21, Simon Albrecht wrote:
> > Hello everybody,
> >
> > this combination of a custom music function that combines the music
> > simultaneously with itself and a \once\offset command causes LilyPond
> > to crash (exit
On Sun, 15 Jul 2018 08:05:05 +0200, Malte Meyn wrote:
>
> Am 14.07.2018 um 23:40 schrieb foxfanfare:
> > I found a strange bug when using the magnifyStaff tool. In this example, you
> > can see a collusion between the clef and the time signature occurs when the
> > lowest staff is smaller (and
12 matches
Mail list logo
