On Fri, 2015-09-04 at 20:20 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > On Fri, 2015-09-04 at 19:25 +0200, David Kastrup wrote:
> >> Richard Shann writes:
> >>
> >> > On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote:
> >> >>
Richard Shann writes:
> On Fri, 2015-09-04 at 20:20 +0200, David Kastrup wrote:
>> Richard Shann writes:
>>
>> > Please correct me if I am wrong, but at the moment I don't know how a
>> > user can place a something at the top of a LilyPond file
I seem to have run into a snag with re-writing
default-time-signature-settings, it works ok if there was previously a
rule for a time signature, but adding a rule for one (such as 6/8) which
has none doesn't result in the beaming pattern being used. Here is a
minimal example. The first bar shows
Richard Shann writes:
> I seem to have run into a snag with re-writing
> default-time-signature-settings, it works ok if there was previously a
> rule for a time signature, but adding a rule for one (such as 6/8) which
> has none doesn't result in the beaming pattern
Richard Shann writes:
> On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote:
>> Richard Shann writes:
>>
>> > I seem to have run into a snag with re-writing
>> > default-time-signature-settings, it works ok if there was previously a
>> >
On Fri, 2015-09-04 at 19:25 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote:
> >> Richard Shann writes:
> >>
> >> > I seem to have run into a snag with re-writing
> >> >
Richard Shann writes:
> On Fri, 2015-09-04 at 19:25 +0200, David Kastrup wrote:
>> Richard Shann writes:
>>
>> > On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote:
>> >> Richard Shann writes:
>> >>
>> >> > I seem
On Fri, 2015-09-04 at 18:56 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > I seem to have run into a snag with re-writing
> > default-time-signature-settings, it works ok if there was previously a
> > rule for a time signature, but adding a rule for one (such
Richard Shann writes:
> On Wed, 2015-09-02 at 20:13 +0200, David Kastrup wrote:
>>
>> > And there is a comment somewhere about using | to separate
>> something,
>> > I guess bars with the same \time signature (or, indeed different
>> > ones).
>>
>> No, it's always for
On Thu, 2015-09-03 at 10:54 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > On Wed, 2015-09-02 at 20:13 +0200, David Kastrup wrote:
> >>
> >> > And there is a comment somewhere about using | to separate
> >> something,
> >> > I guess bars with the same \time
Richard Shann writes:
> On Thu, 2015-09-03 at 10:54 +0200, David Kastrup wrote:
>> Richard Shann writes:
>>
>> > On Wed, 2015-09-02 at 20:13 +0200, David Kastrup wrote:
>> >>
>> >> > And there is a comment somewhere about using | to separate
On Thu, 2015-09-03 at 12:59 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > On Thu, 2015-09-03 at 10:54 +0200, David Kastrup wrote:
> >> Richard Shann writes:
> >>
> >> > On Wed, 2015-09-02 at 20:13 +0200, David Kastrup wrote:
> >> >>
On Tue, 2015-09-01 at 21:04 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > I've been trying to use the music function \beamExceptions
>
> "scheme function"
Is that to say that this should be called a scheme function not a music
function? I found it
On Wed, 2015-09-02 at 20:13 +0200, David Kastrup wrote:
>
> > And there is a comment somewhere about using | to separate
> something,
> > I guess bars with the same \time signature (or, indeed different
> > ones).
>
> No, it's always for exactly one time signature, but at the time it is
>
Am 02.09.2015 um 21:35 schrieb Richard Shann:
On Wed, 2015-09-02 at 20:13 +0200, David Kastrup wrote:
And there is a comment somewhere about using | to separate
something,
I guess bars with the same \time signature (or, indeed different
ones).
No, it's always for exactly one time signature,
Richard Shann writes:
> On Tue, 2015-09-01 at 21:04 +0200, David Kastrup wrote:
>> Richard Shann writes:
>>
>> > I've been trying to use the music function \beamExceptions
>>
>> "scheme function"
>
> Is that to say that this should be called a
On Tue, 2015-09-01 at 22:06 +0200, Simon Albrecht wrote:
> Hello Richard,
>
> if you want to use \beamExceptions, it seems like the only way to do this is
> %%
> \version "2.19.25"
>
> {
>\time 4/4
>\set Timing.beamExceptions = \beamExceptions { 8[] 8[ 8] 8[] 8[] 8[
> 8 8] }
>
Am 02.09.2015 um 21:35 schrieb Richard Shann:
I guess I would know the answer to this if I could find out
what the alist holds initially, but my feeble attempt to elicit this via
\void \displayScheme #beamExceptions
gave me
#>
You can display the list of beam exceptions currently in effect by
Richard Shann writes:
> I've been trying to use the music function \beamExceptions
"scheme function"
> which is in version 2.19.25, I can't find anything much to document it
> though. For example, trying this
>
> \version "2.19.25"
>
> MvmntIVoiceI = {
> e'8[
Hello Richard,
if you want to use \beamExceptions, it seems like the only way to do this is
%%
\version "2.19.25"
{
\time 4/4
\set Timing.beamExceptions = \beamExceptions { 8[] 8[ 8] 8[] 8[] 8[
8 8] }
e'8 f' g' a' b' a' g' f'
}
%%
– that’s a bit cumbersome and IMO it
20 matches
Mail list logo