Re: macOS 64-bit

On 1/7/20, 3:22 PM, "lilypond-devel on behalf of Marnen Laibow-Koser" wrote: On Tue, Jan 7, 2020 at 5:15 PM Hans Åberg wrote: > > > On 7 Jan 2020, at 22:20, Marnen Laibow-Koser wrote: > > > > On Tue, Jan 7, 2020 at 4:16 PM Hans Åberg wrote: > > [...] > >

Re: GUB newbie question

On 1/1/20, 12:09 AM, "Jacques Menu" wrote: Hello Marco, Thanks for the information, and a happy new year 2020! JM > Le 28 déc. 2019 à 10:26, Marco Atzeri a écrit : > > Am 27.12.2019 um 10:32 schrieb Jacques Menu: > plus of course gcc compiler,

Re: GUB newbie question

I can't remember. I'd just start with autotools and do ./configure, and work my way through the output one package at a time. Excuse my Phone spellcheck From: Jacques Menu Sent: Friday, December 27, 2019 2:32:07 AM To: Carl Sorensen Cc: Jacques Menu ; Marco

Re: GUB newbie question

On 12/26/19, 3:39 PM, "lilypond-devel on behalf of Jacques Menu" wrote: What is is exactly that fails when building LilyPond on those various OSes? Dependencies of some kind, or basic compilation problems of Lily’s code base? It's been too long since I tried it for me to give you a

Re: GUB newbie question

On 12/26/19, 6:10 AM, "lilypond-devel on behalf of Muzhic" wrote: Hello folks, If a C++ compiler, flex, bison and Guile are installed on Windows or Mac OS X, what prevents LilyPond from being built — in other words, why is GUB needed? GUB was created because having a user create

Re: Issue 5621: Improve rehearsal mark position at beginning of staff (issue 547340043 by nine.fierce.ball...@gmail.com)

On 12/19/19, 2:28 PM, "lilypond-devel on behalf of nine.fierce.ball...@gmail.com" wrote: On 2019/12/17 18:49:41, dak wrote: > On 2019/12/17 17:57:52, Dan Eble wrote: > > I haven't looked very deeply into the potential use of an unpure-pure > container. > > It looks

Re: create code tests

Dan, This is a great explanation. Can you add this to the CG? Anywhere that it seems to make sense. Thanks, Carl On 11/29/19, 3:18 PM, "lilypond-devel on behalf of Dan Eble" wrote: On Nov 29, 2019, at 16:20, wrote: > > I am familiar with the use of makefile. So if you

Re: Midi block gives errors with bar number checks

On 11/27/19, 9:55 AM, "Dan Eble" wrote: On Nov 27, 2019, at 11:35, Carl Sorensen wrote: > > It’s not bar checks causing the problem, it's bar number checks. Oh, thanks for the correction. It doesn't look difficult to add a context property t

Re: Midi block gives errors with bar number checks

On 11/27/19, 9:29 AM, "lilypond-devel on behalf of Dan Eble" wrote: > On Wed, 27 Nov 2019 10:51:15 +0100 (CET), Martin Tarenskeen wrote: > >> I use MIDI output mainly for proofreading, but at occasions where I need >> better MIDI output I always create separate scores for

Re: Midi block gives errors with bar number checks

On 11/27/19, 7:20 AM, "lilypond-devel on behalf of James Lowe" wrote: Hello, On Wed, 27 Nov 2019 10:51:15 +0100 (CET), Martin Tarenskeen wrote: > > > On Wed, 27 Nov 2019, Peter Toye wrote: > > > I'm not sure how many LP user use the MIDI output

Re: add property label-alignments to OttavaBracket (issue 575330043 by lilyp...@maltemeyn.de)

On 11/26/19, 10:40 PM, "lilyp...@maltemeyn.de" wrote: On 2019/11/23 11:18:10, Malte Meyn wrote: > I would suggest to: > • add the label-alignments property to all spanners with exactly one label > • think about all those different piano pedal grobs, whether they are

