2018-01-16 14:37 GMT+01:00 Urs Liska :
> But you should also look into the openLilyLib files, create a copy of the
> function and try removing the \markup wrapper. This \markup is added
> explicitly so it seems more efficient not to do that in the first place
> instead of removing it afterwards.
>
Thanks URS,
Another great idea for me to try!
Cheers,
Ben
On Jan 16, 2018 08:37, "Urs Liska" wrote:
>
>
> Am 16.01.2018 um 14:27 schrieb Ben Beeson:
>
> Hi,
>
> Wow, that looks very promising. I am looking at this note on my cell
> phone right now, so I cannot test it just yet. I will try th
Am 16.01.2018 um 14:27 schrieb Ben Beeson:
Hi,
Wow, that looks very promising. I am looking at this note on my cell
phone right now, so I cannot test it just yet. I will try this later
when I get home and see what happens.
But you should also look into the openLilyLib files, create a copy
Hi,
Wow, that looks very promising. I am looking at this note on my cell phone
right now, so I cannot test it just yet. I will try this later when I get
home and see what happens.
Thanks very much for this!
Cheers,
Ben
On Jan 15, 2018 21:38, "Flaming Hakama by Elaine"
wrote:
On Sun, Ja
On Sun, Jan 14, 2018 at 4:10 PM, Urs Liska wrote:
> Hi Ben,
>
> Actually I misread your original post and referred you to what you already
> had.
>
> Elaine's hint is true but won't bring you any further because that's what
> is already happening in the background when you use the \gitCommittish
On Sun, 2018-01-14 at 12:17 -0800, Flaming Hakama by Elaine wrote:
>> > -- Forwarded message ----------
>> > From: Ben Beeson
>> > To: David Kastrup , lilypond-user > > rg>
>> > Subject: Re: How to append a git version to an output filename
>> &
n, 2018-01-14 at 12:17 -0800, Flaming Hakama by Elaine wrote:
> > -- Forwarded message --
> > From: Ben Beeson
> > To: David Kastrup , lilypond-user > rg>
> > Subject: Re: How to append a git version to an output filename
> > Hi David,
> &
Hi,
when I've seen the inclusion of git information on lilypondblog [1], I
liked it and adapted it to my taste:
Of course one can include a whole git log in the score, but the only
thing I was interested in is this: If I have a printed score or a PDF, I
want to know which version that was. All th
Ben Beeson writes:
> Hi David,
>
> It has been a while since I visited the site, but more information on
> using git with scores is available at:
> http://lilypondblog.org/2014/04/printing-git-versioning-info-in-a-score
> /
> Urs Liska and Lars Haulin provide some excellent tools and commentary
Hi David,
It has been a while since I visited the site, but more information on
using git with scores is available at:
http://lilypondblog.org/2014/04/printing-git-versioning-info-in-a-score
/
Urs Liska and Lars Haulin provide some excellent tools and commentary
with a link to the current definit
Hi Ben,
2018-01-14 17:26 GMT+01:00 David Kastrup :
> Ben Beeson writes:
>
>> Hi David,
>> Here is how I get the \gitCommitish in the tagline. First, include the
>> "gitDefinitions.ily" file.
>
> What is that?
>
>> I use something like this:
>>
>> \include "/home/workspace/include/gitDefinitions.i
Ben Beeson writes:
> Hi David,
> Here is how I get the \gitCommitish in the tagline. First, include the
> "gitDefinitions.ily" file.
What is that?
> I use something like this:
>
> \include "/home/workspace/include/gitDefinitions.ily"
>
> Then in the header declaration, add the \gitCommitish an
Hi David,
Here is how I get the \gitCommitish in the tagline. First, include the
"gitDefinitions.ily" file. I use something like this:
\include "/home/workspace/include/gitDefinitions.ily"
Then in the header declaration, add the \gitCommitish and any other
items desired to the tagline entry:
Am 14.01.2018 um 11:44 schrieb Andrew Bernard:
Hi Ben,
I think the desire to add git version information to files is a
hangover from earlier days when people used to do this with SCCS, CVS,
RCS, and all those antique systems. With git, due to its model, that's
not so commonly done nowadays.
Hi Ben,
I think the desire to add git version information to files is a hangover
from earlier days when people used to do this with SCCS, CVS, RCS, and all
those antique systems. With git, due to its model, that's not so commonly
done nowadays.
If you want to manage your files by the complex git
Hi Ben,
Am 14.01.2018 um 03:17 schrieb Ben Beeson:
Hello all,
I am using git to keep track of edits to scores and am presently using
\bookOutputName "score-filename"
to write the output filename for the pdf that is generated in the
LilyPond "ly" file. I am also using
"git Version: \gitComm
Ben Beeson writes:
> Hello all,
>
> I am using git to keep track of edits to scores and am presently using
>
>
> \bookOutputName "score-filename"
>
> to write the output filename for the pdf that is generated in the
> LilyPond "ly" file. I am also using
>
> "git Version: \gitCo
Hello all,
I am using git to keep track of edits to scores and am presently using
\bookOutputName "score-filename"
to write the output filename for the pdf that is generated in the
LilyPond "ly" file. I am also using
"git Version: \gitCommitish "
in the tagline so the g
18 matches
Mail list logo
