Re: Lose the tagline (permanently)

Am 28.02.2016 um 03:56 schrieb Andrew Bernard: But I would prefer if it behaved as the other header variables do, off by default, and can be turned on and modified at will. Keep the function, but make the default off. How about setting tagline to ##t prints the default text?

make test fails → texi2html (?) error

Hi list, I tried to compile the regression tests (make test) but this failed with the following message in input/regression/collated-files.texilog.log: Undefined subroutine ::get_index called at /home/malte/lilypond/Documentation/lilypond-texi2html.init line 2408. What’s this? I found the

Re: make test fails → texi2html (?) error

Am 06.10.2017 um 17:20 schrieb Federico Bruni: Il giorno ven 6 ott 2017 alle 16:27, Malte Meyn <lilyp...@maltemeyn.de> ha scritto: What’s this? I found the same message in the list archive (https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00084.html) but I couldn’t find any

issue tracker write access

Hello list, too long I have waited but now I would like to start contributing to LilyPond. Currently I’m going through the “quick start” of the CG; could you please give me (maltem on SourceForge) write access to the issue tracker? Cheers, Malte

Re: issue tracker write access

Thanks, as you can see I just submitted my first patch. I hope I did everything correctly? Am 04.10.2017 um 10:47 schrieb Phil Holmes: Done. -- Phil Holmes - Original Message - From: "Malte Meyn" <lilyp...@maltemeyn.de> To: <lilypond-devel@gnu.org> Sent: Wedne

Fwd: \tempo feature requests

Weitergeleitete Nachricht Betreff: \tempo feature requests Datum: Mon, 9 Oct 2017 11:44:44 +0200 Von: Malte Meyn <lilyp...@maltemeyn.de> An: bug-lilypond <bug-lilyp...@gnu.org> Hi list, could the snippets http://lsr.di.unimi.it/LSR/Item?id=1008 and http://lsr.di.unimi.it/LSR/Item?id=574

Re: PATCHES - Countdown for October 14th

Am 14.10.2017 um 12:56 schrieb James Lowe: Hello, Here is the current patch countdown list. The next countdown will be on October 17th. […] Push: […] 5211 Merge_rests_engraver: fix vertical rest positions - Malte Meyn https://sourceforge.net/p/testlilyissues/issues/5211 http

Re: make test-baseline / make check problem

