Re: Improve relocation debug messages. (issue 347070043 by lemzw...@googlemail.com)

On Feb 8, 2019, at 07:05, d...@gnu.org wrote: > > string > _f (char const *format, const string &s, const string &s2, const string > &s3) > { > return String_convert::form_string (gettext (format), s.c_str (), > s2.c_str (), > s3.c_str ()); > } > > anyway. F

NotoSansCJKjp-Regular cannot be loaded

Does this warning indicate something amiss in my build environment? ``` Layout output to `./1a/lily-d0aeef0b.eps'... fatal error: Font NotoSansCJKjp-Regular cannot be loaded via Ghostscript because it is an OpenType/CFF Collection (OTC) font. ``` That was from input/regression/utf-8.ly during a

Gregorian Divisiones

Is there an ancient music expert lurking who is willing to clarify a couple of things about divisiones for me? The LilyPond Notation Reference says, "A divisio . . . is a staff context symbol that is used to indicate the phrase and section structure of Gregorian music." I see that these are im

Re: NotoSansCJKjp-Regular cannot be loaded

> On Jan 2, 2021, at 14:32, Werner LEMBERG wrote: > >> Does this warning indicate something amiss in my build environment? >> >> ``` >> Layout output to `./1a/lily-d0aeef0b.eps'... >> fatal error: Font NotoSansCJKjp-Regular cannot be loaded via Ghostscript >> because it is an OpenType/CFF Co

Re: cadenza followed by a MMR is buggy

On Jan 14, 2021, at 11:38, Thomas Morley wrote: > > Hi, > > this code > { > \cadenzaOn > b2 > \bar "|" > \cadenzaOff > R1 > } > returns bad output with current master. > 2.22.0 is ok. Harm, Thanks for the report. I'll try to investigate within the next day. Regards, — Dan

Re: cadenza followed by a MMR is buggy

On Jan 14, 2021, at 11:38, Thomas Morley wrote: > > Hi, > > this code > { > \cadenzaOn > b2 > \bar "|" > \cadenzaOff > R1 > } > returns bad output with current master. > 2.22.0 is ok. Alas, all is not well with earlier versions. Consider the confusing bar numbers in the following elabora

Re: cadenza followed by a MMR is buggy

On Jan 14, 2021, at 18:33, Dan Eble wrote: > > Alas, all is not well with earlier versions. Consider the confusing bar > numbers in the following elaboration of your example. How would you resolve > it? My thoughts: Measure 1 is complete, so the first "2" is not inco

Re: cadenza followed by a MMR is buggy

On Jan 14, 2021, at 19:13, Dan Eble wrote: > > On Jan 14, 2021, at 18:33, Dan Eble wrote: >> >> Alas, all is not well with earlier versions. Consider the confusing bar >> numbers in the following elaboration of your example. How would you resolve >> it? >

Re: cadenza followed by a MMR is buggy

> On Jan 15, 2021, at 04:53, Werner LEMBERG wrote: > > >> Add issue #3640 to this discussion. Accidentals, bar numbers, and >> (now) multi-measure rests are all impacted by the fact that \bar "|" >> does not create a new measure. > > Maybe the whole thing is primarily a documentation issue

Re: cadenza followed by a MMR is buggy

On Jan 15, 2021, at 06:53, David Kastrup wrote: > > Werner LEMBERG writes: > >>> Add issue #3640 to this discussion. Accidentals, bar numbers, and >>> (now) multi-measure rests are all impacted by the fact that \bar "|" >>> does not create a new measure. >> >> Maybe the whole thing is primari

Re: cadenza followed by a MMR is buggy

