Re: Fix #5964: MM Rests shouldn’t segfault when there’s no StaffSymbol. (issue 576090043 by v.villen...@gmail.com)

2020-05-08 Thread nine . fierce . ballads
https://codereview.appspot.com/576090043/diff/557790043/lily/multi-measure-rest.cc File lily/multi-measure-rest.cc (right): https://codereview.appspot.com/576090043/diff/557790043/lily/multi-measure-rest.cc#newcode268 lily/multi-measure-rest.cc:268: bool oneline = (!staff) ||

Re: Fix #5964: MM Rests shouldn’t segfault when there’s no StaffSymbol. (issue 576090043 by v.villen...@gmail.com)

2020-05-08 Thread nine . fierce . ballads
https://codereview.appspot.com/576090043/diff/557790043/lily/multi-measure-rest.cc File lily/multi-measure-rest.cc (right): https://codereview.appspot.com/576090043/diff/557790043/lily/multi-measure-rest.cc#newcode268 lily/multi-measure-rest.cc:268: bool oneline = (!staff) ||

Re: migrating to GitLab

2020-05-08 Thread James Lowe
On 08/05/2020 12:21, Jonas Hahnfeld wrote: Am Freitag, den 08.05.2020, 13:07 +0200 schrieb David Kastrup: Jonas Hahnfeld writes: 3) The idea is to have the "main" repository at GitLab, next to the issues and merge requests. This leads to the question what to do with Savannah because git is

Re: define-markup-command-internal -> module-define-markup-command! (issue 547920045 by d...@gnu.org)

2020-05-08 Thread dak
Reviewers: hanwenn, Message: On 2020/05/08 17:12:41, hanwenn wrote: > I don't understand how this approach could ever help byte-compiling the markup > scheme files. This still uses module-define! , so the guile2 compilation step > will be oblivious to markup functions. It makes it easier to

define-markup-command-internal -> module-define-markup-command! (issue 547920045 by d...@gnu.org)

2020-05-08 Thread hanwenn
I don't understand how this approach could ever help byte-compiling the markup scheme files. This still uses module-define! , so the guile2 compilation step will be oblivious to markup functions. https://codereview.appspot.com/547920045/

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread lemzwerg--- via Discussions on LilyPond development
[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,

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread lemzwerg--- via Discussions on LilyPond development
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

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread Han-Wen Nienhuys
On Fri, May 8, 2020 at 4:28 PM wrote: > > seems to make the assertion output comparatively useless. Wouldn't it > be better > > to do such things as > > > > else { > > assert(condition); > > ... > > } > > > > instead? > > I'm used to the following idiom from LLVM: > assert(0 && "Unknown

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread jonas . hahnfeld
On 2020/05/08 14:24:18, dak wrote: > On 2020/05/08 14:14:47, hahnjo wrote: > > > assert(false) that none of the previous cases was true? That should detect a > > breaking change in FT_Outline pretty quickly. > > else if (condition) > { ... } > else assert(false); > > seems to make the assertion

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread dak
On 2020/05/08 14:14:47, hahnjo wrote: > assert(false) that none of the previous cases was true? That should detect a > breaking change in FT_Outline pretty quickly. else if (condition) { ... } else assert(false); seems to make the assertion output comparatively useless. Wouldn't it be better

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread Han-Wen Nienhuys
On Fri, May 8, 2020 at 4:14 PM wrote: > > On 2020/05/08 14:03:23, hanwenn wrote: > > > https://codereview.appspot.com/569700043/diff/582060043/lily/freetype.cc#newcode162 > > lily/freetype.cc:162: } > > On 2020/05/08 08:15:59, hahnjo wrote: > > > This code looks very familiar. Don't we already

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread jonas . hahnfeld
On 2020/05/08 14:03:23, hanwenn wrote: > https://codereview.appspot.com/569700043/diff/582060043/lily/freetype.cc#newcode162 > lily/freetype.cc:162: } > On 2020/05/08 08:15:59, hahnjo wrote: > > This code looks very familiar. Don't we already have it in > > make_draw_bezier_boxes? > > yes. So

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread hanwenn
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#newcode105 lily/freetype.cc:105: bool is_tt = (0 == strcmp ("TrueType", FT_Get_Font_Format (face))); On 2020/05/08

Re: migrating to GitLab

2020-05-08 Thread Jonas Hahnfeld
Am Freitag, den 08.05.2020, 13:07 +0200 schrieb David Kastrup: > Jonas Hahnfeld writes: > > > 3) The idea is to have the "main" repository at GitLab, next to the > > issues and merge requests. This leads to the question what to do with > > Savannah because git is distributed anyway. I first

Re: migrating to GitLab

2020-05-08 Thread David Kastrup
Jonas Hahnfeld writes: > 3) The idea is to have the "main" repository at GitLab, next to the > issues and merge requests. This leads to the question what to do with > Savannah because git is distributed anyway. I first thought about only > pushing "important" branches and tags to GitLab (master,

Re: migrating to GitLab

2020-05-08 Thread Jonas Hahnfeld
Am Freitag, den 08.05.2020, 11:03 +0200 schrieb Valentin Villenave: > On 5/8/20, Jonas Hahnfeld wrote: > > 3) The idea is to have the "main" repository at GitLab, next to the > > issues and merge requests. > > If the two are kept in sync (if and when you enable mirroring), does > that mean some

Re: migrating to GitLab

2020-05-08 Thread Valentin Villenave
On 5/8/20, Jonas Hahnfeld wrote: > I haven't heard further objections which, for me, means we are going > with GitLab. If you don't agree, now's your final time to speak up. Thanks for tackling this! > 3) The idea is to have the "main" repository at GitLab, next to the > issues and merge

Re: migrating to GitLab

2020-05-08 Thread Jonas Hahnfeld
Am Freitag, den 08.05.2020, 10:17 +0200 schrieb Jean-Charles Malahieude: > Le 08/05/2020 à 08:57, Jonas Hahnfeld a écrit : > > I haven't heard further objections which, for me, means we are going > > with GitLab. If you don't agree, now's your final time to speak up. > > Otherwise I would like to

Re: migrating to GitLab

2020-05-08 Thread Jean-Charles Malahieude
Le 08/05/2020 à 08:57, Jonas Hahnfeld a écrit : I haven't heard further objections which, for me, means we are going with GitLab. If you don't agree, now's your final time to speak up. Otherwise I would like to tackle the migration rather soon to take advantage of the new opportunities :-) This

Re: Split glyph contours in up/down segments for skylines (issue 569700043 by hanw...@gmail.com)

2020-05-08 Thread jonas . hahnfeld
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#newcode105 lily/freetype.cc:105: bool is_tt = (0 == strcmp ("TrueType", FT_Get_Font_Format (face))); Can we have this

Re: Issue 4182: avoid checking the offset of cross-staff stems too early (issue 554030043 by barr...@gmail.com)

2020-05-08 Thread barrykp
Thank you for looking at this! Issues should be fixed. https://codereview.appspot.com/554030043/diff/582040043/input/regression/cross-staff-stem-offset.ly File input/regression/cross-staff-stem-offset.ly (right):

migrating to GitLab

2020-05-08 Thread Jonas Hahnfeld
I haven't heard further objections which, for me, means we are going with GitLab. If you don't agree, now's your final time to speak up. Otherwise I would like to tackle the migration rather soon to take advantage of the new opportunities :-) This leads me to some final considerations: 1) I'm