Hi Ralph, Grégoire,
On 24/10/15 11:12, Ralph Corderoy wrote:
> Hi Grégoire,
>
> Keith wrote:
>>> OK, I reinstalled groff-base 1.22.3-1 and groff 1.22.3-1 with dpkg
>>> -i.
>>
>> Those are binary packages.
>>
>>> The patch is made for /contrib/glilypond/glilypond.pl The new groff
>>> works fine,
Hi Grégoire,
Keith wrote:
> > OK, I reinstalled groff-base 1.22.3-1 and groff 1.22.3-1 with dpkg
> > -i.
>
> Those are binary packages.
>
> > The patch is made for /contrib/glilypond/glilypond.pl The new groff
> > works fine, but now, I cannot find the /contrib directory:
>
> You need the sour
On 23/10/15 10:13, Grégoire Babey wrote:
> OK, I reinstalled groff-base 1.22.3-1 and groff 1.22.3-1 with
> dpkg -i.
Those are binary packages.
> The patch is made for /contrib/glilypond/glilypond.pl The new groff
> works fine, but now, I cannot find the /contrib directory:
You need the source p
Hi Ralph,
> DESCRIPTION
> locate reads one or more databases prepared by updatedb(8) and
> writes file names matching at least one of the PATTERNs to
> standard output, one per line.
>
> That database is probably updated once a night so it won't have files
> you've jus
Hi Grégoire,
> OK, I reinstalled groff-base 1.22.3-1 and groff 1.22.3-1 with dpkg
> -i. The patch is made for /contrib/glilypond/glilypond.pl The new
> groff works fine, but now, I cannot find the /contrib directory:
>
> $ locate glilypond
You say find, but use locate(1).
DESCRIPTION
Thank you Ralph!
Le dimanche 18 octobre 2015 à 10:21 +0100, Ralph Corderoy a écrit :
> This is because you've already applied the patch to this tree of groff
> source. If you want to keep testing your patch then you need to get
> back to an unpatched version each time, e.g. unpack the tar file.
Hi Grégoire,
> According to your informations, I tried now this:
>
> $ patch -p1 < /home/gregexp/Bureau/patch0glilypond
> patching file contrib/glilypond/ChangeLog
> Reversed (or previously applied) patch detected! Assume -R? [n]
This is because you've already applied the patch to this tree of g
Thank you Keith and Ralph !
According to your informations, I tried now this:
gregexp@greg-desktop:~/.local/share/Trash/files/groff-1.22.3$ patch -p1
< /home/gregexp/Bureau/patch0glilypond
patching file contrib/glilypond/ChangeLog
Reversed (or previously applied) patch detected! Assume -R? [n]
Hi Grégoire,
Keith's already pointed out -p1 is what's needed. You tried this.
> groff-1.22.3$ patch -p1 patching file contrib/glilypond/ChangeLog
> Hunk #1 succeeded at 1 with fuzz 1.
> patching file contrib/glilypond/glilypond.pl
> patch unexpectedly ends in middle of line
> Hunk #1 succeeded
On 16/10/15 23:55, Grégoire Babey wrote:
> gregexp@greg-desktop:~/.local/share/Trash/files/groff-1.22.3$ patch -p0
> < /home/gregexp/Bureau/patch1glilypond
> can't find file to patch at input line 5
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
>
Hi Werner,
I tried again to come on patching my new groff version.
Le mercredi 13 mai 2015 à 11:14 +0200, Werner LEMBERG a écrit :
> Note that you should be in groff's
> top-level directory while applying such patches so that all
> subdirectories can be correctly found if necessary.
OK, I ca
> I have zero experience in patching files.
> I try to learn about that in the web.
Mastering the `patch' and `diff' programs is really essential IMHO :-)
> Now I took this code: [...]
>
> I made it to a file named "patch1glilypond" and apply the command:
>
> patch -p1 < /home/gregexp/Bureau/pat
Le samedi 21 mars 2015 à 00:24 +0100, Werner LEMBERG a écrit :
> It's a patch that converts your version of glilypond to something that
> works.
Thanks a lot Werner,
I have zero experience in patching files.
I try to learn about that in the web.
Now I took this code:
diff --git a/contrib/glil
> Sorry I don't understand what the attachement exactly means.
It's a patch that converts your version of glilypond to something that
works.
> Can I just copy the code on git and replace the code of glilypond.pl
> on my machine with it?
Yes, this works too.
Werner
Werner,
great, thank you very much.
Sorry I don't understand what the attachement exactly means.
Can I just copy the code on git and replace the code of glilypond.pl on
my machine with it?
Grégoire
Le vendredi 20 mars 2015 à 07:07 +0100, Werner LEMBERG a écrit :
> Grégoire,
>
>
> there wa
> Here, it spots two more flaws. [...]
Committed, thanks.
> glilypond.pl has `use warnings' and friends at the start, but they are
> commented out.
Well, Bernd should take care of it. Unfortunately, he doesn't reacty
since a longer time...
Werner
Hi Werner,
> there was a typo in glilypond.pl, now fixed in git (see attached
> diff).
...
> --- a/contrib/glilypond/glilypond.pl
> +++ b/contrib/glilypond/glilypond.pl
> @@ -546,7 +546,7 @@ our $Read =
> $ly = new FH_FILE($path_ly);
>
> my $include
Grégoire,
there was a typo in glilypond.pl, now fixed in git (see attached
diff). With the patch
foo bar
.lilypond include example.mscz.ly
bar baz
works just fine.
> the 3 commands you have given to me are working fine.
... don't forget to add `-dNOSAFER' to ps2pdf.
Werner
Fr
Thank you Werner,
the 3 commands you have given to me are working fine.
From Lilypond to groff, there is no problem.
If you write the notes with Musescore first (which is a GUI-programm for
writing music), and save it in .ly-format, you get much more code.
I join a small example (c e g e) as a
> 2. copy this Musescore .ly-code into a groff input-text,
> between the 2 requests
>
> .lilypond start
> and
> .lilypond end
OK.
> 3. groff it using the 3 commands:
>
> glilypond foo > foo1
> groff foo1 > foo1.ps
This is OK in case you don't need macro packages.
> ps2pdf foo1.ps > foo1.p
Hi groffers,
this morning, I tried to fit some lines of music into groff-text,
starting this time from Musescore.
I thought, you could
1. write music with Musescore, save it as .ly.
(I call that "Musescore .ly-code").
2. copy this Musescore .ly-code into a groff input-text,
between the 2 re
21 matches
Mail list logo
