Re: Guidance needed in creating a branch

On Fri, Apr 19, 2024 at 7:03 PM Colin Campbell wrote: > Thanks for this, Jason! I've managed to get an MR created, and it just > passed the CI checks; now to remember what worked for the next time . . . > > Cheers, > > Colin > > On 2024-04-19 12:53, Jason Yip wrote: > > On 2024-04-19 12:51,

Re: fundamental problem with `\autoBeamOff`

On Mon, Mar 25, 2024 at 11:47 AM Werner LEMBERG wrote: > > >> Consider this small example. > >> ```tex > >> { > >> f'8 f' \autoBeamOff f' f' > >> f' f' f' f' > >> } > >> ``` > >> > >> For me it was surprising to see that `\autoBeamOff` doesn't act > >> immediately but rather two eighths

Re: unwanted randomness while generating LilyPond output

On Mon, Feb 19, 2024 at 1:28 PM Michael Käppler wrote: > > This patch will print the page stencils as pretty-printed scheme code to > stdout, while > normal messages go to stderr. > > * run `lilypond --eps input.ly > epsdebug.log` > > * send me the resulting log files > > The patch did not

Re: unwanted randomness while generating LilyPond output

On Mon, Feb 19, 2024 at 1:28 PM Michael Käppler wrote: > Hello Werner, > thanks for your reply! > > Just to make sure we're on the same page: You don't assume that there is > variability across > different runs of the same LilyPond build on the same machine? (Aka some > kind of

Re: Error with make doc

On Mon, Feb 12, 2024 at 9:22 AM Werner LEMBERG wrote: > > v2.25.13-8-gbe52228a70 > > Please test again! Theoretically, you should now get proper HTML > pages. > I can confirm that I get the proper HTML pages, compiling with -j10 on both make bytecode and make doc. It was delightful to see

Re: Error with make doc

On Sat, Feb 10, 2024 at 7:20 AM Werner LEMBERG wrote: > > >> systems like macOS that neither have or use '/bin/bash'. > > > > Apple changed the default shell for new users to zsh about 5 years > > ago, but bash is still there. I don't oppose making the build > > scripts more portable, but let's

Re: Error with make doc

On Sun, Feb 4, 2024 at 7:21 AM Werner LEMBERG wrote: > > > Please test > > https://gitlab.com/lilypond/lilypond/-/merge_requests/2254 > > It should fix all the build problems you've reported. > This merge request allowed me to build the documentation using MacOS cp and find. I still got

Re: Error with make doc

On Sat, Feb 3, 2024 at 12:01 AM Werner LEMBERG wrote: > > [Carl sent me the file listing off-list, thanks! I will analyze it in > due course.] > > > [...] and make test with a single job (to avoid race conditions that > > have given me trouble in the past): > > Interesting. When is the 'past'?

Re: Error with make doc

On Fri, Feb 2, 2024 at 4:34 AM Werner LEMBERG wrote: > >> Please read this and check whether you are affected by this > >> problem. In case you can confirm the issue please try whether it > >> works if you omit the `-l` option in all `cp` calls in my patch. > > > > I checked -- the results of

Re: Error with make doc

On Thu, Feb 1, 2024 at 10:47 AM Werner LEMBERG wrote: > > > Doing a bit of an internet search it seems this is a bug in the `cp` > implementation on macOS (as unbelievable it may be, given that `cp` is > such a fundamental command that exists since decades): > > >

Re: Error with make doc

On Wed, Jan 31, 2024 at 10:53 PM Werner LEMBERG wrote: > > > Thanks a lot, very helpful. Please apply the attached patch to the > top-level `GNUmakefile.in` file, then retry from scratch (including > the `configure` step); it should catch all of the three problems > you've encountered. > It

Re: Error with make doc

On Wed, Jan 31, 2024 at 12:49 AM Werner LEMBERG wrote: > > > I already had to install (via homebrew) gnu coreutils and gnu > > findutils, since the MacOS 'cp' and 'find' commands don't work the > > same as the respective GNU commands. > > Please give more details. What problems did you

Re: Error with make doc

Still trying to get 'make doc' to complete successfully. At this point, I think I'm through all the lilypond stuff, and now I'm stuck in shell script errors. I already had to install (via homebrew) gnu coreutils and gnu findutils, since the MacOS 'cp' and 'find' commands don't work the same as

Re: Error with texi2pdf on MacOS

On Sat, Jan 27, 2024 at 12:45 AM Werner LEMBERG wrote: > > Ouch. You have two TeX installations in your path: MacTeX (either > installed directly or via homebrew) and 'texlive-xxx' packages from > MacPorts, and the former is apparently missing XeTeX support (for > whatever reason) since the

Fwd: Error with texi2pdf on MacOS

Forwarding to list -- Forwarded message - From: Carl Sorensen Date: Fri, Jan 26, 2024 at 6:34 PM Subject: Re: Error with texi2pdf on MacOS To: Werner LEMBERG On Fri, Jan 26, 2024 at 3:28 PM Werner LEMBERG wrote: > > >> Please also check whether the two TF

Fwd: Error with texi2pdf on MacOS

Forwarding to list -- Forwarded message - From: Carl Sorensen Date: Fri, Jan 26, 2024 at 6:44 PM Subject: Re: Error with texi2pdf on MacOS To: Werner LEMBERG On Fri, Jan 26, 2024 at 3:28 PM Werner LEMBERG wrote: > > >> Please also check whether the two TF

Re: Error with texi2pdf on MacOS

On Wed, Jan 24, 2024 at 10:33 PM Werner LEMBERG wrote: > > > Another minor issue: In your e-mails, if you paste log files into the > message, there is always an empty line between every text line, which > makes them hard to read. Probably a line ending issue (i.e., mixing > LF and CR and/or

Re: Error with make doc

On Wed, Jan 24, 2024 at 11:49 PM Werner LEMBERG wrote: > > >> I installed Noto Serif JP, and added it to the fontcofig cache. > >> That got me through the previous file error. But then I got > >> stopped on another Japanese font (I suppose this might be a Linux > >> Libertine font, but my

Error with texi2pdf on MacOS

I'm trying to get a working system self-compiled on MacOS. Thanks to help from Dan, Werner, and Jean, I've been able to successfully run 'make test', although there is still a problem with Unicode characters in font file names under some circumstances. Having succeeded with 'make test', I

Re: Error with make doc

On Tue, Jan 23, 2024 at 4:54 AM Carl Sorensen wrote: > > > On Mon, Jan 22, 2024 at 8:37 PM Carl Sorensen > wrote: > >> >> >> On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra >> wrote: >> >>> Le lundi 22 janvier 2024 à 16:38 -070

Re: Error with make doc

On Mon, Jan 22, 2024 at 8:37 PM Carl Sorensen wrote: > > > On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra > wrote: > >> Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit : >> > > Looks like no error: >> > > >> > > carl@Carls

Re: Error with make doc

On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra wrote: > Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit : > > > Looks like no error: > > > > > > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond input/regression/ > pdf-copy-paste.ly > > &g

Re: Error with make doc

On Mon, Jan 22, 2024 at 4:37 PM Carl Sorensen wrote: > > > On Sun, Jan 21, 2024 at 12:33 AM Werner LEMBERG wrote: > >> >> >> You have to check the log files in `lybook-db` to find the problematic >> >> `.ly` file(s). Does `make test` succeed? You sho

Re: Error with make doc

On Mon, Jan 22, 2024 at 3:58 PM Jean Abou Samra wrote: > Le lundi 22 janvier 2024 à 21:10 +, Werner LEMBERG a écrit : > > > > > > OK, thanks. This means that there is apparently a macOS-specific > > problem with either Guile or LilyPond. For testing purposes I renamed > > one of my local

Re: Error with make doc

On Sun, Jan 21, 2024 at 12:33 AM Werner LEMBERG wrote: > > >> You have to check the log files in `lybook-db` to find the problematic > >> `.ly` file(s). Does `make test` succeed? You should actually try that > >> before running `make doc`... > >> > > > > Interesting -- the CG has make doc show

Re: Error with make doc

On Sun, Jan 21, 2024 at 11:05 PM Werner LEMBERG wrote: > > In procedure open-file: No such file or directory: > > "/System/Library/Fonts/??? W4.ttc" > > > > I checked out the /System/Library/Fonts directory, and found these fonts > > listed: > > > > ヒラギノ角ゴシック W3.ttc > > > > ヒラギノ角ゴシック

Re: Error with make doc

Thanks for the hint, Dan! I got to a new log file that gave me what I believe is a helpful error message: carl@carls-mbp-2 build % cat out/lybook-testdb/0f/lily-acefd898.log Processing `0f/lily-acefd898.ly' Parsing... Renaming input to: `/Users/carl/Development/lilypond/input/regression/

Re: Error with make doc

On Thu, Jan 18, 2024 at 11:05 PM Werner LEMBERG wrote: > > > "/Users/carl/Development/lilypond/build/out/lybook-db/ > > snippet-names-ece0c512da6daf7d9aff45809ce97556.ly"' returned non-zero > exit > > status 1. > > You have to check the log files in `lybook-db` to find the problematic > `.ly`

Error with make doc

I've successfully compiled master on my MacBook with M1. I can successfully compile some simple lilypond files. I tried to compile the documentation using make doc. I got this result: carl@Carls-MBP-2 build % make doc Making input/regression/out-www/collated-files.list < 1888 files Making

Re: Installing guile-devel on MacOS M1

On Wed, Jan 17, 2024 at 12:21 PM Carl Sorensen wrote: > I'm trying to get a native M1 MacOS build of Lilypond going. > > > Anybody have any ideas how to solve this? > It looks like I was able to solve this by symbolically linking the pkgconfig files from the Homebrew tree

Installing guile-devel on MacOS M1

I'm trying to get a native M1 MacOS build of Lilypond going. I've installed all of the packages listed at https://lilypond.org/doc/v2.25/Documentation/contributor/requirements-for-running-lilypond https://lilypond.org/doc/v2.25/Documentation/contributor/other and

Re: Make `Beam.positions = #beam::slope-like-broken-parts` the default?

On Sat, Nov 25, 2023 at 9:42 AM Werner LEMBERG wrote: > > The positioning of broken beams becomes so much better IMHO if > `Beam.positions = #beam::slope-like-broken-parts` gets used (of course > this is undocumented...) > > Have a look at the images from the regtest `beam-broken-classic.ly`. >

Re: Getting beam subdivision working

Jason, This work is looking amazing.. Great job! I think I like the idea of a Moment rather than a Duration right now. Part of me thought we might want to just use beam_count (which is the equivalent of a dur_log). But as is mentioned in Urs's document, that would preclude any numerator other

Re: Getting beam subdivision working

Jason, Great work! On Fri, Jun 16, 2023 at 5:23 PM Jason Yip wrote: > Hey all, > > > > The other "failing" regression tests concern the purpose of baseMoment. > >

Re: Clef, key, and time-signature changes

On Fri, Jun 2, 2023 at 9:34 PM Werner LEMBERG wrote: > > >> Time signatures are printed at the beginning of a piece > >> and whenever the time signature changes. > > > > That is true, but incomplete: time signatures are also printed when > > the time signature hasn't changed -- and it has been

Re: Use of dev/ branches in Gitlab and GSOC

On Wed, May 31, 2023 at 8:09 AM Han-Wen Nienhuys wrote: > > > On Wed, May 31, 2023 at 3:56 PM David Kastrup wrote: > >> Han-Wen Nienhuys writes: >> >> > On Wed, May 31, 2023 at 5:12 AM Carl Sorensen < >> carl.d.soren...@gmail.com> >> > wr

Use of dev/ branches in Gitlab and GSOC

Developers, In the past we used to have lots of dev/ branches in our git repository as a place to store work in process. IIUC, when we moved to GitLab as our main repository, we moved to a mode of only putting up dev/ branches when they were ready for a merge request, which prevented

Re: Fix Lilypond Beaming GSOC Project

On Tue, May 16, 2023 at 11:35 AM Jason Yip wrote: > Hey Carl, > > I should have the time to get started with the on-boarding process now. > Great news! Sorry I was a day late responding to you. > To reiterate, I have a working develop environment for Lilypond now; I can > edit whatever source

Re: Fix Lilypond Beaming GSOC Project

Hi, Jason! On Thu, May 4, 2023 at 6:42 PM Jason Yip wrote: > Hi Carl and fellow developers! > > I'm excited to work with all of you on Lilypond and hope that we can > complete the project! > > I'll be quite busy with the end of my university semester and may have > reduced communication until

Fix Lilypond Beaming GSOC Project

that during the Bonding period our communication will be less formal than during the coding phase, as we won't have formal milestones during this time. Again, congratulations on being accepted to GSOC! And I hope we can bond well with you over the next three weeks! Carl Sorensen

Re: Preferred Mentor-Mentee Communication, Plan for Auto-Beaming Project

Thanks, Jason. See my answers below. Carl From: Jason Yip Date: Wednesday, March 29, 2023 at 8:45 PM To: Carl Sorensen Cc: Devel Subject: Preferred Mentor-Mentee Communication, Plan for Auto-Beaming Project Hi Carl, I'm CC'ing the developers mailing list, just to let you know. I would

Re: Fwd: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea

On Wed, Mar 22, 2023 at 7:02 PM Jean Abou Samra wrote: > Carl, > > Do you still have the time and availability to be a mentor for this GSoC > project, or should we search someone else? > > Sorry for asking this bluntly. Given that we haven't seen you contributing > in a while, I had thought you

Re: Differences in `web.html`

On 3/21/23, 10:11 AM, "lilypond-devel-bounces+carl.d.sorensen+digest=gmail@gnu.org" wrote: Le mardi 21 mars 2023 à 04:11 +, Werner LEMBERG a écrit : > Thanks for the explanations. Do I understand correctly that we have a > nifty feature (namely showing the file size to download)

Fwd: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea

Forwarding to list, since I apparently didn't add the list to the email as I intended to. -- Forwarded message - From: Carl Sorensen Date: Mon, Mar 20, 2023 at 12:59 PM Subject: Re: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea To: Jason Yip

Re: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea

Jason, I neglected to leave a link to the Contributor's Guide: https://lilypond.org/doc/v2.25/Documentation/contributor/index.html Thanks, Carl On Sun, Mar 19, 2023 at 12:21 AM Jason Yip wrote: > Hello Carl, > > > My name is Jason Yip, and I am interested in learning more about GNU >

Re: Plan for LilyPond 2.24.1

On Wed, Feb 8, 2023 at 11:09 AM Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Wed, 2023-02-01 at 22:39 +0100, Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > Hi all, > > > > after the situation with Debian seems to be resolved (guile-2.2 and > >

Re: Shorthand for \repeat unfold for individual notes

On Mon, Jan 23, 2023 at 5:17 PM Jean Abou Samra wrote: > > > > Le 24 janv. 2023 à 01:06, Aaron Hill a écrit > : > > > > On 2023-01-23 3:58 pm, Jean Abou Samra wrote: > >> Well, so we are basically having the discussion > >>

Re: Shorthand for \repeat unfold for individual notes

On Mon, Jan 23, 2023 at 5:02 PM Aaron Hill wrote: > > Well, blame my email program, as it truncated my original post. I had > intended to fully call out that ** is exponentiation in some language, > thus might not be the best symbol. > > But this discussion is quickly devolving into needless

Re: Shorthand for \repeat unfold for individual notes

On Mon, Jan 23, 2023 at 4:16 PM Aaron Hill wrote: > There is already shorthand for tremolo repeats, so I wondered if there > could be the same for cases when a single note or rest is repeated. > > %% > % Start with music that has repeated notes: > { \time 7/8 a8 8 8 b16 16 16 16 c4 } > > %

Re: New Lilypond logo?

On Mon, Oct 24, 2022 at 4:27 AM Martín Rincón Botero < martinrinconbot...@gmail.com> wrote: > Hi, > > I've been toying with the amazing DALL·E seeing if it can produce a new > modern logo for e.g. the Lilypond website. Personally, I prefer the existing logo. But I'm almost as old as a

Re: source file ... .scm newer than compiled ... .go file

On Wed, Oct 19, 2022 at 2:54 PM Federico Bruni wrote: > > > Il giorno mer 19 ott 2022 alle 18:06:16 +0200, Jean Abou Samra > ha scritto: > > Le 19/10/2022 à 17:25, Federico Bruni a écrit : > >> You have to manually add `/app/dev/bin/lilypond` in Frescobaldi. > >> (it's explained in the Github

Re: MacOS release help

On Tue, Oct 18, 2022 at 9:58 AM Jean Abou Samra wrote: > Le 18/10/2022 à 01:05, Carl Sorensen a écrit : > > In my opinion, we want to have > > a) an installer for Frescobaldi that could install LilyPond if > > desired, and > > b) an installer for LilyPond tha

Re: MacOS release help

On Mon, Oct 17, 2022 at 3:49 PM Alex Harker wrote: > This is a continuation of the discussion from lilypond-u...@gnu.org > in a more appropriate place. > > I’m responding to Jean and Jonas together as the two most recent sets of > comments were strongly related. >

Re: To branch or not to branch

On Wed, Oct 5, 2022 at 2:36 PM Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Wed, 2022-10-05 at 17:23 +, Werner LEMBERG wrote: > > > There are two dimensions here: First, I personally think it doesn't > > > make sense to create a stable branch from a random commit. It >

Re: Mixed chord/note mode

On Mon, Aug 22, 2022 at 12:59 PM Jean Abou Samra wrote: > > > > Le 22 août 2022 à 15:16, Lukas-Fabian Moser a écrit : > > > >  > >> Am 13.08.22 um 22:04 schrieb David Kastrup: > >> We had this discussion a longer time ago, with chords and notes > >> conflicting in that : is used for tremolo

Re: integrating Joram's 'visualindex'

Two pages, NR appendix Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone Get Outlook for Android From: lilypond-devel on behalf of Colin Campbell Sent: Wednesday, July 13, 2022 2:25:55 PM To: lilypond-devel@gnu.org

Re: Question on Required texinfo version

On Sat, Jun 4, 2022 at 4:06 PM John Wheeler wrote: > This is a probably nit, but I thought I'd ask. > > The Contributor's Guide 4.2.2 subheading Other states a requirement for > Texinfo version 6.1 or newer. > > The web.texi file contains the excerpt: > > @c next line is necessary for broken

Re: Should we be touching goops?

On Fri, Jun 3, 2022 at 7:21 AM David Kastrup wrote: > Dan Eble writes: > > > 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

Re: Request/offer

Andre Musselman wrote: > > What is the syntax for placing the chord on a higher fret? I'm not seeing > that. > > > Please see https://lilypond.org/doc/v2.22/Documentation/notation/common-notation-for-fretted-strings#predefined-fret-diagrams To make a fret diagram for a higher fret, just use

Re: Request/offer

These already exist in Lilypond. See fret diagrams. Carl Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone Get Outlook for Android From: lilypond-devel on behalf of Andrew Musselman Sent: Wednesday, June 1, 2022 5:58:39

Re: RFC on MR 1368

On Wed, May 25, 2022 at 11:20 AM Kevin Barry wrote: > > Also technically I cannot "block contributions", nobody in the > > community has the power to do so. > > > > This might be true technically, but in practice your objections are usually > enough. > I think it is important for us to

Re: RFC on MR 1368

On Tue, May 24, 2022 at 4:01 PM Werner LEMBERG wrote: > > Folks, > > > Jonas and I have an intense (and very exhausting) discussion where to > add kerning data. I want to hear more opinions whether I should go > 'route one' (which I prefer) or 'route two' (which Jonas prefers). > > Please have

Re: LilyPond 2.23.8 released

On Wed, Apr 27, 2022 at 7:31 AM Freeman Gilmore wrote: > > > On Wed, Apr 27, 2022 at 9:04 AM Tim's Bitstream > wrote: > >>  >> >> On Apr 26, 2022, at 9:32 PM, Freeman Gilmore >> wrote: >> >>  >> >> >> On Tue, Apr 26, 2022 at 7:58 PM David Kastrup wrote: >> >>> Freeman Gilmore writes: >>>

Re: Slanted Beams thickness

On Thu, Mar 24, 2022 at 6:46 PM Valentin Petzel wrote: > Hello, > > Lilypond handles slanted Beams in a geometrically weird way, that is, the > thickness is not measured as the shortest distance between the opposing > sides > of the boundary, but as vertical distance. This results in Beams

Re: Slanted Beams thickness

On Fri, Mar 25, 2022 at 7:47 AM Valentin Petzel wrote: > Are you sure about this? It is incredibly hard to cut diagonal lines with > a > chisel. As I mentioned half an hour ago this would have hardly any effect > in > the common cases anyway. > No, I'm not sure about this. It was my

Re: Slanted Beams thickness

On Thu, Mar 24, 2022 at 6:46 PM Valentin Petzel wrote: > Hello, > > Lilypond handles slanted Beams in a geometrically weird way, that is, the > thickness is not measured as the shortest distance between the opposing > sides > of the boundary, but as vertical distance. This results in Beams

Re: "Structure and interpretation" of Scheme

Here's a link that is actually live, I think: https://cdn.preterhuman.net/texts/computing/programming/LISP/Scheme/An%20Introduction%20to%20Scheme%20and%20its%20Implementation.pdf Here's another: http://www.cs.rpi.edu/academics/courses/fall00/ai/scheme/reference/schintro-v14/schintro_toc.html

Re: LilyPond 2.23.6 released

On 2/16/22, 7:37 AM, "lilypond-devel on behalf of Thomas Scharkowski" wrote: Hi all, I installed this version today, everything seems to work. It might be of interest that the MacPorts version of 2.23.6 runs around three times faster on my MacBookPro M1, macOs 12.1

Re: Comments wanted on code highlighting in PDF output

On 2/24/22, 9:03 AM, "Werner LEMBERG" wrote: > I believe that these pdf documents are a significant improvement. I > love them. Good to hear, thanks. > I do not see the need to use the syntax highlighting in the text > references. In fact, I think the

Re: Comments wanted on code highlighting in PDF output

On 2/21/22, 7:50 AM, "lilypond-devel on behalf of Werner LEMBERG" wrote: Folks, Merge request https://gitlab.com/lilypond/lilypond/-/merge_requests/1210 is now mature enough to produce LilyPond documentation with syntax B/W highlighting of

Re: Stepping down from Patch Meister role

James, How much time do you spend per week as Patch Meister? If the time requirement is manageable, I could step in. I don't have lots of time to spend on Lilypond (hence my lack of current development work), but I could plan to spend some. Please help me understand the time you spend.

Re: 'blackpetrucci' stem attachment

On 1/15/22, 11:08 AM, "lilypond-devel on behalf of Jean Abou Samra" wrote: Hi, On lilypond-user-fr, a user wonders about this: \version "2.23.6" { \override NoteHead.style = #'petrucci c'8 \override NoteHead.style = #'blackpetrucci

Re: Why is NonMusicalPaperColumn.line-break-system-details.extra-offset "upside down"?

On 1/1/22, 2:43 PM, "Jean Abou Samra" wrote: I don't know much about the code that places systems on the page, but I think the issue is just that there are two code paths applying extra-offsets, with two different coordinate systems. You are certainly correct. Thank

Re: Why is NonMusicalPaperColumn.line-break-system-details.extra-offset "upside down"?

On 1/1/22, 2:05 PM, "Kieren MacMillan" wrote: Hi Carl, > I assume it is because the negative offset reduces the skyline of the broken (following) system, which allows the spacing engine to raise that system. But extra-offset doesn't (or at least shouldn't) affect the

Re: Why is NonMusicalPaperColumn.line-break-system-details.extra-offset "upside down"?

I assume it is because the negative offset reduces the skyline of the broken (following) system, which allows the spacing engine to raise that system. Carl Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone Get Outlook for Android

Re: [RFC] Moving to Guile 2.2 and away from GUB

On 11/24/21, 1:17 PM, "Jean Abou Samra" wrote: Le 24/11/2021 à 20:54, Carl Sorensen a écrit : > IIRC, it has some start-up overhead, but runs almost as fast as 1.8 if you discount the overhead. The current major problem with 2.2 as far as I understand it is that it

Re: [RFC] Moving to Guile 2.2 and away from GUB

Hi, Jonas, I think your plan sounds good. I think GUB was a great idea, but it has proven difficult to maintain. And the creator of GUB (Jan), has indicated that he thinks it is not worth continuing to work on. So GUB has been a dead man walking for some time. I LOVE the idea of build

Re: MIDI title?

On 11/19/21, 1:31 PM, "lilypond-devel on behalf of David Kastrup" wrote: Aaron Hill writes: > On 2021-11-19 11:28 am, David Kastrup wrote: >> What are other people's feelings here? Should we allow an explicit >> specification of the title as "" to override such a

Re: TimeSignature with note in denominator

On 11/15/21, 10:21 AM, "lilypond-devel on behalf of Flaming Hakama by Elaine" wrote: According to the semantics quoted several times, the denominator describes the length/duration of the unit, the numerator describes how many units are in the measure. There is some space

Re: TimeSignature with note in denominator

On 11/14/21, 9:33 AM, "David Kastrup" wrote: Kieren MacMillan writes: > Hi David, > >> How is that uniquely identified? Why couldn't it be subscripted with 10 instead of 5? > > I suppose it could. It could also be subscripted with a π or a √2. I > can’t

Re: TimeSignature with note in denominator

On 11/13/21, 4:05 PM, "David Kastrup" wrote: Kieren MacMillan writes: > Hi David, > >> It doesn't answer the question. > > Did my explicit answer in the other email (i.e., “one > quintuplet-sixteenth-note”) not suffice? No. You propose replacing

Re: TimeSignature with note in denominator

On 11/13/21, 3:44 PM, "Kieren MacMillan" wrote: Hi David, > It doesn't answer the question. Did my explicit answer in the other email (i.e., “one quintuplet-sixteenth-note”) not suffice? Would that be \times 4/5 16 ? Or \tuplet 5/4 16 ? Carl

Re: TimeSignature with note in denominator

On 11/13/21, 1:00 PM, "Kieren MacMillan" wrote: Hi Carl, Thanks for weighing in! You're welcome > we could not tell the difference between 8.~8 and 8~8., although I can't imagine how the difference between these two representations would be important; both

Re: TimeSignature with note in denominator

On 11/13/21, 1:09 PM, "David Kastrup" wrote: Carl Sorensen writes: > I have not been a strong contributor to this thread. And I have not > been a strong advocate for the time signatures with a notehead in the > denominator. I think all of those

Re: TimeSignature with note in denominator

I have not been a strong contributor to this thread. And I have not been a strong advocate for the time signatures with a notehead in the denominator. I think all of those time signatures can be expressed just as well as a compound meter. HOWEVER, In looking at this, is seems the lexer

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

On 11/7/21, 12:46 PM, "lilypond-devel on behalf of Kieren MacMillan" wrote: Obvious “low-hanging fruit” [at least from the perspective of motivation]: I want — nay, need! — the part combiner to Do The Right Thing™: effectively unlimited voice inputs, no problem with quotes and

Re: What is the point of bug-lilypond?

On 10/16/21, 4:55 AM, "lilypond-devel on behalf of Jean Abou Samra" wrote: A factor to consider is that, as far as I can read http://lilypond.org/bug-reports.html (but I can't remember how it worked for myself), posting to bug-lilypond requires being subscribed to the

Re: [Doc] Organizing changes.tely

On 10/11/21, 12:17 PM, "lilypond-devel on behalf of Jonas Hahnfeld via Discussions on LilyPond development" wrote: Am Samstag, dem 09.10.2021 um 19:28 +0200 schrieb Jean-Charles Malahieude: > Hello all, > > In the last days of 2017, just before 2.20 was born, James

Re: Proposing commit access for Lukas-Fabian Moser

I trust Jean's recommendation on this. Carl

Re: Changed behavior 2.18.0 to 2.22.1

This is definitely a bug. Please post to bug-lilypond. Thanks, Carl

FW: Question on commit c478396f Move all doc building logic to Documentation/GNUmakefile

Forwarding to list, because I didn't reply to all. Sorry! On 9/29/21, 8:35 PM, "Carl Sorensen" wrote: John, On 9/29/21, 5:12 PM, "lilypond-devel on behalf of John Wheeler" wrote: Thank you to both you and Jean. I must

Re: Shortcut for \repeat unfold

On 9/28/21, 6:16 PM, "Dan Eble" wrote: 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 inva

Re: Shortcut for \repeat unfold

On 9/28/21, 5:51 PM, "lilypond-devel on behalf of Dan Eble" wrote: > 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

Re: Shortcut for \repeat unfold

On 9/27/21, 3:52 PM, "lilypond-devel on behalf of David Kastrup" wrote: Jean Abou Samra writes: > is not entirely true: once a function is defined, it can be > relied on internally. Imagine my embarrassment when I had to > explain on -user-fr the cause of the error

Re: Problem

On 8/1/21, 10:21 AM, "lilypond-devel on behalf of Jonas Hahnfeld via Discussions on LilyPond development" wrote: > For me, personally, I'd prefer to see us follow up with either Marnen's or Jaques's work (they may actually be very similar -- I'm not sure) so we can get

Re: Problem

On 8/1/21, 8:42 AM, "lilypond-user on behalf of Craig Comstock" wrote: > Could I help/ volunteer somehow that this workaround gets integrated in the current download version, don't know if that error only happens with MacOS X.14.6 aka 'Mojave' though. FWIW I am using 20.0

Re: Unable to get to Gitlab/lilypond

On 7/15/21, 1:06 PM, "lilypond-devel on behalf of James" wrote: Hello, I am not able to access any MRs or even issues at our gitllab project - generic Error 500. I had that problem also but it has now gone away. Carl

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

Jonas, Thanks for these builds. I have tested the MacOS x86_64 version and have no problems running it on Catalina from Frescobaldii. It has worked well with every score I've tried. Of course, my scores are pretty vanilla, but I do use partcombine a lot. My system is too old to run Big Sur,

Re: Lilypond 64-bit binaries

access to that Apple hardware? Thanks, Carl From: Marnen Laibow-Koser Date: Thursday, April 2, 2020 at 2:18 PM To: Carl Sorensen Cc: LilyPond Users , Moritz Heffter Subject: Re: Lilypond 64-bit binaries On Thu, Apr 2, 2020 at 1:49 PM Carl Sorensen mailto:c_soren...@byu.edu>> wrote:

Re: Outstanding Issues

On 3/15/21, 5:09 PM, "lilypond-devel on behalf of Al Rice" wrote: Is there a list of outstanding issues for LilyPond? https://gitlab.com/lilypond/lilypond/-/issues There are a lot of them! Carl

  1   2   3   4   5   6   7   8   9   10   >