On Jan 15, 2021, at 18:58, Thomas Morley wrote: > > (3) if the cadenza has inner bar-lines, we should provide a simple > method to increase BarNumbers. Not sure, if we could implement this as > an automtism… I had a similar thought, but for a method to force a measure break, with other things (

Re: cadenza followed by a MMR is buggy

On Jan 15, 2021, at 12:17, Werner LEMBERG wrote: > >> The "Unmetered music" section in the manual already discusses issues >> with bar numbers, accidentals, and autobeaming. It might be helpful >> to mention the workaround of using \partial 1024 s1024 to force a >> new measure at the end of a ca

Re: Very Simple question

> -- Original Message -- > From: "Leonid Hrabovsky" > To: t.dani...@treda.co.uk ... >> So my question to you - how soon I and other users may expect the appearance >> of exhaustive covering all kinds of notation like Stockhausen, early >> Penderecki, Lutoslawski e.a.? Some isolated momen

Parsed object should be dead

Did something change in the past couple of weeks to make "Parsed object should be dead" messages more likely? Now that I've turned from documentation back to development, they seem to be getting in my way much more than they used to. This stands out: commit d1be5ec60a058e363835bee60ece6fc61a67

Re: Scoping of Guile modules

On Feb 6, 2021, at 16:27, Jonas Hahnfeld wrote: > > lily/guile-init.cc. Should this become (lily lily), which looks odd, or or (lily core) or (lily main) but (srfi srfi-1) looks odd too and I haven't heard anyone complain. — Dan

Written-end bar line

Gould writes that "[a] thin double barline ... marks the written end of the music when this is not the end of the piece" (Behind Bars, p.240). The statement is in the context of repeated sections: D.S. al Fine, etc. I'm pretty sure that this is easy to implement. Is there any reason not to mak

Re: Written-end bar line

> On Feb 8, 2021, at 20:29, Carl Sorensen wrote: > > > On 2/8/21, 5:30 PM, "lilypond-devel on behalf of Dan Eble" > d...@faithful.be> wrote: > >Gould writes that "[a] thin double barline ... marks the written end of > the music when this is

\inStaffSegno

Is anyone here an expert on the requirements for \inStaffSegno? I'm wondering whether the current implementation is perfect insofar as there is always a double stroke through it. Gould doesn't discuss the in-staff form of segno, but she discusses the mark form and recommends doubling the accom

Re: running `make grand-replace`

On Feb 17, 2021, at 02:25, Werner LEMBERG wrote: > > We should run `make grand-replace` to update all copyright years. > Since this is a completely mechanical thing to do, I suggest to submit > the MR, wait until a build was successful, then immediately merging > and committing it, bypassing the

Re: Parts with differing volta brackets

On Dec 8, 2020, at 14:14, Martin Neubauer wrote: > > On 08/12/2020 17:03, Kieren MacMillan wrote: >> Hi Martin, >> >>> I would try moving the bar line engraver to the staff level >> >> Yes, that was my point! ;) As I understood, Dan was asking for a >> “compelling case” to have a single score

\segno is an articulation?

LilyPond currently has commands \segno, \coda, and \varcoda, which create articulations. I'm looking for encouragement and approval to repurpose \segno and \coda as section delimiters. If I don't get it, my new commands will have to be named something like \segnoSection and \codaSection. To u

Re: \segno is an articulation?

