I've written something that removes duplicate markups (resulting from
partcombine). Maybe that's interesting for you?
I can't look it up without computer but you could try locating it at
git.openlilylib.org
- das trunkne lied
- code (files?)
- library/ly/something
HTH
Urs
Am 22. August 2015
That's overengineering in my opinion. GUILE's own header macros take
all the given parameters so we get a discrepancy when LilyPond's
equivalents don't do so.
Unless there is a very compelling reason to indulge in this sort of
thing (and the template pokery-trickery in lily-guile-macros.hh is
Dan Eble d...@faithful.be writes:
Can anyone offer general architectural advice for adding the option
for parts on the same staff to share rests when possible? I mean
without using \partcombine. I’d like to focus on multi-measure rests
first. Roughly, I guess there should be something that
Dan,
Am 22. August 2015 05:19:43 MESZ, schrieb Dan Eble d...@faithful.be:
Can anyone offer general architectural advice for adding the option for
parts on the same staff to share rests when possible? I mean without
using \partcombine. I’d like to focus on multi-measure rests first.
Reviewers: ,
Message:
Please review. This patch allows whiteout-box to take a number
argument. A boolean argument is still possible as well. This brings it
into parity with whiteout for both grobs and markups. This is a
preliminary step needed for the further changes described in issue 4504.
On 22/08/15 04:44, Masamichi HOSODA wrote:
If you use Debian or Ubuntu etc., please install
`fonts-texgyre' package like following command before
compiling LilyPond.
$ sudo apt-get install fonts-texgyre
Didn’t work in LilyDev 3:
What worked for me was this:
1. Edit
hi,
this patch fixes the issue. fontforge is now detected and configure
script finishes without issue.
thanks.
Dne 22.8.2015 v 14:25 Masamichi HOSODA napsal(a):
i attempted to install lilypond- gentoo ebuild but it fails because it
does not detect fontforge version correctly:
#