Re: What is holding up 2.20 release?

On 11/16/19, 2:14 PM, "David Kastrup" wrote: Carl Sorensen writes: > On 11/16/19, 1:52 PM, "David Kastrup" wrote: > > Carl Sorensen writes: > > > Dear Team, > > > > It seems to me li

Re: What is holding up 2.20 release?

On 11/16/19, 1:52 PM, "David Kastrup" wrote: Carl Sorensen writes: > Dear Team, > > It seems to me like we are pretty much in shape such that we should > release 2.20. I'd be fine if we called 2.19.83-1 the 2.20 release, > even i

What is holding up 2.20 release?

Dear Team, It seems to me like we are pretty much in shape such that we should release 2.20. I'd be fine if we called 2.19.83-1 the 2.20 release, even if there are some critical regressions. 2.19.83 is SO much better than 2.18.2. IIUC, the only thing 2.20 is waiting on is for David K. to

Re: Implement MeasureAttachedSpanner (issue 571180043 by david.nales...@gmail.com)

On 11/16/19, 7:49 AM, "Kieren MacMillan" wrote: >> I'd vote for MeasureSpanner. > +1 +1 Kieren. MeasureSpanner works for me. Carl

Re: MacOS 64bit installer

I'm sorry about the broken link. It's fixed here. On 10/31/19, 12:24 PM, "lilypond-devel on behalf of Carl Sorensen" wrote: On 10/31/19, 12:06 PM, "lilypond-devel on behalf of Malte Meyn" wrote: Is it foreseeable whether and when a simp

Re: MacOS 64bit installer

On 10/31/19, 12:06 PM, "lilypond-devel on behalf of Malte Meyn" wrote: Is it foreseeable whether and when a simple solution will exist for the 64 bit problem? Cheers, Malte P.S.: IIUC Frescobaldi doesn’t have such problems, does it? There is certainly a

Re: expected outcome of make check

On 10/28/19, 1:35 PM, "lilypond-devel on behalf of Jonas Hahnfeld" wrote: Am Samstag, den 26.10.2019, 08:43 +0100 schrieb James: > 1. ./autogen --noconfigure > > 2. mkdir build > > 3. cd build > > 4 ../configure --disable-optimising > > 5. make -j7

Re: make check is broken (again) - patch testing seeming to taking more of my time than I like

