Re: Backporting for 2.14.2

El 28/06/2011 20:52, "Carl Sorensen" escribió: > > On 6/28/11 12:30 PM, "Federico Bruni" wrote: > > > My question is here: > > http://lilypond-translations.3384276.n2.nabble.com/snippets-in-LM-td6518251.ht > > ml > > > Looking at this more closely, I think the instructions (in CG 5.8.2) say > tha

SustainPedal: to-barline setting?

Hi, I'm typesetting a piano score where the pedal is mainly \sustainOn at the beginning of the measure and \sustainOff at the very end of the measure (just before the bar line) and so on. I did not find a proper way to print the \sustainOff at the very end of the measure (just before the ba

Re: does anybody care about LSR?

On Tue, Jun 28, 2011 at 5:48 PM, Graham Percival wrote: > As far as I'm concerned, no I don't care about LSR; Shocker. What else is new? :-) > the people who > wanted it in the first place aren't maintaining it; we haven't had > a flood of users volunteering to take care of it.  This experiment

DynamicTextSpanner inside Dynamics context are shifted due to pedal

%% DynamicTextSpanner inside a Dynamics context are shifted to the left %% if there is a Pedal inside another Dynamics context. %% That leads to really poor output of the DynamicTextSpanner, which %% are shifted left (compared to when they are well aligned without the %% pedal) and so colliding wit

Re: how to create baroque ornaments

On Tue, Jun 28, 2011 at 11:39 AM, Reinhold Kainhofer wrote: > It seems we have so many really great third-party packages (Valentin's, > Nicolas', mine, Gilles' \extractMusic, etc... probably I'm not even aware of > some other great ones). I think we should think about a general way to promote > an

Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

Reviewers: , Message: Cheers, MS Description: Fixes error for tuplet bracket direction calculation when tuplets contain rests. Please review this at http://codereview.appspot.com/4668045/ Affected files: M lily/tuplet-bracket.cc Index: lily/tuplet-bracket.cc diff --git a/lily/tuplet-bracke

RE: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

Mike, From: lilypond-devel-bounces+james.lowe=datacore@gnu.org [lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of mts...@gmail.com [mts...@gmail.com] Sent: 29 June 2011 12:25 To: mts...@gmail.com Cc: re...@codereview.appspotmail.com;

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

test missing. On Wed, Jun 29, 2011 at 8:25 AM, wrote: > Reviewers: , > > Message: > Cheers, > MS > > Description: > Fixes error for tuplet bracket direction calculation when tuplets > contain rests. > > Please review this at http://codereview.appspot.com/4668045/ > > Affected files: >  M lily/tu

Re: does anybody care about LSR?

Am Dienstag, 28. Juni 2011, 19:16:36 schrieb Graham Percival: > > LSR is a place to put snippets that some people think are useful, without > > the filtering of any "expert". > > Ideally so. In practice, it seems like only "experts" (or at > least, developers and contributors) are doing anything

Re: does anybody care about LSR?

Am Dienstag, 28. Juni 2011, 17:48:24 schrieb Graham Percival: > I was discussing LSR with Phil, and it occurred to me that I > should raise the question here. What do we want from LSR? > > As far as I'm concerned, no I don't care about LSR; the people who > wanted it in the first place aren't mai

Re: does anybody care about LSR?

Am Mittwoch, 29. Juni 2011, 10:30:49 schrieb Valentin Villenave: > I must disagree. People have posted tons of interesting snippets > there, ranging from the basic "how to display a whole note" to > advanced tricks used by Eluze, Gilles Thibaut, Jay Anderson&al. (there > are even quite advanced sni

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

Pass all reg tests. However, I note that in the tuplet_rest.ly file i) the tuplet is above the staff for the 3 x crotchet/quarter rest measure where it was below previously (i.e r4 r r) ii) the last 2 measures where the last note is a stemUp instead of stemDown but has a rest in either first qu

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

On Wed, Jun 29, 2011 at 12:35:35PM +, James Lowe wrote: > > Fixes error for tuplet bracket direction calculation when tuplets > > contain rests. > > > > Please review this at http://codereview.appspot.com/4668045/ > Is there a tracker issue for this? No, so James please make one. http://lily

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

Ah, the old coup de regtest. Gets me every time... New patch set uploaded. Cheers, MS http://codereview.appspot.com/4668045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Fixes issue 39 by raising stems (issue3934041)

