Hi there,
> It would provide a way for people who should learn how to use version control
> to kick that can down the road a while longer.
Well put. =)
I'm happy to work with Jean and Valentin's suggestions/snippets for now.
Thanks to everyone for the helpful input!
— Kieren
On Mon, Jan 24, 2022 at 05:02:14PM -0800, Flaming Hakama by Elaine wrote:
>On Mon, Jan 24, 2022 at 3:40 PM Kieren MacMillan
><[1]kie...@kierenmacmillan.info> wrote:
[...]
> I think it's fair to state that the vast majority of people using
> Lilypond don't use version control.
>
>
On Mon, Jan 24, 2022 at 3:40 PM Kieren MacMillan <
kie...@kierenmacmillan.info> wrote:
> Hi Elaine,
>
> > You're probably not going to appreciate this suggestion,
> > because it does not aspire to the auto-magic you desire.
> > However, it is clear to me that the best practice for all software dev
Kieren MacMillan writes:
>> So? I can assure you my kitchen table is perfectly useful for me even
>> though the carpenter did not constrain themselves to use only the kind
>> of tools that I myself have in the house.
>>
>> And frankly, I would not think of paying them for the additional effort
> So? I can assure you my kitchen table is perfectly useful for me even
> though the carpenter did not constrain themselves to use only the kind
> of tools that I myself have in the house.
>
> And frankly, I would not think of paying them for the additional effort
> taken by hobbling themselves i
Kieren MacMillan writes:
> Hi Elaine,
>
>> You're probably not going to appreciate this suggestion,
>> because it does not aspire to the auto-magic you desire.
>> However, it is clear to me that the best practice for all software
>> dev is to use commit messages.
>
> I do appreciate the detailed
Hi Elaine,
> You're probably not going to appreciate this suggestion,
> because it does not aspire to the auto-magic you desire.
> However, it is clear to me that the best practice for all software dev is to
> use commit messages.
I do appreciate the detailed and considered response.
That bein
>
>
> -- Forwarded message --
> From: Kieren MacMillan
> To: David Kastrup
> Cc: Lilypond-User Mailing List
> Bcc:
> Date: Sat, 22 Jan 2022 17:34:31 -0500
> Subject: Re: Extracting a "score diff" from two [or more] Lilypond sources
> Hi
Hello Kieren,
as long as we can store the Information in the file such formatting things can
be easily done from within Lilypond. I'll try to do a small example.
Cheers,
Valentin
23.01.2022 17:32:01 Kieren MacMillan :
> Hi Valentin,
>
>> What about this: We could have a small script that take
Hi Valentin,
> What about this: We could have a small script that takes a diff of the new
> file
> and the old file and creates a new version of the new file where all changed
> (music) lines are tagged. This way we do not need to try to match two streams
> against the other one, but we do in
Hi Kieren,
What about this: We could have a small script that takes a diff of the new file
and the old file and creates a new version of the new file where all changed
(music) lines are tagged. This way we do not need to try to match two streams
against the other one, but we do in already know
Hi Valentin,
> While it is theoretically possible to compare two streams of music events
> it would also require lots of logic to properly do what we want.
I'm up to the challenge of building that logic! =)
> One way to achieve what you want could be storing the
> whole history in the source.
Hi Jean,
> Minimal, but perhaps already usable?
Astounding! I think this is totally useable for my purposes!
Once this workshop is over, I'm going to dive in and see if I can turn this
into an 'update reporting framework'.
Thank you so much.
Kieren
Hi Kieren,
While it is theoretically possible to compare two streams of music events it
would also require lots of logic to properly do what we want.
One way to achieve what you want could be storing the whole history in the
source.
I have recently sent out this showcase example of how we can
Le 23/01/2022 à 00:14, Jean Abou Samra a écrit :
Le 22/01/2022 à 22:51, Kieren MacMillan a écrit :
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a
"diff file" describing the musical differences *as would be perceived
by a human reading the score*. For example,
on behalf of Kieren MacMillan
Sent: Saturday, January 22, 2022 3:34 PM
To: David Kastrup
Cc: Lilypond-User Mailing List
Subject: Re: Extracting a "score diff" from two [or more] Lilypond sources
Hi David,
> What version control system are you using for your score? It will
> pro
Le 22/01/2022 à 22:51, Kieren MacMillan a écrit :
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a "diff
file" describing the musical differences *as would be perceived by a human reading
the score*. For example, given
Score #1 = \score { \new Staff << { c'1
Hi David,
> What version control system are you using for your score? It will
> probably easiest to look at the source code diffs and do a manual
> summary from those.
The problem is that during various stages of composition / arranging /
engraving / coding:
1. there can be huge differences
Kieren MacMillan writes:
> p.s. Motivating use case:
>
> I'm cranking out scores for my newest musical
> (https://www.ccpacanada.com/the-quest/). Rehearsals started on
> Tuesday, and changes always come fast and furious during the
> workshopping of a brand new piece. Every time I send the Musical
p.s. Motivating use case:
I'm cranking out scores for my newest musical
(https://www.ccpacanada.com/the-quest/). Rehearsals started on Tuesday, and
changes always come fast and furious during the workshopping of a brand new
piece. Every time I send the Musical Director an updated score, I would
Hi all!
Given multiple Lilypond sources, I'm hoping to find a way to output a "diff
file" describing the musical differences *as would be perceived by a human
reading the score*. For example, given
Score #1 = \score { \new Staff << { c'1 c' } >> }
Score # 2 = \score { \new Staff \new V
21 matches
Mail list logo