On 10/28/19, 7:53 AM, "lilypond-devel on behalf of Dan Eble" wrote: On Oct 28, 2019, at 05:32, Werner LEMBERG wrote: > Last OS error: No such file or directory > > because the `share' tree present in > > gub/uploads/webtest/v2.21.0-1-unpack/v2.19.83-1/ >

Re: Regression test flip feature

On 10/18/19, 9:56 AM, "lilypond-devel on behalf of Dan Eble" wrote: Live demo: http://faithful.be/tmp/test-results Go to the images for rest-dot-position and press the "Flip" button under the right-hand image. The new image should change to the old image while the

Re: make test-redo

On 10/14/19, 3:41 PM, "lilypond-devel on behalf of Dan Eble" wrote: "make test-redo" seems to be defective, so I’m thinking of removing it and simplifying the Contributor’s Guide. The last discussion I can find of it in the lilypond-devel archive is from 7 years ago, but I thought it

Re: Compiling instructions for macOS 10.15 Catalina

Have you made sure to try the following, listed in that thread? > I did have to make one change to the Portfile > for lilypond-devel. I added macports-gcc-9 at the top of the > compiler.fallback-append list, because MacPorts was mistakenly trying and > failing to build gcc8 as a dependency. The

Re: The behavior of "make check"

Given that make will not do anything if the source tree has not been changed, I see no problem (and plenty of benefit) in having make check do the equivalent of make && make check. Personally, however, I prefer to do make make check rather than make && make check because I want to see my

Re: lilypond does not work with Mac OS 10.15 (Catalina)

From: Eric Benson Date: Thursday, October 10, 2019 at 9:42 AM To: Carl Sorensen Cc: "lilypond-devel@gnu.org" Subject: Re: lilypond does not work with Mac OS 10.15 (Catalina) I could, but it is quite unreasonable to expect Lilypond users to build from source code, especially havin

Re: lilypond does not work with Mac OS 10.15 (Catalina)

That's great news! Can you provide us instructions so we can share them with other users? Excuse my Phone spellcheck From: Eric Benson Sent: Thursday, October 10, 2019 9:01:57 AM To: Carl Sorensen ; lilypond-devel@gnu.org Subject: Re: lilypond does not work

Re: lilypond does not work with Mac OS 10.15 (Catalina)

On 10/8/19, 7:34 AM, "lilypond-devel on behalf of Karlin High" wrote: On 10/8/2019 2:57 AM, Maria-Angeles Casares-de-Cal via lilypond-devel wrote: > Will we have news soon of the new Lilypond (64 bits) to work in macOS 10.15? > > We hope you can solve this issue. It is

Re: gub targets + binary packages

On 10/7/19, 1:47 PM, "Jonas Hahnfeld" wrote: Am Montag, den 07.10.2019, 19:23 +0000 schrieb Carl Sorensen: > > On 10/7/19, 1:10 PM, "Jonas Hahnfeld" < > hah...@hahnjo.de > > wrote: > > Am Montag, den 0

Re: gub targets + binary packages

On 10/7/19, 1:10 PM, "Jonas Hahnfeld" wrote: Am Montag, den 07.10.2019, 17:51 +0000 schrieb Carl Sorensen: > > On 10/7/19, 11:27 AM, "lilypond-devel on behalf of Jonas Hahnfeld via lilypond-devel" < > lilypond-devel-bounces+c_sorensen=

Re: gub targets + binary packages

On 10/7/19, 12:33 PM, "David Kastrup" wrote: Carl Sorensen writes: > On 10/7/19, 11:27 AM, "lilypond-devel on behalf of Jonas Hahnfeld via lilypond-devel" wrote: > > Hi all, > > lately I've been playing with

Re: gub targets + binary packages

On 10/7/19, 11:27 AM, "lilypond-devel on behalf of Jonas Hahnfeld via lilypond-devel" wrote: Hi all, lately I've been playing with gub, partly to get python3 packaged. Upon inspection, it seems some targets are broken and some are ... a bit out-of-date:

Re: 2.20 release roadmap

We are stuck for release because GUB is not working properly. Until we get GUB to work properly, we cannot make a release. As far as I know now, the answer is in fact indefinite. Thanks, Carl On 9/19/19, 6:14 PM, "Andrew Bernard" wrote: I do hope this is not seen as impertinent,

Re: Build Mac binary

with released Mac builds. Carl Sorensen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https

Re: problem with predefined-guitar-fretboards.ly?

On 7/18/19, 8:34 AM, "lilypond-devel on behalf of Wols Lists" wrote: On 17/07/19 13:55, David Kastrup wrote: > f:aug is clearly wrong, aes:aug has the right notes but the root note is > awkward, not being the lowest. I have no idea how guitarists would feel > about that.

Re: lilypond-devel Digest, Vol 200, Issue 23

On 7/17/19, 2:04 PM, "lilypond-devel on behalf of Christopher Heckman" wrote: > f:aug is clearly wrong, aes:aug has the right notes but the root note is > awkward, not being the lowest. I have no idea how guitarists would feel > about that. My guess is: not too good.

Re: problem with predefined-guitar-fretboards.ly?

On 7/17/19, 6:55 AM, "lilypond-devel on behalf of David Kastrup" wrote: James writes: > Hello, > > I saw arecent update by a LP user to an 'already-fixed' tracker > > > > That made it into my inbox

Re: stem.cc - issue 5303 - misplaced notehead (issue 570830043 by pkxgnugi...@runbox.com)

On 7/11/19, 11:49 AM, "Lukas-Fabian Moser" wrote: Hi Carl, > Perhaps this patch should also revert > 87eb2f9fe1be3a532675fe4b7322bbba5a60ba5c > > since that patch was a workaround, rather than a real fix, as > demonstrated during this troubleshooting thread. >

Re: stem.cc - issue 5303 - misplaced notehead (issue 570830043 by pkxgnugi...@runbox.com)

On 7/11/19, 9:18 AM, "lilypond-devel on behalf of lukasfabianmo...@googlemail.com" wrote: As for Carl's suggestion, I'm trying now to understand the relationship between 87eb2f9fe1be3a532675fe4b7322bbba5a60ba5c and the bugs/patches under consideration. I withdraw my

Re: Strange space between beam and slur

On 6/22/19, 3:48 PM, "Lukas-Fabian Moser" wrote: That's about as much as I can contribute, I guess. Does anybody have an idea what precisely is causing the problem? Hmm, this works for me on 2.19.82 running on OSX under Frescobaldi. No extra space. What is your system

Re: What version of guile to build 2.21.0

1.8 On May 17, 2019 9:27 PM, Andrew Bernard wrote: What version of guile should I be using to build 2.21.0 on Ubuntu (or indeed any Linux)? Apologies for my ignorance, but it is not immediately obvious to me where this is documented. Andrew ___

Re: macOS 64-bit

I'm pretty sure there are no Mac build instructions for Lilypond. The Linux build instructions are in the Contributor's Guide. GUB is a Linux build environment. Daniel reported success in a Homebrew build for the Mac. I would guess that he's willing to share it with you. I hope you can get

Re: Charles Winston's chord-semantics GSOC work

On 4/8/19, 7:41 PM, "lilypond-devel on behalf of Flaming Hakama by Elaine" wrote: I understand that in the lily syntax, using c:7+ makes mathematical sense, since following chord naming convention, the "7" refers to dominant 7, or the b7, and we are interested in saying that

Re: Charles Winston's chord-semantics GSOC work (issue 568650043 by carl.d.soren...@gmail.com)

On 4/8/19, 1:59 PM, "thomasmorle...@gmail.com" wrote: On 2019/04/08 18:47:13, lilypond-pkx wrote: > Are we sure all the reg tests are OK (see tracker for download link)? > For example > regression/chord-name-major7.ly > This looks completely broken with

Re: Charles Winston's chord-semantics GSOC work (issue 568650043 by carl.d.soren...@gmail.com)

On 4/2/19, 3:20 PM, "v.villen...@gmail.com" wrote: Hi Carl, I appreciate you taking the time to rework this patch, does it mean you’re intending to shepherd Charles’ work until it gets merged? Yes. In addition to Paul’s comments which you’ve nicely addressed, I had a few

Re: Gvim point and click guide

From: Andrew Bernard Date: Tuesday, February 26, 2019 at 8:18 PM To: Carl Sorensen Cc: Devel Subject: Re: Gvim point and click guide Hi Carl, Some interlineated comments. Should I just make this a tutorial on Scores of Beauty? But it seems very integral to lilypond to me, and many people

Re: Gvim point and click guide

On 2/26/19, 4:32 PM, "lilypond-devel on behalf of Andrew Bernard" wrote: There's been a lot of long discussion about how to get gvim going with point and click lately. I finally achieved this, but found the NR missing important information, and to be ever so slightly in error. To

Re: 64-bit version of Lilypond?

On 2/25/19, 5:25 PM, "Karlin High" wrote: On 2/25/2019 10:44 AM, Carl Sorensen wrote: > A further look into PureDarwin's website shows that many of the Darwin utilities in fact link to closed-source Apple libraries. > > So probably we can't even ship

Re: 64-bit version of Lilypond?

On 2/25/19, 5:23 AM, "lilypond-devel on behalf of David Kastrup" wrote: Karlin High writes: > I'm still thinking it would be ideal if the macOS LilyPond could be > built as it now is. That's the least work for LilyPond build people, > and probably the best result for

Re: 64-bit version of Lilypond?

On 2/25/19, 5:23 AM, "lilypond-devel on behalf of David Kastrup" wrote: Karlin High writes: > I'm still thinking it would be ideal if the macOS LilyPond could be > built as it now is. That's the least work for LilyPond build people, > and probably the best result for

Re: 64-bit version of Lilypond?

On 2/24/19, 12:47 PM, "lilypond-devel on behalf of David Kastrup" wrote: Hans Åberg writes: >> On 24 Feb 2019, at 19:28, Karlin High wrote: >> >> On Sun, Feb 24, 2019, 7:26 AM Hans Åberg wrote: >> >> > On

Re: 64-bit version of Lilypond?

On 2/23/19, 5:13 PM, "lilypond-devel on behalf of Hans Åberg" wrote: > On 23 Feb 2019, at 22:26, Karlin High wrote: > > Full quote: > > " > we use GUB (see ) to build binaries, not Xcode. We link

Re: 64-bit version of Lilypond?

On 2/23/19, 3:34 PM, "Karlin High" wrote: On 2/23/2019 4:11 PM, Carl Sorensen wrote: > I have no idea how best to go after creating an OSX 64-bit binary in gub. I think we can neither provide the Xcode binaries nor find a link that will allow gub to download

Re: 64-bit version of Lilypond?

On 2/23/19, 2:39 PM, "lilypond-devel on behalf of David Kastrup" wrote: Karlin High writes: > On 2/14/2019 4:04 AM, David Kastrup wrote: >> It may well be that the licensing conditions of any such SDK spell >> end-of-line for MacOSX support since Apple is allergic to

Re: Dedicated functions for negative predicate tests (issue 345190043 by v.villen...@gmail.com)

On 2/8/19, 10:17 AM, "lilypond-devel on behalf of d...@gnu.org" wrote: On 2019/02/08 17:05:46, Valentin Villenave wrote: > On 2019/02/08 16:41:06, dak wrote: > > For what? > Since you’re complaining about LilyPond-specific functions not handled by Guile, > what

Re: Please test gub

On 2/6/19, 3:42 PM, "lilypond-devel on behalf of Knut Petersen" wrote: >> - the need to make sure that `python` calls a python2 interpreter. > No idea how this could be solved elegantly. I guess it can't, so we > have again something to document... > Use /usr/bin/env

Re: grand copyright replacement

On 1/25/19, 4:16 AM, "lilypond-devel on behalf of Werner LEMBERG" wrote: So is it OK to simply update the missing cases? Assuming we are running `grand-replace' next year again this would be (in almost all cases) a one-time job. In my opinion, yes. Thanks for looking at this.