On 2011/06/25 18:58:15, Keith wrote: On Sat, 25 Jun 2011 03:53:40 -0700, wrote: > Keith: are you still interested in tackling this problem? I know there > have been some changes in note-collision.cc, so I'll likely scrap this > patch and start from scratch, I

Re: SustainPedal: to-barline setting?

- Original Message - From: "Xavier Scheuer" To: "lilypond-user" ; "lilypond-devel" Sent: Wednesday, June 29, 2011 9:24 AM Subject: SustainPedal: to-barline setting? Hi, I'm typesetting a piano score where the pedal is mainly \sustainOn at the beginning of the measure and \sustai

Re: does anybody care about LSR?

Am Mittwoch, 29. Juni 2011, 17:33:33 schrieb Graham Percival: > I'd like to be able to tell "expert users" that the easiest way > for them improve the documentation is by adding snippets, and that > these would be added to our docs in a timely fashion. But if > we're looking at an average of 1 imp

Re: does anybody care about LSR?

On Wed, Jun 29, 2011 at 02:56:28PM +0200, Reinhold Kainhofer wrote: > Am Dienstag, 28. Juni 2011, 19:16:36 schrieb Graham Percival: > > Ideally so. In practice, it seems like only "experts" (or at > > least, developers and contributors) are doing anything to maintain > > it. > > So, where's the p

Re: does anybody care about LSR?

On Wed, Jun 29, 2011 at 04:39:39PM +0100, Phil Holmes wrote: > I've already told Graham I'm happy to maintain it from an authoriser > point of view. I'll also be wanting you to do CG 7.4 LSR to git, once you have git access. Or maybe even before, since you could send a patch to James for pushing.

Re: does anybody care about LSR?

- Original Message - From: "Graham Percival" To: "Carl Sorensen" So if Phil is willing to take it over, whatever he wants to do is fine with me. That sounds like you're agreeing with my main suggestion: dump it on Phil. :) Cheers, - Graham I've already told Graham I'm happy t

Re: does anybody care about LSR?

On Wed, Jun 29, 2011 at 10:30:49AM +0200, Valentin Villenave wrote: > On Tue, Jun 28, 2011 at 5:48 PM, Graham Percival > wrote: > > I'm suggesting that we just dump the whole thing on Phil.  He can > > choose how picky (or not) to be about explanations, indentation, > > looking for duplicates, etc

Re: SustainPedal: to-barline setting?

Hi Phil (and Xavier), > This is issue http://code.google.com/p/lilypond/issues/detail?id=1128 Would be nice for this to be fixed — I can offer C$25 bounty on a fix. > I now work round it with an extra voice with mainly spacer rests, but adjust > the size of the spacers when I need pedal-on/peda

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

On Jun 29, 2011, at 3:25 PM, pkx1...@gmail.com wrote: > Pass all reg tests. > > However, I note that in the tuplet_rest.ly file > > i) the tuplet is above the staff for the 3 x crotchet/quarter rest > measure where it was below previously (i.e r4 r r) > > ii) the last 2 measures where the last

Re: does anybody care about LSR?

On Wed, Jun 29, 2011 at 6:03 PM, Reinhold Kainhofer wrote: > Okay, you are simply seeing LSR as an input pipe for doc material. I see it as > a very useful, separate entity, which provides a quick, searchable FAQ, which > is able to display just the requested information in an easy way. That's ex

Re: does anybody care about LSR?

Am Mittwoch 29 Juni 2011, 23:11:33 schrieben Sie: 1> Phil, let's work this way: everytime you're in doubt (or on holiday) > about anything lsr-related, or every time you approve a docs-tagged > snippet, please give me a ping so I don't forget to push an lsr-update > onto the git master repo. > > I

Need some input on a new patch for glissando-friendly stems

Hey all, I'm getting a patch together to implement glissandi stem (stems that link up to a glissando to indicate the glissando's duration to avoid awkwardness with ties - comes up all the time in Xenakis). I have the C++ code working, but I'm looking for suggestions on the input syntax. Curren

Re: does anybody care about LSR?

Graham Percival-3 wrote: > > I was discussing LSR with Phil, and it occurred to me that I > should raise the question here. What do we want from LSR? > > As far as I'm concerned, no I don't care about LSR; the people who > wanted it in the first place aren't maintaining it; we haven't had > a

