Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Michael Käppler
Hi Owen, Am 01.07.2020 um 01:54 schrieb Owen Lamb: Ctrl-C'ing yields the same output as before, plus a success message: *** Successfully generated feta20.pfb! *** (The file feta20.pfb does indeed exist, and can be viewed in the build/mf/out, in a temporary folder. It contains all the glyphs incl

Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Owen Lamb
All right, whatever has broken 2.21.X for me broke 2.18.0, too, so I don't think bisecting will be much of a help. However, make's output was apparently more verbose back then, so I got a little more info before and after the copyright notice this time. Some sort of "overlap" errors in Fontforge ar

Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Owen Lamb
On Tue, Jun 30, 2020 at 3:04 PM Jean Abou Samra wrote: > So git clean didn't work? At this point, unfortunately I can't help > much--my > previous message was merely a shot in the dark but I understand almost > nothing > about fonts. Also, I'll be going on vacation pretty soon, so I won't have >

Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Jean Abou Samra
Hi Owen, Le 30/06/2020 à 23:45, Owen Lamb a écrit : Apologies--I double-checked the tutorial, and it looks like I just missed a half-line of code. I put it in, and the beta looks fine now. So... disregard the beta stuff! On Tue, Jun 30, 2020 at 2:35 PM Owen Lamb >

Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Owen Lamb
Apologies--I double-checked the tutorial, and it looks like I just missed a half-line of code. I put it in, and the beta looks fine now. So... disregard the beta stuff! On Tue, Jun 30, 2020 at 2:35 PM Owen Lamb wrote: > Hi Jean, > > If Fontforge is too old, it never told me so. It generated font

Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Owen Lamb
Hi Jean, If Fontforge is too old, it never told me so. It generated font files perfectly well over the last month. Running sudo apt update didn't show any newer versions. I can't help but notice that CI failed to build some commits on Friday due to font issues, the same day that my issue first sh

Re: [RFC] Use GitLab Milestones

2020-06-30 Thread Jonas Hahnfeld
Am Montag, den 29.06.2020, 08:25 -0400 schrieb Dan Eble: > On Jun 29, 2020, at 07:49, Jonas Hahnfeld wrote: > > I got the list down to five corner cases, all involving multiple > > commits related to a single issue. > > ... > > I think it would be sufficient to have the final release that include

Re: GSoC 2020: make hangs when making fonts

2020-06-30 Thread Jean Abou Samra
Hi Owen, To begin with, glad to meet you! What an annoying problem. Here's what I could suggest: - Try 'git -xdf' to clean your repository entirely, removing any untracked or ignored files. If you're touching fonts, it may be that some build artifacts have to be removed (likewise, people often

PATCHES - Countdown for June 30th

2020-06-30 Thread James
Hello, Here is the current patch countdown list. The next countdown will be on July 2nd. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !189 Web: new italian mailing list - Federico Bruni https://gitlab.co

Re: [lilypond-book] @format environments

2020-06-30 Thread Werner LEMBERG
> @format > @exampleindent 0 > @verbatim > \relative { > a4 b c d > } > @end verbatim > @end format > > [...] > > What I do not understand here: The @verbatim environment is not > indented by default, as far as I can see. What is the reason to set > '@exampleindent 0', here? > > (And the enclo

[lilypond-book] @format environments

2020-06-30 Thread Michael Käppler
Hi everyone, (Werner in particular ;)) I'm trying to understand the usage of quoting and formatting environments that occurs when lilypond-book transforms a .tely file to .texi. The following snippet, e.g., = @lilypond[verbatim] \relative { a4 b c d } @end lilypond ==