Re: Python compatibility

On 1/15/19, 12:14 PM, "David Kastrup" wrote: > In contrast, migrating to 2.7 is a Gub-only job. That's much > better defined and better cut out to be single-person or at least > single-focus work. > So, if I understand correctly, we (mostly) think that

Re: Python compatibility

On 1/15/19, 11:37 AM, "David Kastrup" wrote: Carl Sorensen writes: > 1) Why should I prefer 2.7.x over 3.7x (or vice versa)? All of my > python coding to this point has been in 2.x. I suspect there would be > lots more changes to go to 3.x. So any

Python compatibility

On 1/15/19, 6:05 AM, "lilypond-devel on behalf of Knut Petersen" wrote: @everybody: Does anybody volunteer to write a patch to allow python to be compatible with gcc 8? Probably it's easier to tell python's config to look for a gcc-7 (and maybe some other names) if the systems gcc

Re: speeding up issue #5456

On 1/11/19, 2:32 PM, "lilypond-devel on behalf of Werner LEMBERG" wrote: I've just updated the patch for issue #5456; a complete gub build from scratch unveiled that it didn't work as expected. http://codereview.appspot.com/349090043 To continue my work on

Re: GUB lilypond build fails

On 12/16/18, 6:42 PM, "lilypond-devel on behalf of Andrew Bernard" wrote: Hi All, I am new to lilypond dev. work. My intention may be naive, but I am wanting to do the work to uplift gub and lilypond to python 3. Am I premature, or foolish, or misguided? I did have some