Re: GOP-PROP 3: C++ formatting

On Mon, Jun 27, 2011 at 10:45:09PM -0700, Keith OHara wrote: > Some indentation is off because fix-astyle-fiddle removes spaces > after indentation. Really? I thought the two post-processing rules in fix-astyle-fiddle.py improved the formatting. If they don't, we can certainly remove them. > (f

GOP-PROP 4: lessons from 2.14

http://lilypond.org/~graham/gop/gop_4.html ** Proposal summary What went well, what went badly? This is a discussion only; it will be summarized, and we will refer back to it in future policy decisions, but no new policies will be decided in this round. We’ll have (at least) two sections: one fo

GOP-PROP 3: C++ formatting (update)

This is an update, rather than a "probable decision". I don't think we're close enough to have a real proposal. http://lilypond.org/~graham/gop/gop_3.html At the moment I'm leaning towards using astyle+postprocessing. The script in question is here: http://git.savannah.gnu.org/gitweb/?p=lilypond

Re: GOP-PROP 3: C++ formatting (update)

Graham Percival percival-music.ca> writes: > > At the moment I'm leaning towards using astyle+postprocessing. > The script in question is here: Don't post-process, or you mis-align the indentation that astyle did. Pre-filtering works well, assuming we drop the corresponding astyle options: #

Re: GOP-PROP 3: C++ formatting (update)

Graham Percival percival-music.ca> writes: > At the moment I'm leaning towards using astyle+postprocessing. > By coincidence, I just finished looking over astyle alone. The options you first proposed aren't enough for me, because I can't remember how to gnu-space things like me->origin ()

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

On 2011/06/29 13:20:57, graham_percival-music.ca wrote: On Wed, Jun 29, 2011 at 12:35:35PM +, James Lowe wrote: > Is there a tracker issue for this? No, so James please make one. http://code.google.com/p/lilypond/issues/detail?id=1720 Hope this is correct :) James http://codereview.ap

Re: Fixes error for tuplet bracket direction calculation when tuplets contain rests. (issue4668045)

On 2011/06/29 16:32:33, mike_apollinemike.com wrote: On Jun 29, 2011, at 3:25 PM, mailto:pkx1...@gmail.com wrote: Currently, Lilypond does not factor in note position w/ respect to the staff symbol in order to place the tuplet bracket. Nor did my patch...until I read your e-mail. What y

Re: SustainPedal: to-barline setting?

On Wed 29 Jun 2011, 13:23 Kieren MacMillan wrote: > Hi Phil (and Xavier), > > > This is issue http://code.google.com/p/lilypond/issues/detail?id=1128 > > Would be nice for this to be fixed — I can offer C$25 bounty on a fix. Thank you! -- your offer has beed added to the tracker,) -- Dmytro O

Re: GOP-PROP 3: C++ formatting (update)

On 6/29/11 6:01 PM, "Keith OHara" wrote: > Graham Percival percival-music.ca> writes: > >> At the moment I'm leaning towards using astyle+postprocessing. >> > > By coincidence, I just finished looking over astyle alone. > > The options you first proposed aren't enough for me, because I can't

Re: GOP-PROP 4: lessons from 2.14

Graham Percival writes: > http://lilypond.org/~graham/gop/gop_4.html [...] Could I please ask, for my sanity, that we use ISO 8601 dates? Living and working in the USA, I always get mentally confused between DD-MM- and MM-DD- (either way). To help out, I will convert the dates in your

48 Hour Co8untdown for New Breve Rest

23:00 MST Friday July 1 Issue 1705: New breve rest with ledger lines http://codereview.appspot.com/4650052/ Issue 1711: Pitch bend tuning adjustments. http://codereview.appspot.com/4654063/ Issue 1710: rearrange flag definitions in feta-flags.mf http://codereview.appspot.com/4625067 chee

Re: GOP-PROP 3: C++ formatting (update)

On Wed, 29 Jun 2011 21:05:51 -0700, Carl Sorensen wrote: On 6/29/11 6:01 PM, "Keith OHara" wrote: Graham Percival percival-music.ca> writes: At the moment I'm leaning towards using astyle+postprocessing. padding that can be helpful - && ((d == LEFT && !line_->get_bound (LEFT)) -