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

> On Oct 8, 2019, at 12:04, Dan Eble wrote: > > On Oct 8, 2019, at 11:09, Carl Sorensen wrote: >> Federico Bruno says the latest LilyDev includes a Docker container. >> http://lilypond.1069038.n5.nabble.com/LilyDev-0-3-released-td217945.html >> <http://lilypond

The behavior of "make check"

Begin forwarded message: > > Subject: [testlilyissues:issues] Re: #5564 Fix conversion warnings in beaming > code > Date: October 10, 2019 at 12:08:48 EDT > I'm sorry to contribute to your frustration. I can see what the process is, > but my question (which I direct to LilyPond developers in gen

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

On Oct 10, 2019, at 12:15, Hans Åberg wrote: > On 10 Oct 2019, at 17:55, Eric Benson wrote: >> >>> This is good, but I think GCC 8 was kept deliberately as it was unclear if >>> GCC 9 would work. >> >> gcc8 failed to build on MacPorts on Catalina on the latest Xcode. Rather >> than try to und

Re: better LSR to lilypond snippet conversion tool

On Oct 8, 2019, at 16:21, Werner LEMBERG wrote: > I'm not sure how to proceed. Shall I adapt `makelsr.py' to start > where this script stops? I can't contribute much to an answer, but I want to say that the last time I tried updating snippets (probably over a year ago), the documented process

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

On Oct 8, 2019, at 11:09, Carl Sorensen wrote: > Federico Bruno says the latest LilyDev includes a Docker container. > http://lilypond.1069038.n5.nabble.com/LilyDev-0-3-released-td217945.html > FYI, I’m working on exten

Re: PATCHES - Countdown for October 8th

gt; > 5566 Update python headers to match surrounding files - masterodin > https://sourceforge.net/p/testlilyissues/issues/5566 > http://codereview.appspot.com/565080043 > > 5565 simplify python-related makefiles - Dan Eble > https://sourceforge.net/p/testlilyissues/issues/5565 >

Default make output

Who would cheer/object if I started working on changes to make the build output less verbose by default, which would require saying make VERBOSE=1 … when you actually wanted to see all the commands? By “less verbose,” I mean ideally logging one short line per interesting target at the

Re: Python 3

On Sep 30, 2019, at 19:46, Matthew Peveler wrote: > > I've been maintaining my work in > https://github.com/MasterOdin/lilypond/tree/py3_future2 > . . . > … but I do not know one would approach making it work on both Python 2 and > Python3.7 (and potentially other Python3 targets) and that I t

Re: Python 3

On Sep 30, 2019, at 17:05, Matthew Peveler wrote: > > Please see attached for [ten] patches, which given the work done prior by > Jonas, allows for running the various make targets under both python2&3 > (assuming application of my other two patches for py3) The thought that gave rise to my qu

Re: Python 3

On Sep 30, 2019, at 14:22, David Kastrup wrote: > > But I don't see > that a clean cut from Python2 to Python3 in a single step is easily > feasible and testable for all targets at once including all GUB targets. OK. On Sep 27, 2019, at 16:34, Matthew Peveler wrote: > The primary thing missing

Re: Python 3 (was: 2.20 where are we?)

On Sep 27, 2019, at 16:34, Matthew Peveler wrote: > > I'll have another email later on with patches for having this branch run > under both python2.7 & 3 as the necessary backport efforts were not really > all that extravagant with just a handful of shims around the changes you > noted in long vs

Re: Issue 4365: non-member is_smob<>(), is_derived_smob<>(), etc. (issue 231680043 by nine.fierce.ball...@gmail.com)

On Jun 5, 2019, at 09:33, d...@gnu.org wrote: > > The resulting comment text is nonsensical. That might have been a clue > that the resulting behavior is not up to par, either. I took a new job last October and it doesn’t leave me with much energy to dig into LilyPond issues. — Dan _

Re: add articulation support to multi measure rests (issue 562710043 by lilyp...@maltemeyn.de)