Re: GUB lilypond build fails

On 12/16/18, 4:38 PM, "lilypond-devel on behalf of Werner LEMBERG" wrote: >I think you have the same issue me and others had. You don't see >it in the tail below, but if you open the lilypond.log file >you'll see a python command failing to generate a file

Re: GSoC Proposal - SVG Export

On 12/2/18, 1:30 PM, "Étienne Beaulé" wrote: That is more of a problem with Pixbuf (similar problem was fixed in librsvg). However, a case could be made to specify black for glyphs instead of currentColor, and I would be open to it (leaning against it though) However, changing

Re: GSoC Proposal - SVG Export

On 11/30/18, 8:40 PM, "lilypond-devel on behalf of Étienne Beaulé" wrote: Hello all! I’m Étienne Beaulé and I’ve been making some changes to LilyPond. I am also the maintainer of the MediaWiki Score extension which allows embedded LilyPond on Wikipedia. I’m currently a bachelor

Re: GSoC Proposal - SVG Export

On 12/1/18, 9:21 PM, "Étienne Beaulé" wrote: Having glyph styling through CSS is one of the goals of this project. In the use of « currentColor, » it does seem to follow specifications. If an object does not have a colour associated with it, it should leave the colour to the viewer.

Re: GSoC Proposal - SVG Export