On Feb 27, 2021, at 06:44, James Lowe wrote: > > convert-ly considerations aside (and really trying not to bike-shed), would > it be simpler using this example, if we did away with /segno and instead of > re-purposing created explicit commands (e.g. /segnoSign, /segnoSection, > /segnoWhatever

Ongoing work on repeated music

Lately, I've been trying to contribute self-contained, well-tested enhancements to repeated music in bottom-up fashion. In the code review for the `\section` command, Harm expressed interest in what's still in the queue. I don't want to clutter the review with tangential discussion, so I'm pro

Re: Reducing the number of open issues

> On Mar 17, 2021, at 15:10, Jonas Hahnfeld wrote: > > Hi all, > > there are currently 1066 open issues at LilyPond's GitLab repository: > https://gitlab.com/lilypond/lilypond/-/issues > > I'd like to reduce this number: In the short term, I propose to close > issues with ~Patch::abandoned (

Fwd: LilyPond | Configure --with-flexlexer-dir does not stick (#6138)

https://gitlab.com/lilypond/lilypond/-/issues/6138#note_589638792 > Enrico Maria Crisostomo commented: > > I actually complain about this! I came here to search for this issue before > sending a PR. We're hitting this in MacPorts and we're actually patching > configure.ac ourselves. > > https:

Re: MIDI time signature

On Jun 6, 2021, at 17:32, David Kastrup wrote: > > I'd argue that if we have > > \tempo 60 > \time 6/8 > > then we should likely interpret this (regarding the MIDI playing speed) > as > > \tempo 60 = 4. > \time 6/8 Is "\tempo 60" without a note duration a typo or is it a proposal for new syn

Re: MIDI rendition of things like rall./acc./rit./fermata

On Jun 12, 2021, at 18:48, David Kastrup wrote: > > So how robust (or not) would be the following approach? Make it > possible to write in the timing track something like > > \rit 2/3 { \skip 1*2 } > > with the effect that some run-always translator keeps adjusting > tempoWholesPerMinute durin

Re: MIDI rendition of things like rall./acc./rit./fermata

On Jun 13, 2021, at 12:36, David Kastrup wrote: > (by > the way: it is patently ridiculous that it requires \articulate for > getting tomh1:32 rendered as more than one note). Yes, especially because the Notation Reference comes quite close to saying that the :N notation is equivalent to \repeat

Re: MIDI rendition of things like rall./acc./rit./fermata

On Jun 13, 2021, at 14:16, Dan Eble wrote: > > If pD:d constructed the same music as \repeat tremolo d-per-D { pd }, that > would have worked. https://gitlab.com/lilypond/lilypond/-/issues/6145 — Dan

Re: Please review Pygments lexer and style

On Jun 23, 2021, at 10:33, Jean Abou Samra wrote: > > Le 23/06/2021 à 09:58, Jean Abou Samra a écrit : >> To whet your appetite, a highlighted version of the test >> file included in the PR is attached. > > Not sure why the HTML hasn't gotten through email — on > the archives and in Dan's mailbo

Re: Please review Pygments lexer and style

On Jun 24, 2021, at 14:17, Jean Abou Samra wrote: > > Ok, I already simplified it, but it's still too complicated. Consider approaching from the other direction. If you had only italic, bold, and red to work with, how would you use them? — Dan

Re: Obsolete labels

On Jun 26, 2021, at 09:09, Jonas Hahnfeld via Discussions on LilyPond development wrote: > > Hi all, > > while colorizing the labels (let me know what you think of the first > stage!) Do you mind if I adjust the Patch labels to increase contrast? It's especially low in Patch:countdown. > ,

Capitalized text

I am working on a grob for section labels. I want to recommend that the user encode the section name in title case (Coda), but I want LilyPond to render it in all caps (CODA) by default. Is there already a grob property to enable this transformation? I've hacked in a callback that calls strin

Re: Capitalized text

> On Jun 28, 2021, at 06:03, Jean Abou Samra wrote: > >> Le 27 juin 2021 à 21:19, Dan Eble a écrit : >> >> I am working on a grob for section labels. I want to recommend that the >> user encode the section name in title case (Coda), but I want LilyPond to

Re: Capitalized text

On Jun 28, 2021, at 09:11, Jean Abou Samra wrote: > >> TH. I plan to try enabling small caps and adding the option to >> transform to *lowercase* in text-interface to avoid a larger "C" in >> "CODA". > > I'd make a forced-case property taking values 'upper, 'lower or '(). > That shoul

\tuplet in \grace

Are tuplet indications on grace notes (M.2 of the example) a feature or a mere side effect of the current implementation? I'm working on some changes that happen to make them disappear and I want to understand whether I need to debug that. \new Staff \fixed c' { \new Voice { \tuplet 3/2 4 \g

Re: \tuplet in \grace

On Jul 25, 2021, at 01:29, David Kastrup wrote: > > Dan Eble writes: > >> Are tuplet indications on grace notes (M.2 of the example) a feature >> or a mere side effect of the current implementation? ... > > Looks like "if someone writes it that way, LilyPond

lilypond-book error during test-baseline

I hit an error building test-baseline after updating master. This is what I did. rm -rf * ~/lilypond-src/autogen.sh —ci make -j7 CPU_COUNT=7 && time make -j7 CPU_COUNT=7 test-baseline I couldn't reproduce it after making test-clean and test-baseline again. The tail of the terminal o

Re: Shortcut for \repeat unfold

On Sep 25, 2021, at 06:32, Lukas-Fabian Moser wrote: > > > "\*" = > #(define-music-function (n mus) (index? ly:music?) >#{ \repeat $repeat-shorthand $n { #mus } #}) > Instead of debating a default repeat type and function, why not provide access to repetition as a music function with a cl

Re: Shortcut for \repeat unfold

On Sep 25, 2021, at 14:27, David Kastrup wrote: > > Dan Eble writes: > > How about we change \repeat ... \alternative in its structure to be > \repeat ... { \alternative ... }, namely introduce a separate music > expression for \alternative? That way neither \repeat nor \alt

Re: Shortcut for \repeat unfold

On Sep 25, 2021, at 18:55, David Kastrup wrote: > > Subject: [PATCH] Allow partial \repeat commands without \alternative > > This allows using > >\repeat \etc > > and > >\repeat \etc > > to act like partial music functions in order to make it easy to define > abbreviations. Howev

Re: Shortcut for \repeat unfold

> On Sep 24, 2021, at 19:32, Jean Abou Samra wrote: > > Other possibilities: > > - "\rep n music", not as self-telling (and I think Lukas > only calls his shortcut \rep because redefining \repeat > is not syntactically valid); > - "music * n", attractive but the difference between c1*5 >

Re: Shortcut for \repeat unfold

On Sep 28, 2021, at 20:12, Carl Sorensen wrote: > > Would >28 x { d a b fs | g d g a } > > Work with the current MR? No, the x is a suffix. 28 would be parsed as a duration (an invalid one) and x as a note name (an invalid one). — Dan

Re: Shortcut for \repeat unfold

> On Sep 24, 2021, at 19:32, Jean Abou Samra wrote: > > - "\rep n music", not as self-telling (and I think Lukas > only calls his shortcut \rep because redefining \repeat > is not syntactically valid); What about killing two birds with two stones? 1. convert-ly \times A/B into \tuplet B/A

Re: lilypond x64 and arm64 for macOS users in homebrew

On Sep 30, 2021, at 17:34, Jefferson Felix wrote: > > Therefore, I would like your opinion if we can continue with Guile 2, even > if this homebrew distribution is not an official distribution, or if you > could demonstrate, with examples, known issues in compiling sheet music > with Guile 2. Je

Grob remorse

I have created a grob. Later, perhaps in another timestep, I want to discard that grob so that it has no bearing on the final score. Is there a way to do that? Is there a good example? How late is too late, etc.? Thanks, — Dan

Re: Lyric extenders in/out of alternatives

On Oct 4, 2021, at 12:44, Lukas-Fabian Moser wrote: > >>> Of course, the ideal solution would be a possibility to tell the Lyrics >>> context that it should "take" the second alternative and make it skip the >>> first alternative automatically (and suspend the LyricExtender along the >>> way).

Re: What I needed Scheme MIDI performers for...

On Oct 6, 2021, at 20:57, David Kastrup wrote: > > I am typing some drum parts for our accordion orchestra into MIDI, and > multi-measure drum rolls become completely incoherent (or rather > completely coherent) without this. Try leaving off the performer… Nifty. — Dan

Re: What is the point of bug-lilypond?

On Oct 16, 2021, at 10:58, Jonas Hahnfeld via Discussions on LilyPond development wrote: > > in my opinion we want to > send users to the mailing list by default. I don't devote much time to handling bugs (until I'm tagged), but the reports that have come directly through the GitLab UI have be

Issue description templates

This "Description template" feature might help improve the quality of issues added directly to the tracker by users. It seems we could even use it to direct them to the mailing list first if there is any doubt as to whether an issue should be added. https://docs.gitlab.com/ee/user/project/desc

Re: Any ideas what is happening here?

On Nov 3, 2021, at 18:40, David Kastrup wrote: > > > My use case is something different entirely and it does not work as > expected. This may or may not be a relevant minimal example for my use > case (no idea) but is weird enough to suggest something's off. > > { > \repeat volta 2 > { >

Re: Any ideas what is happening here?

> On Nov 3, 2021, at 19:20, David Kastrup wrote: > > Dan Eble writes: > >> On Nov 3, 2021, at 18:40, David Kastrup wrote: >>> >>> >>> My use case is something different entirely and it does not work as >>> expected. This may or may

Re: Any ideas what is happening here?

On Nov 3, 2021, at 22:10, Dan Eble wrote: > > Using \tuplet 1/1 instead of \volta 1 causes the same problem. \tuplet: https://gitlab.com/lilypond/lilypond/-/issues/6205 \volta: https://gitlab.com/lilypond/lilypond/-/issues/6207 — Dan

Re: TimeSignature with note in denominator

On Nov 8, 2021, at 16:09, Kieren MacMillan wrote: > > So: In your opinion, would adding a new function be superior overall to > “improving” the existing \time function? The \compoundMeter command would like a word with you (and the \compound-meter markup command is standing behind it). How f

Re: Question on LilyDev3 mkosi/debian/mkosi.postinst script

On Nov 19, 2021, at 14:37, John Wheeler wrote: > I have used the .bashrc script extracted from > LilyDev3/mkosi/debian/mkosi.postinst file in the past to set up a user for > LilyPond development work and the PS1 value seemed to work. This morning I > tried to do that again on a new machine and

Bar lines in hymns

There is a type of bar line that looks the same as a section bar line but is used where a mid-measure break coincides with a line break in the text. Example: https://hymnary.org/hymn/GRH1911/6 (systems 2 and 4) Does anyone know a term for this bar line or practice? Thank you, — Dan

Re: Bar lines in hymns

On Dec 20, 2021, at 16:46, Karlin High wrote: > > On 12/19/2021 1:44 PM, Dan Eble wrote: >> Does anyone know a term for this bar line or practice? > > From a music tradition based on older American hymnals, I know this as a > "phrase bar." Thank you. Tha

Re: balloonText and DoublePercentEngraver

On Dec 22, 2021, at 01:37, Werner LEMBERG wrote: > > ``` > \once\override DoublePercentRepeat.slope = #.3 > \repeat percent 2 { e'2 e' e' e' } > ``` > > Would it be possible to make `\repeat` accept such overrides, passing > them down to the various repeat grobs? ``` { \override DoublePercent

Re: RFC: Adding syntax highlighting to the official documentation

On Dec 30, 2021, at 17:07, Jean Abou Samra wrote: > > What about the original one, I mean, the one > starting this thread? As I understand it, Dan > tried less colors because there was a lot of > blue and black was easier to read. Maybe it > will be better with some kind of green? I have the sam

Re: Make Grid take an edit id

On Jan 2, 2022, at 17:59, Valentin Petzel wrote: > > Is there a good reason why we limit the scheme handles for find_context to > finding above and only by context name (and not id)? If not I’d revise this, > as > the context id based approach would require such functionality. The answer is u

Re: Careful with Texinfo markup on GitLab

On Jan 5, 2022, at 17:42, Jean Abou Samra wrote: > > request. The typical case is @lilypond, which mentions all 25+ > members of the LilyPond group … "You can prevent users from being added to a conversation and getting notified when anyone mentions a group in which those users are members." h

Re: Stepping down from Patch Meister role

On Jan 8, 2022, at 05:06, James wrote: > > I am going to stop doing the Patch countdown at the end of this month. > Thanks for the many years of steady contribution, James. — Dan

Re: Discussion: Improved Scheme interface for finding contexts

On Jan 11, 2022, at 11:35, Jean Abou Samra wrote: > > (ly:context-find-id context) >(No direction: there cannot be two contexts with the >same ID, can there? I cannot imagine Allow me: << \new PianoStaff << \new Staff = "RH" ... \new Staff = "LH" ... >> \new PianoStaff

Re: build problems

On Jan 11, 2022, at 11:37, Werner Arnhold wrote: > > Hello, > > I tried to build the program and ended up with this message: > > Traceback (most recent call last): > File "/usr/local/software/lilypond/build/../scripts/lilypond- > book.py", line 72, in >import book_base > ModuleNotFoundErr

Re: build problems

On Jan 11, 2022, at 17:40, Dan Eble wrote: > >> >> Any hint how to proceed? Thanks in advance! > > Can you provide the (Whoops! Premature send.) Can you provide the commands one would use to reproduce the issue? — Dan

LilyPond 2.23.6

Would it be reasonable to release 2.23.6 soon? The documentation of \jump (!1134, in review) is the last of the documentation related to \repeat segno, and it would be nice to let users get their hands on the feature. — Dan

Re: Bar lines in hymns

On Dec 20, 2021, at 19:03, Dan Eble wrote: > > On Dec 20, 2021, at 16:46, Karlin High wrote: >> >> On 12/19/2021 1:44 PM, Dan Eble wrote: >>> Does anyone know a term for this bar line or practice? >> >> From a music tradition based on older American hy

Ancient repeat sign

https://www.pinterest.ca/pin/560909328587237881/ The sections of this work seem to be separated with a kind of repeat sign. A :|||: B :|||: C :||: D :|: Q. Do I understand correctly that this is performed AAA BBB CCD? Q. Is this the most obvious way to code it? { \repeat v

Re: Patch scheduling

On Feb 6, 2022, at 22:23, Colin Campbell wrote: > > For my guidance, I'd be grateful if the community would correct or amplify > the following recap of the patch handling process. > Colin, I think you summed it up well and I agree with Lukas' additions. Thanks, — Dan

Re: On reproducing failures of MR

On Feb 15, 2022, at 04:54, Paulo Matos wrote: > > So `make test` runs the regression tests to `out`, `make test-baseline` > creates a current baseline in `out-baseline` and `make check` runs the > tests and creates a comparison with baseline. :) I hope I got it. And after making a change, run `m

ASSIGN_EVENT_ONCE in Scheme

ASSIGN_EVENT_ONCE(cur, new) does this: - if cur is nullptr: assign cur = new, return true - if *cur and *new are equal: quietly return false - if *cur and *new are unequal: warn and return false Would a Scheme analog of ASSIGN_EVENT_ONCE be used like this, (let ((my-foo-event #f))

Repeat count as "ij" in Gregorian chant

Please see merge request 1235 [1] for an image of a repeat count for Gregorian chant that is generated according to \repeat in the ly code. I learned of this notation only recently and I don't expect to use it myself except as a way to test LilyPond's data flow. Is anyone here interested in sp

Re: VoltaBracketSpanner → VoltaBracketLineSpanner?

On Mar 5, 2022, at 08:04, Werner LEMBERG wrote: > > SostenutoPedal → SostenutoPedalLineSpanner > SustainPedal → SustainPedalLineSpanner > UnaCordaPedal → UnaCordaPedalLineSpanner Does "Spanner" add anything to "Line" in these cases, or is it like, "I brought down that wolf-ani

Re: Future tag names for releases

On Mar 16, 2022, at 17:04, Jean Abou Samra wrote: > > Le 16/03/2022 à 21:57, Jonas Hahnfeld via Discussions on LilyPond development > a écrit : >> >> ... >> would drop the superfluous "release/" prefix (probably still stemming >> from CVS times?) and the "-1" suffix for the buildnumber, which

Re: Should \partial accept music instead of duration?

On Mar 19, 2022, at 20:53, Aaron Hill wrote: ... >>> A convert-ly rule would probably not be possible given the limited power >>> of regular expressions. As such, \partial might need to support both >>> duration and music arguments. Initially I thought this might not be >>> possible, given that

Re: Partial version numbers in master

On Mar 22, 2022, at 07:57, Jean Abou Samra wrote: > > Hi, > > With https://gitlab.com/lilypond/lilypond/-/merge_requests/1187, > I introduced a change that I didn't notice: something like > > \version "2.23" > > is now an error. It is accepted with current released versions. > On the other han

Re: Slanted Beams thickness

On Mar 25, 2022, at 04:35, Luca Fascione wrote: > > This video shows Hans Kuehner at work > > https://www.youtube.com/watch?v=BvyoKdW-Big > > at 4m36 shows beams being engraved, he appears to keep the instrument > orthogonal to the line direction, It's fascinating, but those beams are nearly h

Re: MR tests showing raw HTML

On Mar 29, 2022, at 20:02, Colin Campbell wrote: > > When I verify the results of the test stage of CI, clicking on the link ( > https://gitlab.com/lilypond/lilypond/-/jobs/2261164728/artifacts/file/test-results/index.html > ), I get a screenful of raw HTML. Pasting that URL directly into an ad

Re: Scheme pattern for retrieving data in objects

> On Apr 2, 2022, at 07:38, Han-Wen Nienhuys wrote: > > On Fri, Apr 1, 2022 at 6:43 PM Jean Abou Samra > wrote: ... >> (fetch left-bound-info assoc-ref (common-Y X padding attach-dir) I'm not enthusiastic about multiple variable declarations in one line or variabl

Re: Translation

On Apr 2, 2022, at 10:10, Robert Ernest wrote: > > how can I help with translation, seeing as the webpage is mistranslated? > Welcome, Robert. See the Contributor's Guide, which is available in HTML or PDF at https://lilypond.org/development.html. Regards, — Dan

Re: C++ question on wrapper API for setting Guile fluids

On Apr 20, 2022, at 18:04, Jean Abou Samra wrote: > > Calls to scm_dynwind_begin () and scm_dynwind_end () must be > paired correctly. Obviously, if '...' contains statements > causing non-local control flow like return, break, continue, > and such, it is easy to miss a scm_dynwind_end (). I read

Re: C++ question on wrapper API for setting Guile fluids

On Apr 21, 2022, at 02:55, Luca Fascione wrote: > > I'd think you can up this by one, and get a cleaner looking piece of code > if you implement scm_dynwind_fluid() as a forwarded method on your context: ... > dwc.fluid (fluid2, value2); Here's something that does bother me. That reads as if d

Re: C++ question on wrapper API for setting Guile fluids

On Apr 21, 2022, at 06:54, Jean Abou Samra wrote: > > Le 21/04/2022 à 12:47, David Kastrup a écrit : >> So what one would want is a C++ wrapper working with functionals? ... > So this needs an interface that is easier to use, whether it uses > RAII or functionals or something else. Current talks

Re: C++ question on wrapper API for setting Guile fluids

On Apr 22, 2022, at 05:39, Jean Abou Samra wrote: > > You both made a good point. My conclusion is that I should stick to > > { > Local_assumption la (Lily::prebreak_estimate, SCM_BOOL_T); > ... > } > > where the constructor does everything, included scm_dynwind_begin () > and scm_d

Re: Bar lines in hymns

On Jan 16, 2022, at 15:36, Dan Eble wrote: > > I have a mind to generalize the commands for Gregorian divisiones so that > they create breathing signs, bar lines, or scripts over bar lines, according > to context properties. That will serve this case and more, and requir

Re: LSR and Documentation/snippets/new

> On May 6, 2022, at 18:46, David Kastrup wrote: > > Thomas Morley writes: > >> Please stop doing so, please first test, whether it compiles with >> current LSR-version, and please update the snippet _inside_ LSR. If >> you don't have an account please create one. Or please ask me, Pierre, >

Re: Thinking about the next stable release

On May 22, 2022, at 08:39, Jonas Hahnfeld via Discussions on LilyPond development wrote: > > So, what do people think: Would targeting a release towards the end of > this year be a reasonable thing? probably — Dan

Re: checkout releases?

On May 26, 2022, at 06:52, Thomas Morley wrote: > > Hi, > > some time ago we decided to use v2.23.7 instead of the old > release/2.23.6-1 in the repository. > > Alas I can't checkout v2.23.7: > $ git checkout v23.7 typo: missing "2." between "v" and "23" — Dan

Re: Thinking about the next stable release

On May 26, 2022, at 12:12, Jean Abou Samra wrote: > >> 1) Target a release towards the end of this year, but do not deprecate >> things in anticipation of a new major version after; instead go for a >> "regular" 2.26.0 afterwards. > > I think there's reasonable agreement that this is a > good pl

Re: Nested segno and volta repeats

On May 29, 2022, at 03:56, Jean Abou Samra wrote: > > Hi Dan, > > Is there any way to get this repeat structure with the recent > repeat additions? This is from a question on the user list. > > ||: A:|| B|| > Fine D.C. Al Fine > > -> A A B A How cruel it would have

Re: Nested segno and volta repeats

On May 29, 2022, at 10:01, Jean Abou Samra wrote: > Well, I know about \unfolded … I took it as a last resort > for tricky cases, should I not have viewed it like that? > Ideally, you'd be able to avoid repetituous code without > needing variables (if there are 10 voices, you need > 10 more variab

Re: Should we be touching goops?

On Jun 2, 2022, at 20:32, David Kastrup wrote: > > #(define-method (+ (a ) (b )) (ly:moment-add a b)) > #(define-method (- (a ) (b )) (ly:moment-sub a b)) Could we also introduce a distinction in type between points and spans of time? "Measure 12 minus Measure 8" is 4 measures, but it is not M

Re: Should we be touching goops?

On Jun 3, 2022, at 11:48, David Kastrup wrote: > > Programming languages don't offer different types for distances, > positions, weights, forces, whatnot. When I equate various amounts of Bringing the conversation back to a Moment versus the delta between two Moments, C++11 has std::chrono::tim

\bar "|.|"

Does anyone know the use case for bar type "|.|"? Is it intended as a variation of ":|.|:" without dots? I have a feeling that it should decompose at a line break as repeat bar types do. It currently appears as "|.|" at the end of a line. Thanks, — Dan

Re: Should we be touching goops?

On Jun 5, 2022, at 08:36, David Kastrup wrote: > > Right, let me refocus. > That summary is accurate. — Dan

Re: Should we be touching goops?

On Jun 5, 2022, at 08:36, David Kastrup wrote: > > While I agree with Dan that at the current point of time Moment is > definitely overloaded too much (this has historical reasons since it had > been the _only_ Scheme-accessible version of the Rational type, with > Rational being required before

Can't use direction names in (case)

This not do what I intended: ``` (case (ly:item-break-dir grob) ((LEFT) (ly:grob-property grob 'glyph-left)) ((RIGHT) (ly:grob-property grob 'glyph-right)) (else (ly:grob-property grob 'glyph ``` This does: ``` (case (ly:item-break-dir grob) ((-1) (ly:grob-property grob '

Re: I'm asking for guidance on how to start contributing to Lilypond!

On Jun 14, 2022, at 13:17, Fernando Dantas wrote: > > Hi there! > > My name is Fernando and I'm a software developer. I have a (not so large) > experience with C and C++ languages and a good experience with Python. > > I have already read most of the contributor's guide (specifically chapters >

Re: Distribution delays on mailing lists for GNU LilyPond

On Jun 17, 2022, at 02:18, Jean Abou Samra wrote: > >> we do. Does lilypond want one or more of their lists to be one of the >> initial group to move to mailman 3? > > Yes, I'd be in favor of doing that. Others, what do you > think? fine — Dan

Testing that no grob is created

I have a regression test that should fail if a BarLine grob is created. It is sufficient to override BarLine.glyph-name to make it obvious in the visual diff. Is there a simpler, more direct, or more robust way to test this? I suppose I could add an engraver that warns about each BarLine it ac

<    1   2   3   4   5   6   7   8   9   >