On Apr 27, 2019, at 07:31, David Kastrup wrote: > > But we are talking about a \fermata on an _uncompressed_ multimeasure > rest here. If the compression leaves just a single rest, placing the > fermata does not pose a conundrum to typesetting (it may pose one to the > musician but that's entire

Re: add articulation support to multi measure rests (issue 562710043 by lilyp...@maltemeyn.de)

On Apr 27, 2019, at 04:54, d...@gnu.org wrote: > > Multimeasure rests can be split into multiple rests and across lines. > That's what makes then a Spanner rather than an Item and is the main > cause of this complication. How are you dealing with such a split? A > fermata only makes sense on the

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

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 or should it be treated as a known issue

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

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, e.g. R1*8\fermata * expanded vs. not ex

Re: problems with \cueDuring and events

On Apr 14, 2019, at 08:10, Thomas Morley wrote: > > As far as I understand, it's the partcombiner at work here. > At least: > > \version "2.21.0" > > %% use \partcombine with lowercase "c" for lower versions > \partCombine > \relative { fis'8 fis4. \repeat tremolo 4 { b16 c } r1 } > \relative

Re: Charles Winston's chord-semantics GSOC work

On Apr 9, 2019, at 10:43, Carl Sorensen wrote: > majorSevenSymbol, but since it can be set, in can be unset. And if it is > unset, we should not produce nothing, because then c:7+ will display as C7, > which is the same as c:7. I don't think the display needs to be sensible, > but it needs to

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

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

On Feb 7, 2019, at 14:49, v.villen...@gmail.com wrote: > > That being said, no problem for adding index entries no matter what we > end up choosing. Would anyone else have thoughts on the subject of > \invertChords vs \rotateChords? So that it’s clear: I have no firm objection to \invertChords.

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

On Feb 3, 2019, at 05:36, Valentin Villenave wrote: > > BTW, there’s no proper notion of inversions as such in jazz music > (AFAICT); so the purpose of an \invertChords function here is left to > our appreciation, with the minimal requirement being that the lowest > note of the chord changes each

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

On Feb 2, 2019, at 14:36, v.villen...@gmail.com wrote: > Oh. Then this becomes a whole other can of worms; what should be the > correct inversion of an 11th chord? > > Should > > become > (as you seem to suggest) > or > (as the current code produces)? Isn’t the salient property of an inversi

Re: Let wordwrap-field and justify-field take non-strings?

On Dec 2, 2018, at 09:38, Thomas Morley wrote: > > Currently a formated markup will be dropped entirely without any warning, see: My two cents: at some time in the past year, I was working on a mark performer, and I wanted a way to turn the markup for the mark into a MIDI-compatible string. I

Re: PATCHES - Countdown for Nov 2nd

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/ is not being tracked. —

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

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 transformed into stable_sort() than if the functions parallel those

Re: 2.20 plans.