On 12/1/18, 1:22 AM, "lilypond-devel on behalf of Richard Shann" wrote: It is probably a very small thing, but it would be good if you could improve the SVG output with regard to the use of "current color" which Lily outputs as the default foreground color rather than black.

Re: New LilyPond contributor: Basia Mroczek

I recommend that you start by building on LilyDev, rather than on your own system. You can set up LilyDev in a VM, and make sure that all goes well. Then, if you still want to, you can try to get it building on your own system. Personally, I gave up trying to keep lilypond building on my

Re: New LilyPond contributor: Basia Mroczek

Welcome, Basia! We're always excited to see new people join in with us! Janek is a great resource; I expect the two of you to make great contributions to LilyPond. And I hope you'll have fun doing so! Carl Sorensen Provo, UT, US From: lilypond-devel

Re: what happened with janneke/gub on github?

On 11/20/18, 3:08 PM, "lilypond-devel on behalf of Karlin High" wrote: On 11/20/2018 3:48 PM, Werner LEMBERG wrote: > Yes, but our documentation still talks about Jan's repository, which > seemed to be available a few months ago, and which is now gone. (CC to Jan

Re: Use a stable sort when ordering MIDI items (issue 353790043 by mrbobo1...@gmail.com)

On 10/31/18, 7:32 PM, "Dan Eble" wrote: On Oct 31, 2018, at 14:00, carl.d.soren...@gmail.com wrote: > > Why not always have our sort use stable_sort? Because when someone finally clears away std-vector.hh, they will be more likely to mess it up if sort() needs to be

Re: Problem with guile-2.9.1-prerelease

On 10/11/18, 12:35 PM, "lilypond-devel on behalf of Urs Liska" wrote: Am 11. Oktober 2018 20:17:45 MESZ schrieb Karlin High : >On 10/11/2018 12:59 PM, David Kastrup wrote: >What level of optimism is appropriate for that claim? I don't think that tells us very

Re: Negative page numbers

Never mind. I only focused on half the comments. Sorry for the noise. Carl Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Negative page numbers

