*Much* better to read and understand, thanks! LGTM now.
https://codereview.appspot.com/566080043/
> > I don't fully understand this code.
>
> that is an ominous comment to come from the Freetype
> author. I had assumed you reviewed the existing code
> as well.
I have two difficulties: I'm not good at C++ and Guile stuff, and it's
not completely clear to me what the code wants to achieve. I
LGTM. This issue also adds some scheme code and a conversion rule –
they are different commits, right?
https://codereview.appspot.com/560030044/diff/557800043/scm/define-context-properties.scm
File scm/define-context-properties.scm (right):
https://codereview.appspot.com/560030044/diff/55780004
I don't fully understand this code. Please add more comments.
A quite well documented routine to walk over a contour is function
`FT_Outline_Decompose` in file `src/base/ftoutln.c` of the FreeType
source code.
https://codereview.appspot.com/566080043/diff/560030043/lily/freetype.cc
File lily/f
LGTM, with minor nits.
https://codereview.appspot.com/561810045/diff/551840043/scm/backend-library.scm
File scm/backend-library.scm (right):
https://codereview.appspot.com/561810045/diff/551840043/scm/backend-library.scm#newcode143
scm/backend-library.scm:143: ;; When the directory already exist
[forgot to send it previously]
https://codereview.appspot.com/569700043/diff/582060043/lily/freetype.cc
File lily/freetype.cc (right):
https://codereview.appspot.com/569700043/diff/582060043/lily/freetype.cc#newcode126
lily/freetype.cc:126: else if (outline->tags[j] & 1)
On 2020/05/08 08:15:58,
https://codereview.appspot.com/569700043/diff/573820043/lily/freetype.cc
File lily/freetype.cc (right):
https://codereview.appspot.com/569700043/diff/573820043/lily/freetype.cc#newcode129
lily/freetype.cc:129: else if (ctags[j] & 1)
1 → FT_CURVE_TAG_ON
https://codereview.appspot.com/569700043/d
LGTM
https://codereview.appspot.com/554030043/diff/582040043/input/regression/cross-staff-stem-offset.ly
File input/regression/cross-staff-stem-offset.ly (right):
https://codereview.appspot.com/554030043/diff/582040043/input/regression/cross-staff-stem-offset.ly#newcode5
input/regression/cross-s
LGTM
https://codereview.appspot.com/561790043/
Thanks for the changes. Here the next round of comments :-)
https://codereview.appspot.com/548080043/diff/567530058/lily/open-type-font-scheme.cc
File lily/open-type-font-scheme.cc (right):
https://codereview.appspot.com/548080043/diff/567530058/lily/open-type-font-scheme.cc#newcode467
lily/ope
LGTM, with some nits
https://codereview.appspot.com/548080043/diff/573790043/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.com/548080043/diff/573790043/Documentation/usage/running.itely#newcode663
Documentation/usage/running.itely:66
LGTM
https://codereview.appspot.com/559960060/
LGTM
https://codereview.appspot.com/569700043/
LGTM.
The figured bass stuff is a separate commit, I guess...
https://codereview.appspot.com/553980043/
LGTM, thanks! Looks very good, indeed.
https://codereview.appspot.com/548030043/
LGTM, thanks!
https://codereview.appspot.com/559930043/diff/549940043/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
https://codereview.appspot.com/559930043/diff/549940043/Documentation/notation/rhythms.itely#newcode275
Documentation/notation/rhythms.ite
LGTM
https://codereview.appspot.com/582010043/
Very nice, thanks!
There are some grammar glitches in the documentation – I hope that a
native English speaker can improve that.
https://codereview.appspot.com/577900043/diff/577910043/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.c
LGTM
https://codereview.appspot.com/577840053/
LGTM
https://codereview.appspot.com/561680043/
LGTM, thanks a lot!
https://codereview.appspot.com/551830043/diff/573740043/po/GNUmakefile
File po/GNUmakefile (right):
https://codereview.appspot.com/551830043/diff/573740043/po/GNUmakefile#newcode14
po/GNUmakefile:14: sed-makestuff = -e 's/[a-zA-Z_/]*make\[[0-9]*\].*//'
shouldn't this be rathe
LGTM
https://codereview.appspot.com/567480043/
LGTM
https://codereview.appspot.com/565960043/
LGTM
https://codereview.appspot.com/551820043/
LGTM
https://codereview.appspot.com/573730043/
LGTM
https://codereview.appspot.com/557720043/diff/581940043/Documentation/GNUmakefile
File Documentation/GNUmakefile (right):
https://codereview.appspot.com/557720043/diff/581940043/Documentation/GNUmakefile#newcode304
Documentation/GNUmakefile:304: $(outdir)/contributor.texi:
$(outdir)/ly-gram
LGTM
https://codereview.appspot.com/555700043/
LGTM
https://codereview.appspot.com/549920043/
Nice! I don't really understand the C++ wizardry, but having to type
less macros in the normal code is certainly beneficial.
https://codereview.appspot.com/551780043/
LGTM
https://codereview.appspot.com/563870043/
> I agree with the sentiment, but I fail to come up
> with a naming choice that does not make the cure
> worse than the problem.
I would simply use GET_LISTENERX (or GET_LISTENER1) for the longer call.
https://codereview.appspot.com/549890043/
LGTM
https://codereview.appspot.com/567450043/diff/555680043/lily/performance-scheme.cc
File lily/performance-scheme.cc (left):
https://codereview.appspot.com/567450043/diff/555680043/lily/performance-scheme.cc#oldcode31
lily/performance-scheme.cc:31: LY_DEFINE (ly_performance_set_header_x,
"ly:
LGTM - but I don't know the internals well enough to really decide that.
What about using two macros instead of one? The first would take a
context as a first argument (as it does now), the second one uses 'this'
in the macro body, omitting that as a macro argument. The former seems
to be a rare
LGTM
https://codereview.appspot.com/559870043/diff/553910043/lily/include/box.hh
File lily/include/box.hh (right):
https://codereview.appspot.com/559870043/diff/553910043/lily/include/box.hh#newcode38
lily/include/box.hh:38: /// smallest box enclosing `this` and `b`
Why '///' instead of '//'?
h
LGTM
https://codereview.appspot.com/565920043/
LGTM
https://codereview.appspot.com/579590044/
LGTM
https://codereview.appspot.com/581910043/
LGTM, with some nits.
https://codereview.appspot.com/545870043/diff/549860043/make/doc-i18n-root-rules.make
File make/doc-i18n-root-rules.make (right):
https://codereview.appspot.com/545870043/diff/549860043/make/doc-i18n-root-rules.make#newcode10
make/doc-i18n-root-rules.make:10: find $(outdir)
>From visual inspection, LGTM.
I only wonder whether we should use
if
{
foo(...);
}
or
if
foo(...);
for single statements – right now, the source code contains both
variants...
https://codereview.appspot.com/561640043/
some nits
https://codereview.appspot.com/557670043/diff/569610043/input/regression/system-start-brace-style.ly
File input/regression/system-start-brace-style.ly (right):
https://codereview.appspot.com/557670043/diff/569610043/input/regression/system-start-brace-style.ly#newcode4
input/regression
LGTM
https://codereview.appspot.com/583750044/
LGTM. Maybe you can add a comment w.r.t. speed improvement.
https://codereview.appspot.com/551690046/
Maybe this can be short-tracked to quickly get rid of the faulty
webpage?
https://codereview.appspot.com/581880043/
LGTM (without testing)
https://codereview.appspot.com/549840043/
LGTM
https://codereview.appspot.com/545860043/
LGTM, thanks.
BTW, it's 'clean up' if you use it as a verb'.
https://codereview.appspot.com/547890043/
> I'd rather not have 2.21.0 in a state inconsistent
> with its makelsr program. So if I were to push,
> I'd need to push the results of a new makelsr run
> as well.
OK, I misunderstood.
https://codereview.appspot.com/549820043/
LGTM, and please push directly.
https://codereview.appspot.com/549820043/
LGTM, thanks!
https://codereview.appspot.com/571950043/diff/545810043/input/regression/auto-beam-exceptions.ly
File input/regression/auto-beam-exceptions.ly (right):
https://codereview.appspot.com/571950043/diff/545810043/input/regression/auto-beam-exceptions.ly#newcode7
input/regression/auto-be
Nice idea, thanks. Some nits and questions.
https://codereview.appspot.com/557640051/diff/571940043/Documentation/notation/text.itely
File Documentation/notation/text.itely (right):
https://codereview.appspot.com/557640051/diff/571940043/Documentation/notation/text.itely#newcode1552
Documentati
Minor doc nits.
https://codereview.appspot.com/575330043/diff/549780043/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/575330043/diff/549780043/Documentation/changes.tely#newcode67
Documentation/changes.tely:67: @item The labels can be changed
https://codereview.appspot.com/553580043/diff/571810043/mf/gen-emmentaler-brace.fontforge.py
File mf/gen-emmentaler-brace.fontforge.py (right):
https://codereview.appspot.com/553580043/diff/571810043/mf/gen-emmentaler-brace.fontforge.py#newcode40
mf/gen-emmentaler-brace.fontforge.py:40: # mergeF
LGTM
https://codereview.appspot.com/553760043/diff/565830044/Documentation/notation/staff.itely
File Documentation/notation/staff.itely (right):
https://codereview.appspot.com/553760043/diff/565830044/Documentation/notation/staff.itely#newcode801
Documentation/notation/staff.itely:801: rests, sk
LGTM
https://codereview.appspot.com/577710043/
> > What's the reason this isn't called `LOADLIBS`?
>
> you should ask the GNU project.
Aah, indeed, thanks. Well, `LOADLIBES` is deprecated, and the new name
is `LDLIBS`. So maybe use `LDLIBS`?
https://codereview.appspot.com/577690043/
LGTM
https://codereview.appspot.com/559700043/diff/545760043/input/regression/beaming-more-than-4-beams-normal-size.ly
File input/regression/beaming-more-than-4-beams-normal-size.ly (right):
https://codereview.appspot.com/559700043/diff/545760043/input/regression/beaming-more-than-4-beams-normal
LGTM, with nits.
https://codereview.appspot.com/577700045/diff/547810068/flower/GNUmakefile
File flower/GNUmakefile (right):
https://codereview.appspot.com/577700045/diff/547810068/flower/GNUmakefile#newcode17
flower/GNUmakefile:17: TEST_LOADLIBES = $(LIBRARY) $(CXXABI_LIBS)
I suggest s/TEST_LOA
LGTM
https://codereview.appspot.com/547810069/diff/575870045/GNUmakefile.in
File GNUmakefile.in (right):
https://codereview.appspot.com/547810069/diff/575870045/GNUmakefile.in#newcode26
GNUmakefile.in:26: RELEASE_FILES = RELEASE-COMMIT
Many GNU packages auto-generate a ChangeLog file from the gi
LGTM
https://codereview.appspot.com/575870044/
LGTM
https://codereview.appspot.com/563780044/
LGTM
https://codereview.appspot.com/577700043/
LGTM, thanks! I have some nits here and there, though.
https://codereview.appspot.com/553750044/diff/561590043/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/553750044/diff/561590043/Documentation/changes.tely#newcode66
Documentation/changes.t
>From visual checking I'm not sure whether your changes work as
expected...
https://codereview.appspot.com/577690043/diff/581870043/lily/GNUmakefile
File lily/GNUmakefile (right):
https://codereview.appspot.com/577690043/diff/581870043/lily/GNUmakefile#newcode15
lily/GNUmakefile:15: LOADLIBES =
LGTM, and some minor nits.
https://codereview.appspot.com/575860044/diff/547790043/aclocal.m4
File aclocal.m4 (right):
https://codereview.appspot.com/575860044/diff/547790043/aclocal.m4#newcode625
aclocal.m4:625: AC_ARG_VAR(GUILE_FLAVOR, AS_HELP_STRING([],
What about breaking the line here to ge
https://codereview.appspot.com/553740043/diff/547780043/input/regression/tie-single-manual.ly
File input/regression/tie-single-manual.ly (right):
https://codereview.appspot.com/553740043/diff/547780043/input/regression/tie-single-manual.ly#newcode19
input/regression/tie-single-manual.ly:19: \ove
https://codereview.appspot.com/553700043/diff/555460043/mf/invoke-mf2pt.sh
File mf/invoke-mf2pt.sh (right):
https://codereview.appspot.com/553700043/diff/555460043/mf/invoke-mf2pt.sh#newcode18
mf/invoke-mf2pt.sh:18: # which no longer dump a .mem file
> > We could probably get rid of the .mem fil
LGTM
https://codereview.appspot.com/553700043/diff/555460043/mf/invoke-mf2pt.sh
File mf/invoke-mf2pt.sh (right):
https://codereview.appspot.com/553700043/diff/555460043/mf/invoke-mf2pt.sh#newcode18
mf/invoke-mf2pt.sh:18: # which no longer dump a .mem file
We could probably get rid of the .mem fi
LGTM
https://codereview.appspot.com/579480047/
> Are there still systems that run without bash that we care about?
I guess all BSD variants might miss bash since it is evil, evil GNU
software.
https://codereview.appspot.com/569540043/
https://codereview.appspot.com/553700043/diff/545710043/mf/invoke-mf2pt.sh
File mf/invoke-mf2pt.sh (right):
https://codereview.appspot.com/553700043/diff/545710043/mf/invoke-mf2pt.sh#newcode4
mf/invoke-mf2pt.sh:4: mf2pt1=$(realpath $1)
Second try. According to
https://unix.stackexchange.com/
Just skimming the code: LGTM
https://codereview.appspot.com/569540043/diff/555440061/scripts/build/output-distance.py
File scripts/build/output-distance.py (right):
https://codereview.appspot.com/569540043/diff/555440061/scripts/build/output-distance.py#newcode66
scripts/build/output-distance.py
this looks like a good idea, thanks!
https://codereview.appspot.com/553700043/diff/547740044/mf/invoke-mf2pt.sh
File mf/invoke-mf2pt.sh (right):
https://codereview.appspot.com/553700043/diff/547740044/mf/invoke-mf2pt.sh#newcode4
mf/invoke-mf2pt.sh:4: mf2pt1=$(realpath $1)
I only know `realpath`
LGTM now, thanks!
https://codereview.appspot.com/565750043/diff/557620047/scm/define-music-types.scm
File scm/define-music-types.scm (right):
https://codereview.appspot.com/565750043/diff/557620047/scm/define-music-types.scm#newcode685
scm/define-music-types.scm:685: . ((description . "A transit
> configure.ac:195: save_CPPFLAGS="$CXXFLAGS"
> Took me some time to find this two-character typo :-(
> fixed in staging with commit 7fddbc0ff1
Thanks a lot!
https://codereview.appspot.com/557580043/
> Gould talks specifically about vowels, but I don't see
> any reason why it shouldn't apply to sh->ss, or even
> from vowel to closed mouth. How about
> gradual-syllable-change-event?
Mhmm, what about simply `vowel-transition-event`? IMHO it's not
necessary to invent new names.
https://coderev
Some more nits :-)
https://codereview.appspot.com/565750043/diff/557610044/Documentation/music-glossary.tely
File Documentation/music-glossary.tely (right):
https://codereview.appspot.com/565750043/diff/557610044/Documentation/music-glossary.tely#newcode415
Documentation/music-glossary.tely:415:
Looks very nice, thanks!
I must admit that I've never seen such a feature before, so I can't
really comment on the actual implementation; my nits are just to improve
the documentation.
However, I wonder why you call this transition *line* and not transition
*arrow* ...
https://codereview.appspo
Too lazy to check every file, but according to the few samples I looked
at: LGTM, thanks!
https://codereview.appspot.com/573610048/
LGTM
https://codereview.appspot.com/551580044/
Reviewers: hanwenn, hahnjo,
Message:
> > can we include this rather than copy & paste?
>
> This would require generating aclocal.m4 by aclocal as
> part of generating configure. I'm all for doing this,
> but I'd avoid doing this level of tooling changes
> before 2.21.0
Seconded.
Description:
a
LGTM
https://codereview.appspot.com/577610043/
LGTM
https://codereview.appspot.com/559600043/
Very nice, thanks! From visual inspection, LGTM, with only minor nits.
https://codereview.appspot.com/567340043/diff/565730043/scripts/build/fix-docsize.sh
File scripts/build/fix-docsize.sh (right):
https://codereview.appspot.com/567340043/diff/565730043/scripts/build/fix-docsize.sh#newcode37
s
LGTM
https://codereview.appspot.com/569490044/
LGTM
https://codereview.appspot.com/565720043/
LGTM
https://codereview.appspot.com/563650043/
LGTM
https://codereview.appspot.com/549680043/
LGTM, thanks!
https://codereview.appspot.com/571780043/
not happy with indentation yet...
https://codereview.appspot.com/571780043/diff/549620043/mf/feta-scripts.mf
File mf/feta-scripts.mf (left):
https://codereview.appspot.com/571780043/diff/549620043/mf/feta-scripts.mf#oldcode999
mf/feta-scripts.mf:999: .. z2l
> Nevertheless, I've changed the inden
> > Can we assume that FontForge's python support and is
> > always enabled? Shall we check this?
>
> the FF page doesn't say that python is optional.
It's a build option in both the old (configure) and new (cmake)
builds...
https://codereview.appspot.com/553580043/
LGTM
https://codereview.appspot.com/547690053/
LGTM; some minor nits
https://codereview.appspot.com/553580043/diff/571780045/mf/GNUmakefile
File mf/GNUmakefile (right):
https://codereview.appspot.com/553580043/diff/571780045/mf/GNUmakefile#newcode130
mf/GNUmakefile:130: $(outdir)/emmentaler-brace.otf:
emmentaler-brace.fontforge.py $(outdir)/
Very nice, thanks! LGTM.
https://codereview.appspot.com/571780043/diff/549620043/mf/feta-arrowheads.mf
File mf/feta-arrowheads.mf (right):
https://codereview.appspot.com/571780043/diff/549620043/mf/feta-arrowheads.mf#newcode58
mf/feta-arrowheads.mf:58: y5 = 0;
Please use an indentation of 8 spa
LGTM. Please feel free to ignore (most of) my remarks if you consider
such nitpicking as unnecessary :-)
https://codereview.appspot.com/563630043/diff/571770043/lily/include/page-breaking.hh
File lily/include/page-breaking.hh (right):
https://codereview.appspot.com/563630043/diff/571770043/lily
LGTM
https://codereview.appspot.com/579340043/
LGTM.
https://codereview.appspot.com/555370043/
> How about
> * beamed-stem-french-adjustment
> * french-beaming-stem-adjustment
> …?
I like the second one.
https://codereview.appspot.com/557500043/
Reviewers: hahnjo,
Message:
> Do we really want that many "no"s in the output
Currently, you get this (in one long line):
checking for guile-1.8 >= 1.8.2... checking for guile-2.2 >= 2.2.0...
checking for guile-2.0 >= 2.0.7... Package guile-2.0 was not found in
the pkg-config search path. Perh
> It sounds like actual manipulation of that property
> by the user would interfere with the implementation
> of french-beaming. So maybe just mark/sort it as an
> internal property and only regtest french-beaming as
> such?
If this is the intention, yes.
https://codereview.appspot.com/557500043
LGTM
https://codereview.appspot.com/551510043/
1 - 100 of 722 matches
Mail list logo