ypond-user Mailing List (lilypond-user@gnu.org) u...@gnu.org>
> Subject: RE: metronome-mark-alignment
>
> When Metronome_mark_engraver is part of a Score or Staff context,
> MetronomeMarks that coincide with TimeSignatures align by default to the
> TimeSignature. However, I have
Am Mo., 20. Jan. 2020 um 23:52 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mi., 15. Jan. 2020 um 01:23 Uhr schrieb David Kastrup :
> >
> >> We need to put out the difference between # and $ even for beginners.
> >> Basically # can only be used for stuff where you can figure out
Thomas Morley writes:
> Am Mi., 15. Jan. 2020 um 01:23 Uhr schrieb David Kastrup :
>
>> We need to put out the difference between # and $ even for beginners.
>> Basically # can only be used for stuff where you can figure out the
>> meaning in context without even looking at the Scheme expression
Am Mi., 15. Jan. 2020 um 01:23 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 14. Jan. 2020 um 23:39 Uhr schrieb David Kastrup :
> >>
> >> Thomas Morley writes:
> >>
> >> > Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen
> >> > :
> >> >>
> >> >> > The hash mark #
Aaron Hill writes:
> On 2020-01-14 5:18 pm, David Kastrup wrote:
>> No, it's that \notes is identical to $notes (apart from the syntax) in
>> that it creates a copy. So whenever you write \something and do
>> something with it, whatever you do with it will not affect the original
>> stuff
On 2020-01-14 5:18 pm, David Kastrup wrote:
No, it's that \notes is identical to $notes (apart from the syntax) in
that it creates a copy. So whenever you write \something and do
something with it, whatever you do with it will not affect the original
stuff stored in the Scheme variable
Aaron Hill writes:
> On 2020-01-14 2:39 pm, David Kastrup wrote:
>> Ok, let me try again.
>> # and $ differ in several respects. # inserts Scheme constructs in
>> places where LilyPond can decide how they fit into its syntax without
>> looking at their value first. In that case, evaluation of
> -Original Message-
> From: David Kastrup [mailto:d...@gnu.org]
> Sent: Tuesday, January 14, 2020 5:39 PM
> To: Thomas Morley
> Cc: Daniel Rosen ; lilypond-user Mailing List (lilypond-
> u...@gnu.org) ; David Nalesnik
>
> Subject: Re: metronome-mark-alignmen
Thomas Morley writes:
> Am Di., 14. Jan. 2020 um 23:39 Uhr schrieb David Kastrup :
>>
>> Thomas Morley writes:
>>
>> > Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen
>> > :
>> >>
>> >> > The hash mark # method of embedding Scheme is a natural fit for this
>> >> > system.
>> >> > Once
On 2020-01-14 2:39 pm, David Kastrup wrote:
Ok, let me try again.
# and $ differ in several respects. # inserts Scheme constructs in
places where LilyPond can decide how they fit into its syntax without
looking at their value first. In that case, evaluation of those Scheme
expressions is done
Am Di., 14. Jan. 2020 um 23:39 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen
> > :
> >>
> >> > The hash mark # method of embedding Scheme is a natural fit for this
> >> > system.
> >> > Once the lexer sees a hash mark, it
Thomas Morley writes:
> Am Mo., 13. Jan. 2020 um 07:14 Uhr schrieb Daniel Rosen :
>>
>> > The hash mark # method of embedding Scheme is a natural fit for this
>> > system.
>> > Once the lexer sees a hash mark, it calls the Scheme reader to read one
>> > full Scheme
>> > expression (this can be
g List
> > (lilypond-user@gnu.org)
> > Subject: Re: metronome-mark-alignment
> >
> > Though, I've already heard about difficulties about using scheme to write
> > own extension pretty often.
> > Just like you say:
> >
> > Am So., 12. Jan. 2020 um 22:19 Uhr
> -Original Message-
> From: David Kastrup [mailto:d...@gnu.org]
> Sent: Monday, January 13, 2020 7:35 AM
> To: Daniel Rosen
> Cc: Thomas Morley ; lilypond-user Mailing List
> (lilypond-user@gnu.org) ; David Nalesnik
>
> Subject: Re: metronome-mark-alignment
Daniel Rosen writes:
> As far as the Extending manual goes, though... I could be wrong, but
> it seems to assume a basic working knowledge of how computer programs
> and programming languages work that I simply don't have. Going through
> it, I think to myself that I would need to have
> -Original Message-
> From: Thomas Morley [mailto:thomasmorle...@gmail.com]
> Sent: Sunday, January 12, 2020 6:04 PM
> To: Daniel Rosen
> Cc: David Nalesnik ; lilypond-user Mailing List
> (lilypond-user@gnu.org)
> Subject: Re: metronome-mark-alignment
>
>
Hi Daniel,
you may have heard there's a conference soon in Salzburg.
I will have a talk there as well, thus I doubt I can't look into the
problem you've reported before I'm back.
Nevertheless in alzburg I'll talk about user-defined extensions for LilyPond.
During the talk I'll frequently
> -Original Message-
> From: Thomas Morley [mailto:thomasmorle...@gmail.com]
> Sent: Saturday, January 11, 2020 5:37 PM
> To: David Nalesnik
> Cc: Daniel Rosen ; lilypond-user Mailing List (lilypond-
> u...@gnu.org)
> Subject: Re: metronome-mark-alignment
>
>
(get-par parx))
(if(ly:grob? pary)
(get-par pary))
;; the inner function gets called from here
(let* ((result (get-par grob)))
;; check if we found something
(if (ly:grob? result)
result
#f)))
David N
On Saturday, January 11, 2020, Daniel Rosen wrote:
> On Jan 9, 2020, at 4:21 PM, Daniel Rosen wrote:
>
> >> I have a new problem. If I take away the first instance of \music in
> each staff of my original example,
>
>
> > Whoops, meant to say *your* example with the revised function.
>
> >> the
On Jan 9, 2020, at 4:21 PM, Daniel Rosen wrote:
>> I have a new problem. If I take away the first instance of \music in each
>> staff of my original example,
> Whoops, meant to say *your* example with the revised function.
>> the file fails to compile, and I get this error message:
>>
>>>
> my original example
Whoops, meant to say *your* example with the revised function.
DR
> Fantastic. A minor point though: while the example does compile as it should,
> I also get the following text in the log during the preprocessing stage:
>
> > Fontconfig warning: ignoring 1033: not a valid language tag
>
> It doesn't say it's an error or even a warning, but I've never seen it
> The problem is that ly:make-simple-closure has been removed. I replaced
> the old default with the new definition (found in the Internals Reference),
> and the function works again.
Fantastic. A minor point though: while the example does compile as it should, I
also get the following text in
On Wed, Jan 8, 2020 at 7:28 AM David Nalesnik wrote:
>
> Hi Daniel,
>
> On Tue, Jan 7, 2020 at 5:18 PM Daniel Rosen wrote:
> >
> > I just rediscovered David Nalesnik's metronome-mark-alignment function in
> > this thread that I originally started years ago: htt
Hi Daniel,
On Tue, Jan 7, 2020 at 5:18 PM Daniel Rosen wrote:
>
> I just rediscovered David Nalesnik's metronome-mark-alignment function in
> this thread that I originally started years ago: https://bit.ly/2QUmi6H
I just rediscovered it too! Completely forgot I had done this.
>
&g
I just rediscovered David Nalesnik's metronome-mark-alignment function in this
thread that I originally started years ago: https://bit.ly/2QUmi6H
The function works fine as long as Metronome_mark_engraver only exists in the
Score context. However, if it's added to, say, a Staff context
27 matches
Mail list logo