Isnt this talking about negative page heights, not negative page numbers? Carl Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: melismaBusyProperties: scheme syntax vs. lily syntax

On 7/15/18, 6:53 PM, "Simon Albrecht" wrote: On 16.07.2018 02:51, Carl Sorensen wrote: > > On 7/15/18, 3:29 PM, "lilypond-devel on behalf of David Kastrup" wrote: > > Simon Albrecht writes: > > > Hello ev

Re: melismaBusyProperties: scheme syntax vs. lily syntax

On 7/15/18, 3:29 PM, "lilypond-devel on behalf of David Kastrup" wrote: Simon Albrecht writes: > Hello everybody, > > I just noticed that it’s possible to use the LilyPond symbol list/key > list syntax when setting melismaBusyProperties. However, the doc >

Re: GUB

On 7/10/18, 1:30 AM, "David Kastrup" wrote: Carl Sorensen writes: > Are there any opinions on whether we should pursue a move to Guix? Wouldn't that mean abandoning Windows? I haven't looked carefully at GUB for a few years, and even when I did, I scar

Re: GUB

In May, when we were discussing the limitations of 32 bit MinGW, I asked Jan for an estimate of how much work it would be to add a 64-bt MinGW to GUB. His answer was that GUB is a hack, and that he wasn't interested in putting any more effort into fixing up GUB, although he would certainly

Re: C++ standards

On 7/5/18, 12:02 PM, "lilypond-devel on behalf of David Kastrup" wrote: What C++ standard should we be able to ask for? I think that at the current point of time, C++11 should be reasonably fine for the asking. That would have the advantage that we would have a few more

Re: Microrhythm

On 5/26/18, 10:44 AM, "lilypond-devel on behalf of David Kastrup" wrote: Entirely subjective which hill is worth dying on: Güllich was the first to extensively exposed hard "solo" routes, with the

Re: Microrhythm

On 5/21/18, 10:02 PM, "lilypond-devel on behalf of metachromatic" wrote: = Different percentages of microrhythm will require correspondingly larger tuplets, and, due to the

Re: logging an optional input location

