LGTM.
https://codereview.appspot.com/304200043/diff/20001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
https://codereview.appspot.com/304200043/diff/20001/Documentation/notation/rhythms.itely#newcode3436
Documentation/notation/rhythms.itely:3436: the l
Hello,
Here is the current patch countdown list. The next countdown will be on
July 27th.
A quick synopsis of all patches currently in the review process can be
found here:
http://Philholmes.net/lilypond/allura/
__
Push:
4932 Doc: Describe the "midititle" \header variable - Heikki
> Please use 5.x – 4.x is no longer supported.
Or even better 6.x.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "Werner LEMBERG"
> Cc: ;
> Sent: Sunday, July 24, 2016 5:57 PM
> Subject: Re: Gub failure
>
>
>> Werner LEMBERG writes:
>>
Maybe gub still contains an older version? Sorry for not having
checked tha
> OK - so it looks like I should update
> https://github.com/gperciva/gub/blob/master/gub/sources.py to a later
> version of texinfo - possibly 4.13 to move forward but not risk a
> breakage with a new major release?
Please use 5.x – 4.x is no longer supported. At least on my box I can
easily bu
- Original Message -
From: "David Kastrup"
To: "Werner LEMBERG"
Cc: ;
Sent: Sunday, July 24, 2016 5:57 PM
Subject: Re: Gub failure
Werner LEMBERG writes:
Maybe gub still contains an older version? Sorry for not having
checked that before committing.
Indeed, I now see that only
Werner LEMBERG writes:
>> Maybe gub still contains an older version? Sorry for not having
>> checked that before committing.
>
> Indeed, I now see that only texinfo 4.11 is required.
>
> How to proceed? Reverting is easy (commit
> 445bf3bb2fbd1f259fe43ade204fb34d68bdd581, the changes in
> `macr
- Original Message -
From: "Werner LEMBERG"
To:
Cc: ;
Sent: Sunday, July 24, 2016 5:04 PM
Subject: Re: Gub failure
Maybe gub still contains an older version? Sorry for not having
checked that before committing.
Indeed, I now see that only texinfo 4.11 is required.
How to proce
> Maybe gub still contains an older version? Sorry for not having
> checked that before committing.
Indeed, I now see that only texinfo 4.11 is required.
How to proceed? Reverting is easy (commit
445bf3bb2fbd1f259fe43ade204fb34d68bdd581, the changes in
`macros.itexi'). However, I would prefer
"Phil Holmes" writes:
> Looks like this was the problem. I had to edit the file and push it
> to release/unstable since Gub always seems to pull its source files
> from there, so editing locally doesn't work. My normal course would
> be to push this change to staging once I've uploaded the new
> I now got as far as make doc, when the build failed making
> notation.makeinfo, with lots of errors similar to this:
>
> /home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/Documentation/out-www//notation/pitches.texi:4417:
> Unknown command `ragge
- Original Message -
From: "Phil Holmes"
To: "David Kastrup"
Cc:
Sent: Sunday, July 24, 2016 3:53 PM
Subject: Re: Gub failure
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Sunday, July 24, 2016 12:15 PM
Subject: Re: Gub failure
Phil Holmes wr
> Moreover, Ghostscript developers seem to want that `.loadfont' is
> not used.
>
> http://bugs.ghostscript.com/show_bug.cgi?id=696823
> http://bugs.ghostscript.com/show_bug.cgi?id=696824
This is something we can trustfully ignore, I think, given that we
resolve TTCs to Type42 and OTCs to bare C
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Sunday, July 24, 2016 12:15 PM
Subject: Re: Gub failure
Phil Holmes writes:
Trying to build Gub today, I get the following failures:
/home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git
On 2016/07/22 15:27:10, wl_gnu.org wrote:
> ps2pdf -I \
> -dNOSAFER -P \
> Fontless.pdf WithEmbeddedFonts.pdf
This should rather be
ps2pdf -I \
-dNOSAFER \
Fontless.pdf WithEmbeddedFonts.pdf
I've tested with the fonts in the current d
Phil Holmes writes:
> Trying to build Gub today, I get the following failures:
>
> /home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-
> release-unstable/lily/dynamic-performer.cc: In member function 'Real
> Dynamic_performer::compute_departure_volume(Direction, Real, Re
Trying to build Gub today, I get the following failures:
/home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-
release-unstable/lily/dynamic-performer.cc: In member function 'Real
Dynamic_performer::compute_departure_volume(Direction, Real, Real, Real,
Real)':
/home/gub/Ne
> \new Staff { << { g\=Staff.1( a b } >> << { c,\newCommand d e\=Staff.1) } >> }
> Without the command indicating the slur's change in voice, the d and e
> would not be acknowledged by the slur, since it would still belong to
> the voice it started in.
Correction: the c and d would not be acknowle
Hello,
On Tue, Jul 19, 2016 at 3:20 PM, Trevor Daniels wrote:
> You're now a developer AFA SourceForge is concerned, which means you can add
> Issues. There are a few more hoops to jump through before you can submit
> patches.
I have uploaded the patch, thanks.
Having worked on cross-voice
19 matches
Mail list logo