On Oct 8, 2018, at 11:35, David Kastrup wrote: > This will be followed (as soon as the state of download/web pages and > Phil's resources permit) with releasing 2.21.0 to get an unstable > version to refer to. Request: Distribute 2.21 for macOS as a 64-bit application. macOS 10.14 (“Mojave”) fl

Negative page numbers

> Real > Page_breaking::page_height (int page_num, bool last) const > { > // The caches allow us to store the page heights for any > // non-negative page numbers. We use a negative value in the > // cache to signal that that position has not yet been initialized. > // This means that we wo

Re: Non-quadratic form of whiteout

On Sep 16, 2018, at 12:34, Malte Meyn wrote: > > Do I understand correctly, that instead of making a sort of elliptic whiteout > you would stick to rectangles and ♦ (a diamond) would have an octogonal > whiteout instead of something like a diamond with rounded corners? Are you guys looking fo

Re: LilyDev - some questions

On Aug 27, 2018, at 10:32, Federico Bruni wrote: > > Trying Docker was on my TODO list... Can you send the Docker file? > I'd like to add it to LilyDev repository. I’ve attached what I’m using now, with a little documentation. You are welcome to add it to your LilyDev repository. It is based

Re: LilyDev - some questions

On Aug 28, 2018, at 00:08, Dan Eble wrote: > > Ubuntu 18.04 with GCC 8 and takes Guile 1.6 from Ubuntu 16.04. Guile 1.8. — Dan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Macport version of lilypond: problem with ghostscript

On Aug 23, 2018, at 09:41, Jean-Julien Fleck wrote: > > I like to do almost everything from the command line. > But thanks, the graphical version for MacOS downloaded from lilypond.org > works fine and will allow me to continue my work. lilypond packaged in the macOS app can be invoked from the

Incompatible function types

g++ 8 is spamming my build log with messages like this: /root/lilypond-src/lily/include/smobs.hh:228:37: warning: cast between incompatible function types from 'scm_unused_struct* (*)(SCM, SCM, SCM, SCM)’ {aka 'scm_unused_struct* (*)(scm_unused_struct*, scm_unused_struct*, scm_

Re: LilyDev - some questions

On Jul 26, 2018, at 22:15, Dan Eble wrote: > > On Jul 26, 2018, at 00:47, Federico Bruni wrote: >> - Finally I'd like to figure out a way of running the containers also in a >> Windows or Mac host machine. See this issue: >> https://github.com/systemd/mkosi/issues

Re: Quick question about grob interfaces

On Jul 27, 2018, at 17:21, Han-Wen Nienhuys wrote: > > It's not clear to me how the alist per se is a problem and how > restructuring could fix that. It’s been a couple months, and I only profiled one regtest, but I remember sloppy_assq, string hashing, and string comparison standing out as si

Re: LilyDev - some questions

On Jul 26, 2018, at 00:47, Federico Bruni wrote: > - Finally I'd like to figure out a way of running the containers also in a > Windows or Mac host machine. See this issue: > https://github.com/systemd/mkosi/issues/251 Would xhyve further that goal? (Virtualization software is not my forte.) ht

Re: Limiting the number of accepted contexts

On Jul 12, 2018, at 09:32, David Kastrup wrote: > Karlin High writes: > >> On 7/12/2018 8:21 AM, Werner LEMBERG wrote: >>> What is this good for? >> >> Maybe what's mentioned in the last paragraph of the original post, >> "eliminate a small amount of special code for Global/Score.” > > By repl

Limiting the number of accepted contexts

I am considering allowing context definitions to express that no more than one of a certain child is accepted. This is the currently implicitly the case for Score as a child of Global. I thought a syntax something like this would work: \accepts “Zinnia” % any number of Zinnias is acce

Re: Context_handle

On Jul 8, 2018, at 14:11, David Kastrup wrote: > > I think it's for providing a definite point of time for running the > finishing hooks of a context's iterators and making the context > unavailable for \context ... [= ...] continuations. > > Garbage collection is not determinate. I think I se

Context_handle

What is the purpose of Context_handle? It looks like a scoped contribution to a reference count until the destructor: > Context_handle::~Context_handle () > { > /* > Don't do > if (outlet_) > down (); > with GC, this is asynchronous. > */ > } I can understand garbage collect

Re: C++ standards

On Jul 6, 2018, at 04:40, Knut Petersen wrote: > > Am 05.07.2018 um 20:02 schrieb David Kastrup: >> 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. > > GUB uses gcc 4.9.4, so C++11 is fully implemented

Re: What's up with Grob_info::origin_contexts ?

On Jul 7, 2018, at 10:28, David Kastrup wrote: > accesses to [0]) or should we just say "to heck with it" and throw out > all the stuff that apparently worked without ever needing > origin_contexts? Throw it out. If there is something that needs to navigate the contexts, it shouldn’t have to in

Re: C++ standards

On Jul 5, 2018, at 15:20, Hans Åberg wrote: > >> On 5 Jul 2018, at 20:02, 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. > > The g++7 default, and clang++6, is C++14, but

Re: Now this is a nightmare...

On Jul 4, 2018, at 07:29, David Kastrup wrote: > > Having our own ly_is_integer variant map to the Guile-2 version > conditionally is simple, and when we do it wrong, there is an obvious > missing symbol at link time. Or stuff works without complaint. That’s fine, but if it’s going to be a prox

Re: Issue 5362: Generalize context searches (issue 344050043 by nine.fierce.ball...@gmail.com)

On Jul 1, 2018, at 16:40, d...@gnu.org wrote: > > Premature optimization is the root of all evil. I'm going to > pontificate now in the hope that you'll have some opportunity in your > work life to take karmatic revenge by passing this kind of "wisdom" > on. I sense some frustration. First, ple

Re: Issue 5362: Generalize context searches (issue 344050043 by nine.fierce.ball...@gmail.com)

On Jul 1, 2018, at 15:08, d...@gnu.org wrote: > > We currently have > > dak@lola:/usr/local/tmp/lilypond$ git grep "find or create" lily > lily/context.cc: warning (_f ("cannot find or create new `%s'", > lily/context.cc: warning (_f ("cannot find or create `%s' called `%s'", > dak@lola:/us

Re: Issue 5362: Generalize context searches (issue 344050043 by nine.fierce.ball...@gmail.com)

> On Jul 1, 2018, at 13:14, d...@gnu.org wrote: > > Something like > origin->warning (_f ("Cannot find or create context: %s", > ctx->identification ())) Meh. Multiple callers would repeat the message “cannot find or create context” which is part of what I was trying to avoid. I wouldn’t stake

Re: fix CueEndClef with parenthesized ClefModifier (issue 353720043 by lilyp...@maltemeyn.de)

On Jun 20, 2018, at 16:15, Simon Albrecht wrote: > > On 20.06.2018 21:04, lilyp...@maltemeyn.de wrote: >> https://codereview.appspot.com/353720043/diff/1/input/regression/cue-clef-transposition-optional.ly#newcode1 >> >> input/regression/cue-clef-transposition-optional.ly:1: \version "2.21.0" >

Re: make doc bombs out in MusicXML

On Jun 16, 2018, at 08:46, James Lowe wrote: > > Well before I applied those patches on behalf of Alexander's patches I did a > full patch test with the patches applied and had no problems. > > However ... I know that there are some 'prgramming errors' reported that do > not break patch testin

Re: Issue 5336: Remove downcasting methods from Grob_array and Grob_info (issue 344010043 by nine.fierce.ball...@gmail.com)

On Jun 12, 2018, at 18:18, carl.d.soren...@gmail.com wrote: > > The tradeoff of having people know about dynamic casting and using it > properly needs to be matched with people not needing to know about > dynamic casting and being able to ignore it. Carl, I appreciate hearing your perspective and

Re: logging an optional input location

On May 12, 2018, at 16:17, Carl Sorensen wrote: > > Does our code base use the optional second parameter anywhere? If not, maybe > it would be even simpler to eliminate the optional second parameter, and just > call > > warning (_f (. . .), origin); > > and keep all the testing for a nu

logging an optional input location

There’s this repetition in context.cc: if (origin) { origin->warning (_f ("cannot find or create `%s' called `%s'", ly_symbol2string (n).c_str (), id)); } else { warning (_f ("cannot find or create `%s' called `%s'", ly_symb

Counters

While pondering how an “nth time only” feature might work, I considered what it might take to generalize the way the Mark engraver handles updating the rehearsal mark number and make it expressible in ly code instead. I have a working prototype that uses all the following features and I’m lookin

Re: Updating LSR snippets

On Mar 3, 2018, at 13:24, Thomas Morley wrote: > > Now that I had I look, let me ask why you propose the simplified snippet. > I can't see anything wrong with the current, doc-tagged, lsr-snippet, > though. If a user wants it this way, why not demonstrating it? The snippet has \mark 1 at measur

Updating LSR snippets

Do LSR editors lurk here? A little over a week ago, I used the LSR web interface to suggest simplifying the snippet “Forcing rehearsal marks to start from a given letter or number” to avoid repeating marks with the same sequence number within a score. This statement from the web page set my ex

Re: Stagnant regression test output

On Feb 16, 2018, at 07:49, Dan Eble wrote: > > At this point, I don’t have any reason to believe that there is a problem > affecting other people; however, I don’t have evidence to the contrary > either. It’s going to take me some time to get to the bottom of it. My > hyp

Re: LN_SRC_TO_BUILD not found

On Feb 22, 2018, at 06:23, Malte Meyn wrote: > 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

Re: Using a hash-table context property

On Feb 17, 2018, at 16:10, Dan Eble wrote: > On Feb 17, 2018, at 15:13, David Kastrup wrote: >> #(call-after-session >> (lambda () >> (hash-clear! default-fret-table) >> (hash-clear! chord-shape-table))) > > I see. Thanks again. That didn’t solve my prob

Re: Using a hash-table context property

On Feb 17, 2018, at 15:13, David Kastrup wrote: > > Well, your included links seem a bit optimistic. I doubt you reserved > the engraver-init.ly domain just for this request. Apple’s Mail is being too helpful. > #(call-after-session > (lambda () > (hash-clear! default-fret-table) > (hash-

Using a hash-table context property

After adding a property to define-context-properties.scm and initializing it in Score context in engraver-init.ly to a hash table created with alist->hash-table, my engraver is able to get the table and use it. My problem is that the entries the engraver adds persist

Stagnant regression test output

Last night, I noticed that the log output for my local regression tests did not hold the updated output I expected after test-clean, check. It still held old output that did not match what my rebuilt lilypond binary produced in a manual run on the test input. I ended up deleting my whole build

Re: Chromatic solfedge

On Feb 14, 2018, at 18:12, Simon Albrecht wrote: > >> And if so, would it be possible to extend this to a twelve-tone >> chromatic-solfege notation, avoiding accidental suffixes, such as: >> " d v r w m f x s y l z t” […] > So you could just define v as the equivalent of cis A glance at the le

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

On Feb 6, 2018, at 20:44, nine.fierce.ball...@gmail.com wrote: > > Reviewers: , > > Message: > I would be happy to hear suggestions for the name of this command. Esteemed LilyPond developers, Thank you for the voluminous feedback. It is encouraging to hear that a solution using unique IDs wou

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

On Feb 6, 2018, at 21:12, Simon Albrecht wrote: > > Brainstorming (NB, only brainstorming) on the name: > > Normal rehearsal marks refer to the beginning of a section, while these refer > to the end of a section, so an input command might be \endMark "D.S.". You > still have to complete it to

Re: 6 notes when the tempo is 5/4 ?

On Feb 3, 2018, at 19:20, Vivyan wrote: > > d4\rest > > \tuplet 3/2{ >\crossStaff { b } > } I believe that this B has a duration of 2/3 of a quarter note, therefore the final D begins with 1/3 of a beat remaining in the measure. — Dan _

Re: Is Patchy running?

On Feb 2, 2018, at 05:12, James Lowe wrote: > > Yes David is correct. I do run the patches manually. Others have been known > to also test patches ;) but you have to make sure that you do a full reg test > and full make doc which can take a long time on some machines, I had a > relatively powe

Is Patchy running?

Is Patchy running? I uploaded a few changes for review yesterday but I’ve seen no activity in the tickets since then. This is the first time I’ve used git-cl on macOS. It created code review and issue tracker tickets with no obvious complaint. https://sourceforge.net/p/testlilyissues/issues/5

Development on macOS

I’m starting to overcome inertia and get back into LilyPond development. I am hoping to keep the LilyPond source on a macOS host and build with LilyDev 4.1 in VirtualBox, accessing the source via a read-only shared folder. The main advantage is that I can exclude the gigantic VM disk image fro

Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by lilyp...@maltemeyn.de)

On Dec 28, 2017, at 05:49, lilyp...@maltemeyn.de wrote: > > Thank you for that hint. Indeed there is an unwanted interaction. The > following prints two maxima rests instead of one maxima + one longa + > one breve + one semibreve. I’ll have to work on this. > > { > \override MultiMeasureRest.exp

Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by lilyp...@maltemeyn.de)

On Dec 26, 2017, at 08:41, lemzw...@googlemail.com wrote: > > Could you provide an image? > > https://codereview.appspot.com/40043/ While you’re at it, could you add a regression test to your patch? (Or is there already a regression test that demonstrates this bug?) Regards, — Dan

Re: Issue #5246: Make empty scores abort engraving process (issue 332470043 by beauleetien...@gmail.com)

On Dec 21, 2017, at 23:06, beauleetien...@gmail.com wrote: > > @@ -110,8 +110,7 @@ LY_DEFINE (ly_interpret_music_expression, > "ly:interpret-music-expression", > > if (!iter->ok ()) > { > - warning (_ ("no music found in score")); > - /* todo: should throw exception. */ > +

Re: error en documentacion Lilypond en español

Dear translators, Gonzalo seems to be suggesting a correction to a musical term in the Spanish documentation. Regards, — Dan > On Sep 14, 2017, at 06:43, Gonzalo Pérez wrote: > > Hola. > > Mi nombre es Gonzalo, utilizo mucho el manual de Lilypond, me ha resultado > de gran utilidad. Escribo

Re: New repeat type

On Aug 30, 2017, at 16:00, Christopher Heckman wrote: > > As several people have pointed out, this is not a repeat … > Perhaps Dan meant the following? I meant what I wrote, but I take your point and Carl's. The disease is that Lilypond needs to see lyrics for multiple stanzas encoded as simu

Re: New repeat type

> On Aug 29, 2017, at 19:14, Carl Sorensen wrote: > > I wouldnt, because it is not a repeat. Not even as \alternative { \new Lyrics { \stanzaI } \new Lyrics { \stanzaII } } to be treated as simultaneous during engraving but unfolded before performing? — Dan

New repeat type

Consider: \repeat XX \A \alternative { \B \C } If “unfold” is effectively { { \A \B } { \A \C } } what type would you call this, if it existed? << { \A \B } { \A \C } >> — Dan ___ lilypond-devel mailing list lily

Re: What is void music?

On Aug 22, 2017, at 09:44, David Kastrup wrote: > >> I stumbled at this when I tried to define a predicate for void music, >> used (B) as an example, and found that it didn’t catch ##{#}. I’m not >> sure what to do. > > What is it that you are trying to predicate? The void flag is typically >

What is void music?

A. ly-syntax-constructors.scm has this. (define-public (void-music) (ly:set-origin! (make-music 'Music))) B. music-functions.scm has this: ... (make-music 'Music 'void #t) ... In lily-library.scm, the function collect-music-aux has the comment "void music is discarded”. It seems to

Re: Multi Measure Rest Interface

On Jul 20, 2017, at 17:20, Dave Higgins wrote: > > If R1*1 (or R1*3/4*1, etc.) could add the 1, that'd make a few less key > strokes over time. Like this? \version "2.19.58" % what I tested with \new Staff \with { restNumberThreshold = 0 } { R1*1 } Regards, — Dan ___

Re: Any objections to branching off a stable branch for 2.20?

> On Jul 19, 2017, at 15:19, David Kastrup wrote: > > Paul mailto:p...@paulwmorris.com>> writes: > >> It's usually `a = b` or `\a b` but not `\a = b` or `\a b = c`. > > You can only use markup functions when refered to in markup mode, so it > makes sense to me to define them in markup mode. T

Re: [partcombine] honouring Voice context name

> On Jun 7, 2017, at 19:48, Carl Sorensen wrote: > > On 6/7/17 5:30 PM, "Kieren MacMillan" > wrote: > >>> Could it not leave the parts where they are (continuous parts in >>> exactly one voice context per part) and change their context properties >>> instead? >> >> Not sure I quite understand

Re: [partcombine] honouring Voice context name

> On Jun 7, 2017, at 09:34, Kieren MacMillan > wrote: > > As a first step, I would offer that we should figure out how (if?) the "one" > context can be funnelled seamlessly into the "shared" and "solo" contexts — > as I see it, that's the main problem with lyrics getting disconnected (etc.).

Re: [partcombine] honouring Voice context name

On Jun 6, 2017, at 15:30, Kieren MacMillan wrote: > >> I guess what you are saying is that if the parts to be combined are each >> context-specced-music, use those contexts. > > Exactly. The part combiner can also route events to “shared”, “solo”, and “null” contexts. If you took the step yo

Re: pdf changes every few compilations, although changing nothing

On Apr 10, 2017, at 08:43, David Nalesnik wrote: > > It's strange -- it seems that the value of > ly:tuplet-bracket::calc-x-offset is used sometimes regardless of the > ly:grob-set-property! and there's no predictability to it. > > No idea :( Maybe there’s a race against the garbage collector.

Text on broken lyric extenders

Here’s a proof of concept that I don’t currently have time to develop. I think it would be nice if ly::lyric-extender::print worked this way by default, so that a user only had to set LyricExtender.text to get this behavior. Regards, — Dan \version "2.19.54" %% Print a lyric extender with te

Re: Lily version operators documentation

On Feb 14, 2017, at 04:23 , Urs Liska wrote: > introduces the procedures > > - lilypond>? [etc.] > comparing a given version to the one currently compiling the document. Adding “version” to the name would be clearer. — Dan ___ lilypond-devel mailin

Re: music function to be included somewhere in scm/*

On Dec 20, 2016, at 08:23 , Werner LEMBERG wrote: > Sorry, but I strongly dislike collapsing two properties into one, even > if the values for the two properties are always the same. So please > use `collapse-length' (`suppress-threshold', etc.) and > `forced-length'. This is wise. — Dan

Re: Unit testing

On Nov 1, 2016, at 03:55 , Chris Yate wrote: > > It's probably pedantry, but "unit tests" by most good definitions ought not > to touch stuff like network, threads, filesystems and databases. If we're > testing the graphic output it's too high level. Agreed. > Unit tests would directly examine

Re: Changing voice order...

On Oct 28, 2016, at 05:01 , David Kastrup wrote: > > Well, there is still the question of what 1/2/3 should _mean_. > Currently they are connected with \voiceOne, \voiceTwo, > \voiceThree... and the meaning of those is "topmost", "lowest", "below > topmost" ... > > I find this both disturbing an

Re: Changing voice order...

On Oct 27, 2016, at 09:54 , David Kastrup wrote: > > << \context Voice = "1" \with \voiceThree ... > \context Voice = "2" \with \voiceOne ... > \context Voice = "3" \with \voiceTwo ... > \context Voice = "4" \with \voiceFour ... I’m not sure whether this thread has progressed beyond the ne

Re: Instrument equalization

> On Aug 29, 2016, at 03:42 , David Kastrup wrote: > > Dan Eble writes: > >> the moment, I am inclined to defeat the equalizer in my Lilypond >> scores so that all instruments use the same mapping of dynamic to >> velocity, and account for the relativ

Instrument equalization

A request from a performer to receive MP3 rather than MIDI has triggered an excursion into soundfont design and led me to question Lilypond’s default instrument-equalizer settings. ("flute" . (0 . 0.7)) ("oboe" . (0 . 0.7)) ("clarinet" . (0 . 0.7)) ("bassoon"

Re: Gub failure

> On Jul 26, 2016, at 07:57 , David Kastrup wrote: > > Dan Eble writes: > >> In LilyDev 3, I’ve tried “sudo apt-get install texinfo” and it tells >> me “texinfo is already the newest version.” Is there any easier path >> forward than switching to a new VM

Re: Gub failure

On Jul 24, 2016, at 13:32 , David Kastrup wrote: > > Note that even "make" builds a basic non-image version of the Info > files, and of course with a non-image version, the difference is quite > noticeable. > > At any rate, if we were to update Texinfo, it would likely make sense to > take the n

Re: [testlilyissues:issues] #4048 Is Dynamic_performer’s understanding of (de)crescendo too limited?

> This is unlikely to happen this week for a few reasons beyond my control. > Sorry to anyone who is inconvenienced. > Pushed to staging as the following commits. I've not been able to log in to Sourceforge to update the status of the ticket. Author: Dan Eble Date: Mon Jul 4

Re: PATCHES: Countdown for July 14th.

James Lowe gnu.org> writes: > On 18/07/16 19:23, Dan Eble wrote: > > James gnu.org> writes: > > > >> Push: > > [...] > >> 4048 Is Dynamic_performer’s understanding of (de)crescendo too limited? > >> - Dan Eble > >>

Re: PATCHES: Countdown for July 14th.

James gnu.org> writes: > Push: [...] > 4048 Is Dynamic_performer’s understanding of (de)crescendo too limited? > - Dan Eble > https://sourceforge.net/p/testlilyissues/issues/4048 > http://codereview.appspot.com/302910043 This is unlikely to happen this week for a few reasons

Re: Doc: Add a section about handling MIDI dynamics with multiple voices (issue 302930043 by ht.lilypond.developm...@gmail.com)

> I suspect all of this behavior is due to the Staff_performer logic, > which tries to distribute notes and dynamics into separate classes by > the names of their associated Voices - maybe this should be done using > some other criterion (such as an internal Voice ID, unique to each Voice > instanc

Reitveld email

I didn’t receive any email about a comment made two days ago on one of my patches (https://codereview.appspot.com/302910043 ). I don’t see any options in the Reitveld settings related to notifying me about feedback by email. Am I blind? TIA. — Dan

Re: PATCHES: Countdown for July 7th.

> 4048 Is Dynamic_performer’s understanding of (de)crescendo too limited? - Dan > Eble > https://sourceforge.net/p/testlilyissues/issues/4048 > http://codereview.appspot.com/302910043 This should have been in “review.” I’ve updated the ti

Re: [GSoC] spanners project update

> On Jun 24, 2016, at 07:41 , Nathan Chou wrote: > > Hello, > > spanners with an id are handled as potentially being cross-voice. Each > engraver maintains a static list member (so it is shared between all > instances of an engraver) of named spanners and the voice each spanner > currently belon

Re: Protected_scm warning: returning reference to temporary

On Jun 13, 2016, at 18:37 , David Kastrup wrote: > > Anyway, I'll push a fix. Can you check again in 5 minutes? No more warnings from protected-scm. Thanks, — Dan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman

<    1   2   3   4   5   6   7   8   9   >