On 5/12/18, 1:49 PM, "lilypond-devel on behalf of Dan Eble" wrote: There’s this repetition in context.cc: if (origin) { origin->warning (_f ("cannot find or create `%s' called

Re: LilyDev - some questions

On 5/9/18, 12:08 AM, "lilypond-devel on behalf of Federico Bruni" wrote: Don't you have a date configuration in the system settings? I'll have a look and see if I can improve this. The thing is that

Re: Clarify notation for slurs and beams (issue 343060043 by carl.d.soren...@gmail.com)

On 4/30/18, 11:04 AM, "lilypond-devel on behalf of tdanielsmu...@googlemail.com" wrote: @ref definitely should work. It may be that the heading for one of them is "Articulation and

Re: Skylines and certain grob properties (rotation, extra-offset)

On 4/20/18, 7:44 AM, "lilypond-devel on behalf of Torsten Hämmerle" wrote: What do you think about making skylines consider the grob properties rotation and extra-offset? (1) keep

Re: Allura/SourceForge to Gitlab migration

On 4/9/18, 3:43 PM, "Karlin High" wrote: I wasn't clear on whether the free-Gold-tier-for-open-source was automatic for any public repository, or if it needed GitLab approval. So I tried it out, and the paid-version "squash and merge" feature IS

Re: Allura/SourceForge to Gitlab migration

On 4/9/18, 1:04 PM, "lilypond-devel on behalf of Urs Liska" wrote: Am 9. April 2018 20:06:20 MESZ schrieb James Lowe : >Hello, > >On Mon, 9 Apr 2018 12:56:57

Re: Allura/SourceForge to Gitlab migration

On 4/9/18, 12:14 PM, "Karlin High" <karlinh...@gmail.com> wrote: On 4/9/2018 1:13 PM, Carl Sorensen wrote: > In my GitLab usage we use tags. This feature, perhaps? <https://docs.gitlab.com/ce/user/project/issues/issues_functionalities.html#7-l

Re: Allura/SourceForge to Gitlab migration

On 4/9/18, 12:06 PM, "lilypond-devel on behalf of James Lowe" wrote: Hello, Does Gitlab really only just have 2 status for an 'issue' (Open and Closed) or can this be refined/configured

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

On 2/7/18, 9:05 AM, "David Kastrup" <d...@gnu.org> wrote: Carl Sorensen <c_soren...@byu.edu> writes: > On 2/7/18, 2:37 AM, "lilypond-devel on behalf of Torsten Hämmerle" <lilypond-devel-bounces+c_sorensen=byu@gnu.org on beha

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

On 2/7/18, 8:55 AM, "Kieren MacMillan" wrote: Hi Carl, Of all suggestions so far, I most like your flow/Flow the most. > If we want to capture semantics properly, I believe we need to recognize that there are three different kinds of

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

On 2/7/18, 2:37 AM, "lilypond-devel on behalf of Torsten Hämmerle" wrote: If there will probably even be a MIDI playback in the future, we actually need "real" marks to jump to, not only text

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

How about \flow and FlowScript? Carl Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: maximumFretStretch in TabStaff?

On 1/26/18, 4:40 PM, "lilypond-devel on behalf of David Kastrup" wrote: Thomas Morley writes: > Hi, > > while thinking about a nice lsr-snippet demonstrating usage of

FW: Reverting Beat Grouping Commands

Urs, Here's an old email that discusses a proposed different structure for setting beaming characteristics. The thing that caused me to see this as the most promising is it has settings for both beat grouping (i.e. how to combine beamed notes into groups) and beat subdivision (i.e. how to

Re: Installing URW++ fonts, issue 4998: why not add wget lines to lilydev-setup.sh?

On 10/4/17 4:06 PM, "lilypond-devel on behalf of Karlin High" wrote: >https://codereview.appspot.com/315850043/ >https://sourceforge.net/p/testlilyissues/issues/4998/ > >I found this issue with the fonts while

Re: Better discoverability for thin-variant Aiken heads: add to snippets, docs, or features?

On 9/8/17 12:47 PM, "lilypond-devel on behalf of Karlin High" wrote: > >a snippet for the LSR, >a reference in the documentation, perhaps under NR 1.1.4 Shape note heads, >adding a feature to LilyPond, the command

Re: Things that make you go hmmm

On 9/5/17 10:42 AM, "lilypond-devel on behalf of James" wrote: >Anyway, it threw up a reg test diff. > >(attached). > >See if you can spot it (second to last bar). > >tres 'odd' n'est pas? Hmm. The dot column

Re: New repeat type

Original message From: Dan Eble <d...@faithful.be> Date: 8/29/17 5:33 PM (GMT-07:00) To: Carl Sorensen <c_soren...@byu.edu> Cc: LilyPond Development Team <lilypond-devel@gnu.org> Subject: Re: New repeat type > On Aug 29, 2017, at 19:14, Carl Sorensen <c

Re: New repeat type

I wouldnt, because it is not a repeat. Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone Original message From: Dan Eble Date: 8/29/17 5:01 PM (GMT-07:00) To: LilyPond Development Team Subject: New repeat type

Re: rest/mm-rest-markup

On 7/31/17 8:08 AM, "lilypond-devel on behalf of David Kastrup" wrote: > >Now the thing is that with the new change in place, we would not >necessarily _need_ different arguments: an integral multiplier larger >than 1

Re: midi2ly on mac: midi.so wrong architecture

On 7/28/17 3:09 PM, "lilypond-devel on behalf of ElRay" wrote: >>> I am pretty sure that Graham posted a patch for this on one of the >>>lists >>> one of the last times this was being discussed.

<    1   2   3   4   5   6   7   8   9   10   >