Am 19.10.2017 um 14:59 schrieb Knut Petersen: Hi everybody! I constantly hit the problem that the files  * build/out/test-results/input/regression/out-test-baseline/merge-rests-engraver.png  * build/out/test-results/input/regression/out-test/merge-rests-engraver.png are different (a

Re: Release schedule for 2.20

Am 09.05.2018 um 11:16 schrieb David Kastrup: Aaron Hill writes: Hi folks, It would seem the release of version 2.20 must be nearing, but I have not found anything published about the release schedule for the project. There isn't one. [CC-ing to

Re: Release schedule for 2.20

Am 09.05.2018 um 11:49 schrieb Malte Meyn: Don’t get me wrong: We can be very happy to have such a committed project leader. But maybe also the other developers should join forces to 1. find out what blocks the release of 2.20.0 2. concentrate on that instead of new features. Personally, I

How to propose patches for stable branch?

Hi list, I fixed issue 4807 (https://sourceforge.net/p/testlilyissues/issues/4807/) which was a regression. It’s now in master branch and tagged Fixed_2_21_0. How will this become part of the stable branch? Will someone (David?) just scan the master branch for changes that are cherry-picked

Re: PATCHES - Countdown for January 10th

Am 10.01.2018 um 18:33 schrieb James Lowe: Hello Here is the current patch countdown list. The next countdown will be on January 13th. […] Push: 5247 add dynamic n for “niente” to feta - Malte Meyn https://sourceforge.net/p/testlilyissues/issues/5247 http://codereview.appspot.com/339090043

Re: PATCHES - Countdown for January 7th

/338320043 Countdown: 5247 add dynamic n for “niente” to feta - Malte Meyn https://sourceforge.net/p/testlilyissues/issues/5247 http://codereview.appspot.com/339090043 Review: 3208 Wrong MultiMeasureRest glyph - Malte Meyn https://sourceforge.net/p/testlilyissues/issues/3208 http

LN_SRC_TO_BUILD not found

Hi list, I’d like to build changes.pdf following the instructions from CG 4.6.2 (subsection “Building a single document”) but it fails with the error message “LN_SRC_TO_BUILD@: Command not found”. Complete output (after make-ing the binary and cd-ing to build/Documentation): $ make out=www

Re: LN_SRC_TO_BUILD not found

Am 22.02.2018 um 11:56 schrieb Malte Meyn: Hi list, I’d like to build changes.pdf following the instructions from CG 4.6.2 (subsection “Building a single document”) but it fails with the error message “LN_SRC_TO_BUILD@: Command not found”. Complete output (after make-ing the binary and cd

vertical position of Rests and MMRs

Hi list, I need some advice on how to deal with breve and longer rests. While I tried to fix issue 3208 (correct choice of rest glyphs for MMRs) I also “fixed” vertical position of the rest glyphs for shorter rests, ia. e. I made the behaviour of Rests and MultiMeasureRests more consistent.

Re: Build error. MergeFonts: Can't find font: feta11.pfb

Am 11.03.2018 um 01:01 schrieb Lucas Werkmeister: Hi everyone, I’m getting the following error message when trying to build LilyPond from git (specifically, building the AUR lilypond-git package). […] The requested file, feta11.pfb, does not exist I have a similar problem after

Re: Build error. MergeFonts: Can't find font: feta11.pfb

Am 17.03.2018 um 20:01 schrieb Lucas Werkmeister: Can confirm, coredumpctl shows loads of t1asm core dumps (no idea why there’s no error message in the terminal), and downgrading to t1utils 1.39 fixed the problem (1.40 seems buggy as well). Thanks for the info! I’m back from Lisbon and can

Re: 1/8 and 1/16 feta flags too wide?

Am 23.02.2018 um 20:34 schrieb Torsten Hämmerle: But for the sake of consistency and homogeneity, we (i.e. Malte) should remove these two relics now we have issue #5277. Will do. ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: PATCHES - Countdown for Nov 2nd

Am 02.11.18 um 23:38 schrieb Dan Eble: On Nov 2, 2018, at 10:44, James Lowe wrote: A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Somehow, https://codereview.appspot.com/353790043/

Re: makelsr

Am 29.12.18 um 18:21 schrieb Phil Holmes: - Original Message - From: "Malte Meyn" To: Sent: Saturday, December 29, 2018 9:29 AM Subject: Re: makelsr Am 28.12.18 um 21:33 schrieb Phil Holmes: A little late to the party, but I am almost certain that running makelsr

Re: makelsr

Am 28.12.18 um 21:33 schrieb Phil Holmes: A little late to the party, but I am almost certain that running makelsr to create an LSR patch and then (after testing with at least make, make doc) and pushing that patch, and then putting up the doc patch for review is a perfectly accestable way

Re: LSR snippet for docs

Am 26.12.18 um 11:51 schrieb pkx1...@runbox.com: Yes but I would add the snippet first to the NR as a patch (i.e. via ../snippets/new/..) and put it through review that way; then worry about the LSR 'website' later as the LSR is not independent the doc build process. I already added the

LSR snippet for docs

Hi list, for documentation of restNumberThreshold (https://sourceforge.net/p/testlilyissues/issues/5251/) I made a snippet (http://lsr.di.unimi.it/LSR/Item?id=1078) that I would like to add to the NR. IIUC, the snippet now needs to be reviewed and then I can add it to git and upload a patch

git-cl: "Update attempt returns error code 404"

Hi list, I just uploaded a patch for issue 2575 and got the following git-cl messages: […] Issue created. URL: http://codereview.appspot.com/341520043 Uploading base file for input/regression/ambitus-middleC.ly Uploading base file for lily/ambitus-engraver.cc This has been identified with

linker error: DSO missing from command line

Hi list, in a clean repository (in a branch based on current origin/master) I did the following: $ ./autogen.sh $ mkdir build $ cd build $ ../configure $ make -j5 CPU_COUNT=5 I got the following output before the compilation ended without success, what’s wrong there? Cheers, Malte g++ -o

Re: makelsr

Am 28.12.18 um 13:13 schrieb Thomas Morley: James askes not to run makelsr, because a plethora of changes will clutter the patch-set. OTOH, a patch can't stand alone and can't be applied for testings by reviewers without makelsr. So I voted for doing makelsr. The CG is not clear in this

Re: linker error: DSO missing from command line

Am 08.01.19 um 10:47 schrieb James Lowe: Hello Malte On 08/01/2019 8:22 am, Malte Meyn wrote: Hi list, in a clean repository (in a branch based on current origin/master) I did the following: $ ./autogen.sh not ./autogen.sh --noconfigure? (I don't know what this does but it is what I

Re: Non-quadratic form of whiteout

Am 16.09.18 um 16:18 schrieb Thomas Morley: The disadvantage of this approach is obvious as soon as thickness is increased. That’s true but the function stencil-whiteout-outline (from scm/stencil.scm) takes not only a thickness argument but also three other arguments called color,

Re: Non-quadratic form of whiteout

Am 16.09.18 um 18:17 schrieb David Kastrup: Kieren MacMillan writes: Hi Urs, Am I getting something wrong here: why are you asking about intermediate points? Aren't we only interested in the whiteout around the outer edges? Consider the letter O, with 'outline #'(5 . 0). It’s easy to

Re: Non-quadratic form of whiteout

Am 16.09.18 um 15:16 schrieb Kieren MacMillan: 3. at any other point on the grob, the whiteout should extend [horizontally and vertically] by an interpolated amount. How to interpolate? Maybe in such a way that a point or circle gets an elliptical whiteout?

R\fermata: How to build a markup in C++?

lt; R\fermataMarkup \\ R\fermataMarkup >> \bar "||" R1\fermata R1^\fermata R1_\fermata << R\fermata \\ R\fermata >> \bar "||" R\shortfermata R\upbow R\lheel } From 7392872dacc5f483792d3f41c2049567b4754d7c Mon Sep 17 00:00:00

R\fermata: How to build a markup in C++?

lt; R\fermataMarkup \\ R\fermataMarkup >> \bar "||" R1\fermata R1^\fermata R1_\fermata << R\fermata \\ R\fermata >> \bar "||" R\shortfermata R\upbow R\lheel } From 7392872dacc5f483792d3f41c2049567b4754d7c Mon Sep 17 00:00:00

Re: R\fermata: How to build a markup in C++?

Am 16.04.19 um 13:38 schrieb Neil Puttock: Yeah. You should be able to check for an articulation-event and extract the type to build the markup. Yes. The only thing that I’m not sure is how to get hold of the context that has the scriptDefinitions property. My current approach just uses

Re: R\fermata: How to build a markup in C++?

Am 16.04.19 um 13:21 schrieb Neil Puttock: Hi Malte, On Mon, 15 Apr 2019 at 10:55, Malte Meyn wrote: Are there any other ideas how the R\fermata thing could be done? Check out scm/lily-syntax-constructors.scm, where there's a constructor for MM rests: http://git.savannah.gnu.org/gitweb

Re: R\fermata: How to build a markup in C++?

Am 16.04.19 um 14:50 schrieb Malte Meyn: Am 16.04.19 um 13:38 schrieb Neil Puttock: Yeah.  You should be able to check for an articulation-event and extract the type to build the markup. Yes. The only thing that I’m not sure is how to get hold of the context that has

Re: Undocumented "ambitusAfter"

Am 10.05.19 um 22:42 schrieb Thomas Morley: Malte, do you've time to add a doc-string? I didn’t realize that the doc-string is used for documentation generation also for music functions. Thanks for the hint! I’ll upload a patch that adds a doc-string, mentiones \ambitusAfter in

R\fermata: How to update translated docs

Hi list, my third attempt to make R\fermata work (after https://lists.gnu.org/archive/html/lilypond-devel/2019-04/msg00069.html and https://lists.gnu.org/archive/html/lilypond-devel/2019-04/msg00079.html) seems to be successful: https://sourceforge.net/p/testlilyissues/issues/5511/ One of

Re: R\fermata: How to build a markup in C++?

Am 19.04.19 um 19:50 schrieb Dan Eble: On Apr 16, 2019, at 06:58, Malte Meyn wrote: In all these cases \fermata behaves the same as \fermataMarkup, because both simply create a MultiMeasureRestText. It’s placed on the first measure of expanded MMRs Is that the most reasonable result

Re: R\fermata: How to build a markup in C++?

Am 16.04.19 um 00:24 schrieb Dan Eble: On Apr 15, 2019, at 05:55, Malte Meyn wrote: Attached you can find what I’ve tried as a patch file, below some LilyPond code for testing. It would be valuable to consider more cases. * multi-measure rests that actually span multiple measures

ottava signs

Hi list, inspired by a discussion on notat.io [1] I started to make some improvements to ottava signs, the first one about the texts [2], the second one about dashed right edges [3] and a third one about vertical alignment. IMO the criticism on LilyPond’s default 8va markup [4] is

git-cl upload and existing sf issues

Hi list, when uploading a first patch set, git-cl asks for a sourceforge issue number. If a new issue is created, everything is fine but when you choose an existing issue, there is some 404 error and the Rietveld link is not added to the sf issue—resulting in a missing Rietveld link on

Re: ottava signs

Am 01.10.19 um 23:13 schrieb Joram: 1. ottava for arbitrary octavations (>2) This currently produces broken output: { \ottava #3 a } The warning in your patch¹ addresses that and the patch extends the default range up to ± 4 which seems enough (I am not sure how far the …ma naming works

Re: ottava signs

Am 02.10.19 um 11:27 schrieb Joram: 2. nice line spanners (top- or bottom-aligned, dotted etc.) That’s what Gould recommends, yes. But I’m not sure how to implement this: One could a) use a single number/direction for “alta” ottavations and mirror it for “bassa” → somehow inflexible and if

Re: ottava signs

Am 02.10.19 um 08:45 schrieb Malte Meyn: However, the reasoning in the SMuFL 1.3 specifications ("Implementation notes") about "ma" vs. "mb" convinced me that 15mb does not make sense and I’d suggest to use 15ma etc. as default setting. Hm … Gould recom

define-public vs. define-safe-public

Hi list, is there a clear policy which functions are defined public or safe-public? Asking for https://sourceforge.net/p/testlilyissues/issues/5517/ If I understand correctly what define-safe-public does I don’t understand why some things at the beginning of lily-library.scm are public and

Re: ottava signs

Am 29.09.19 um 10:28 schrieb Malte Meyn: and a third one about vertical alignment. I’m not sure how a easily changeable vertical alignment should be done best: The easiest solution I found would be to remove the line text.align_to (Y_AXIS, CENTER); from ottava-bracket.cc (line 179

Re: ottava signs

Hi foxfanfare, Am 29.09.19 um 18:43 schrieb foxfanfare: For those interested, here's my current tweak for the ottava brackets: […] ottava.ly ottava.pdf Hopefully, all of

MacOS 64bit installer

Hi list, my university asked me if I could give a LilyPond basics workshop for students and lecturers. There are some interested people who use Macbooks with the newest OS on which LilyPond wouldn’t work anymore IIUC. Of course I would like to give such a workshop but I would need to know

Re: Cannot build changes.pdf anymore

Am 23.11.19 um 12:23 schrieb Malte Meyn: Hi list, I used to build the changes document like this: $ cd ~/lilypond/build/Documentation/ && touch ../../Documentation/changes.tely && time make -j5 CPU_COUNT=5 out=www out-www/changes.pdf This doesn’t work anymore for me, ev

Cannot build changes.pdf anymore

Hi list, I used to build the changes document like this: $ cd ~/lilypond/build/Documentation/ && touch ../../Documentation/changes.tely && time make -j5 CPU_COUNT=5 out=www out-www/changes.pdf This doesn’t work anymore for me, even after a fresh $ cd ~/lilypond $ rm -rf build $

Re: Cannot build changes.pdf anymore

Am 23.11.19 um 13:59 schrieb Jonas Hahnfeld: Am Samstag, den 23.11.2019, 12:23 +0100 schrieb Malte Meyn: $ cd ~/lilypond/build/Documentation/ && touch ../../Documentation/changes.tely && time make -j5 CPU_COUNT=5 out=www out-www/changes.pdf is there a reason you're

Re: What is holding up 2.20 release?

Am 17.12.19 um 19:58 schrieb Jonas Hahnfeld: 3300acdd8d Issue 5532/1: \ottava doesn’t confuse ambitus 04a0052411 Issue 5532/2: add regtest I think this is a fix for a1bde20430 Issue 2575/1: Ambitus respects staffLineLayoutFunction not yet in stable/2.20? Not really. It fixes a bug I

Re: What is holding up 2.20 release?

Am 16.11.19 um 21:52 schrieb David Kastrup: But the current roadblock is David K. cherry-picking some patches. Here is a remaining list (not completely up to date with current master, though not missing much) to check for possible inclusion (assuming I have not overlooked something important

Re: ottava signs

need only changes in scm/ly files: https://codereview.appspot.com/568970043 (there is one little change in a C++ file too but you won’t need that if you don’t use ottava at the beginning of a piece *and* Ambitus_engraver). Malte Meyn-3 wrote Any thoughts from your side on how to do vertical

Re: PATCHES - Countdown for December 10th

Am 10.12.19 um 07:41 schrieb Werner LEMBERG: Is there a specific reason that issue #5621 is not on this list? Werner If there exists a patchset on Rietveld, neither is it linked to on Sourceforge nor is 5621 set to Patch:new.

Re: french beaming incorrectly makes stems longer

Am 25.01.20 um 08:12 schrieb Werner LEMBERG: Before adding it to the bug tracker I want to check this group's knowledge whether there is a reason that French beams are longer than normal: \relative c'' { r16 f d f \override Stem.french-beaming = ##t r16 f d f } Looking

[Notensatz im 21. Jahrhundert] documentation for those who cannot attend?

Hi list, after reading the recent threads about the upcoming conference I had another look at the updated programme and saw that so many of you will be there and the LilyPond dev meeting on Sunday will have a very interesting agenda. I would love to come and meet you in person after all the

move some OLL functions to vanilla LilyPond? [was: A suggestion: add \rf to built-in dynamics]

Am 04.01.20 um 12:29 schrieb Malte Meyn: But that brings me to another question: Shouldn’t we add the \dynamic command from openlilylib to vanilla LilyPond? This would allow users to have “p dolce”, “più f” and ‘exotic’ dynamics like “mfz” whithout having to define extra commands using make

Re: A suggestion: add \rf to built-in dynamics

Am 04.01.20 um 11:04 schrieb Peter Toye: I suggest that \rf (for rinforzando) be added to the built-in dynamic list. I suggested this on the users list, and got two replies, one fairly positive, one negative. My rationale is that it's accepted as a synonym of rfz, and was used as such by

Re: A suggestion: add \rf to built-in dynamics

Am 05.01.20 um 18:11 schrieb Wols Lists: Anyways, I'll give you a little tip, and attach my "dynamics.ily" file. All my custom dynamics live in here, and I include it in any work that might need them. I'm *guessing* that it's very similar to the standard definitions that exist in lilypond,

Re: AU-1.2 Relocation

Am 25.03.20 um 17:19 schrieb Jean-Charles Malahieude: Hi Werner, On my way to updating the French documentation, I read in running.itely (1st item of  Relocation algorithm) "Compute the directory where the currently executed @command{lilypond} binary is located.  Let's call this

Re: An exciting new release… of Sibelius!!!

Am 27.03.20 um 15:08 schrieb Valentin Villenave: Hi everybody, I know it’s off-topic but I wanted to share the news because, let’s be honest, nobody in their right mind would want to miss it: Yes! It’s finally here! The latest and brightest version of Sibelius is out… *And* it offers one

Re: ottava signs

Am 18.03.20 um 14:55 schrieb foxfanfare: Malte Meyn-3 wrote Yes, that would be \set Staff.ottavationMarkups = #ottava-ordinals Digging up an old topic but I wonder where we currently stand about ottava signs? I recently updated to version 2.20.0 but I wasnt able to find anything

make builds everything

Hi list, first of all, I’d like thank those who made the make output less verbose, this makes errors much easier to find. Is there a reason for building every .o file every time a single .cc file is changed? It’s very time-consuming when you want to test little changes … make[1]: Entering

Re: make builds everything

Am 21.03.20 um 19:19 schrieb Han-Wen Nienhuys: On Sat, Mar 21, 2020 at 6:12 PM Malte Meyn wrote: Hi list, first of all, I’d like thank those who made the make output less verbose, this makes errors much easier to find. Is there a reason for building every .o file every time a single .cc

Re: make builds everything

Am 21.03.20 um 20:54 schrieb David Kastrup: Malte Meyn writes: Am 21.03.20 um 19:19 schrieb Han-Wen Nienhuys: On Sat, Mar 21, 2020 at 6:12 PM Malte Meyn wrote: Hi list, first of all, I’d like thank those who made the make output less verbose, this makes errors much easier to find

resuming contribution at gitlab

Hi list, after drowning my laptop in April and not having time to contribute since then I’m back again. I’d like to finish my work on issue 5611 but I’ve missed the move to gitlab and the nearing 2.22. IIUC, I should 1. request and wait for commit access 2. then push my work to a branch