Re: [GSoC] spanners project update

Am 01.07.2016 um 09:28 schrieb Jan-Peter Voigt: >> Hm. If this is a limitation required by the implementation then it's >> acceptable. But from a user perspective I would be very surprised if an >> ID isn't recognized without an explicitly named context around it. Isn't >> that the (one) idea of

Re: [GSoC] spanners project update

Am 01.07.2016 um 09:01 schrieb Nathan Chou: > Thanks David and Urs for replying. > >>> There is a detail I would like to clarify. David suggested allowing \= >>> to optionally specify the parent context in which a cross-voice >>> spanner's information is shared (although I am not sure how that

Re: [GSoC] spanners project update

Am 30.06.2016 um 14:47 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 30.06.2016 um 14:37 schrieb David Kastrup: >> >>> How does that differ from symbols? >> Ah, not in the Scheme domain, of course. But you can't *enter* them a

Re: [GSoC] spanners project update

Am 30.06.2016 um 14:37 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 30.06.2016 um 14:05 schrieb David Kastrup: >>> Urs Liska <u...@openlilylib.org> writes: >>> >>>> Am 30.06.2016 um 11:52 schrieb David Kastrup: &

Re: [GSoC] spanners project update

Am 30.06.2016 um 14:05 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 30.06.2016 um 11:52 schrieb David Kastrup: >>>> There is a detail I would like to clarify. David suggested allowing \= >>>>> to optionally spec

Re: [GSoC] spanners project update

Am 30.06.2016 um 11:52 schrieb David Kastrup: >> There is a detail I would like to clarify. David suggested allowing \= >> > to optionally specify the parent context in which a cross-voice >> > spanner's information is shared (although I am not sure how that would >> > be done with a key-list,

Re: Scheme question

Am 13. Juni 2016 19:51:48 MESZ, schrieb Phil Holmes : >Can anyone explain why the f in the attached code is 2 octaves above >where >I would expect them? Where *do* you expect it? > >testy = #(define-music-function (note) > (ly:music?) >#{ > \tag #'a { #note } > \tag

Re: Patch

HTH Urs > > > > Thanks! > > > > --Steven > > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel > -- Urs Liska www.openlilylib.org _

Re: Rewriting the Translator definition framework

Am 23.04.2016 um 07:09 schrieb Paul Morris: > (Also, while I’m at it, your recent dotted list work, allowing "violin.1” > etc, is also really nice.) Oh, I seem to have missed this, but that's great. Finally we can write indexed parts/variables! Thanks for adding this, David. Best Urs

Re: Newbie contributor seeking a mentor

Am 15.04.2016 um 04:25 schrieb Bryan Jacobowitz: > Hi, I'm interested in contributing to Lilypond but I could use some > direction in starting out. How can I get in touch with a mentor? > > I have some C++ and Python experience, and I've been using Lilypond off and > on for about 4 years now. So

Re: Current status of Guile 2 for lilypond

Am 12.04.2016 um 09:20 schrieb Thomas Morley: > 2016-04-12 8:06 GMT+02:00 Andrew Bernard : >> What is the current status wirh respect to porting lilypond to use guile 2.*? >> >> I am not seeking long disquisition on all the issues with guile 2, but >> rather wondering

Re: Pushing to staging from patches vs branches

Am 11. April 2016 12:16:50 MESZ, schrieb Federico Bruni : >Il giorno dom 10 apr 2016 alle 21:50, Paul Morris > ha scritto: >> Hi all, >> >> In CG 3.4.10 “Pushing to staging” it describes ways to push to >> staging from a patch file or from a branch:

Re: Pushing to staging from patches vs branches

If I'm not misunderstanding you you should rebase your branch on top of staging. Then you don't have a merge commit. HTH Urs Am 10. April 2016 21:50:59 MESZ, schrieb Paul Morris : >Hi all, > >In CG 3.4.10 “Pushing to staging” it describes ways to push to staging >from a

Re: Code examples in docs

Am 09.04.2016 um 15:27 schrieb Phil Holmes: > - Original Message - From: "Urs Liska" <u...@openlilylib.org> > To: <lilypond-devel@gnu.org> > Sent: Thursday, April 07, 2016 7:11 AM > Subject: Re: Code examples in docs > > >> >> >

Re: Code examples in docs

Weitergeleitete Nachricht Betreff:Re: Code examples in docs Datum: Sat, 9 Apr 2016 12:56:12 +0100 Von:James <p...@gnu.org> An: Urs Liska <u...@openlilylib.org> Hello Urs On 09/04/16 12:27, Urs Liska wrote: > > Am 9. April 2016 12:56:42 M

Re: Code examples in docs

Am 07.04.2016 um 11:11 schrieb Carl Sorensen: > On 4/7/16 12:11 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of Urs Liska" <lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of > u...@openlilylib.org> wrote: > >> However, w

Re: Code examples in docs

Am 07.04.2016 um 12:11 schrieb David Kastrup: > David Kastrup writes: > >> Carl Sorensen writes: >> >>> What about if you delete python/out and redo make doc? >>> >>> Just wondering if there's something wrong with the build script that >>> python/out isn't

Re: Code examples in docs

Am 07.04.2016 um 08:03 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Hm, I'm puzzled. >> >> I must say that this file and particularly >> BookHTMLOutputFormat.snippet_output() looks like it's exactly the code >> I'm looki

Re: Code examples in docs

Am 07.04.2016 um 07:54 schrieb Urs Liska: > > Am 07.04.2016 um 07:50 schrieb Noeck: >> Hi Urs, >> >> a very uneducated guess: Could it be that the html pages are only >> generated if the input has changed and as you change the generating code >> and not the

Re: Code examples in docs

Am 07.04.2016 um 07:50 schrieb Noeck: > Hi Urs, > > a very uneducated guess: Could it be that the html pages are only > generated if the input has changed and as you change the generating code > and not the doc-input, the generation is skipped? It is still strange > that it works if you empty

Re: Code examples in docs

Am 06.04.2016 um 09:37 schrieb Urs Liska: > Hi Carl, > > Am 06.04.2016 um 02:09 schrieb Carl Sorensen: >> On 4/5/16 5:09 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on >> behalf of Urs Liska" <lilypond-devel-bounces+c_sorensen=byu@gnu.org on

Re: Code examples in docs

Hi Carl, Am 06.04.2016 um 02:09 schrieb Carl Sorensen: > On 4/5/16 5:09 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of Urs Liska" <lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of u...@openlilylib.org> wrote: > >> Hi, >&g

Code examples in docs

Hi, can someone tell me where I should look for code that generates code examples in the HTML docs? Thanks Urs -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: building from source

invariably broke the site and required hours or days of >> fixing things. LilyDev in a VirtualBox VM always works, and works easily. >> >> I would really recommend using LilyDev in a VM. >> >> Carl >> > > > ___ > lilypond-devel mailing list > lilypond-devel@g

GSoC next steps

of these two projects can be done. Nathan Chou has applied for the "Let Spanners Cross Voices" project, which would be mentored by Jan-Peter Voigt. Jeffery Shivers has applied for "ScholarLY", which I would mentor. Best Urs -- Urs Liska www.openlilylib.org

Re: redundant hostnames and obsolete urchin.js

Am 23. März 2016 15:06:59 MEZ, schrieb Federico Bruni : >I've started looking at Analytics, which gives two warnings: > >1. We are using the old script urchin.js, which was replaced by >analytics.js > >$ git grep urchin.js

Re: Lilypond issue tracker account request

Am 22.03.2016 um 15:32 schrieb Karl O. Pinc: >>> I'm thinking about someday contributing to lilypond >> Great! The first step is to post specific issues that >> you have identified to the bug list: >> http://lists.gnu.org/archive/html/bug-lilypond/ >> for discussion and to have an Issue

Re: Lilypond issue tracker account request

Hi Karl (and Phil), Am 22.03.2016 um 09:25 schrieb Phil Holmes: > I believe you can contribute to the tracker without an account: it's > just that the contributions require moderation. Could I suggest you > start like that and see how you progress? I think Karl talks about uploading patches

Re: GSoC mentors once more

Just a heads-up for us to know: The student application window has now opened, but we need to list our mentors only until the window closes again, that is until March 25. Urs Am 14.03.2016 um 01:08 schrieb Urs Liska: > Given the advent of a fifth potential applicant I find it inaccepta

Re: GSoC mentors once more

mong developers, and Google explicitly endorses to have code review shared by the devs and not only been done by the mentor. So depending on the project and the student it *may* be a rather easy task. Or not. Urs > > Cheers > Jan-Peter > > Am 14. März 2016 01:08:09 MEZ, schrieb Urs L

GSoC mentors once more

Given the advent of a fifth potential applicant I find it inacceptable that we don't seem to make any progress in raising our mentor number beyond two. Is it really true that I am the only one pushing this? Urs -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Going from XML to (make-sequential-music)

Hi devs, this question may seem somewhat far-fetched and maybe even out-of-the-blue, but it actually has a concrete context (if you don't know what I mean you may ask me off-list). Consider the scenario that I have a specific XML format where a number of external formats can be converted to

Re: GSoC applications and slots

Am 07.03.2016 um 10:49 schrieb Urs Liska: > > Am 07.03.2016 um 09:58 schrieb David Kastrup: >> Urs Liska <u...@openlilylib.org> writes: >> >>> Am 07.03.2016 um 09:26 schrieb David Kastrup: >>>> Urs Liska <u...@openlilylib.org> writes: >>

"Spanner-context" GSoC project, mentor needed

Hi devs, we have a potential student looking for a GSoC project (http://lists.gnu.org/archive/html/lilypond-devel/2016-03/msg6.html and following messages). He has expressed interest in the "Allow spanners to cross voices" project where I am listed as potential/secondary mentor. However, I

Re: Changing Staff Size Without Messing Up Fonts

but unfortunately only after other things which I don't really have enough time for either ... Best Urs > Best, Simon > > _______ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Urs Liska www.openlil

Re: GSoC applications and slots

Am 07.03.2016 um 09:58 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 07.03.2016 um 09:26 schrieb David Kastrup: >>> Urs Liska <u...@openlilylib.org> writes: >>> >>>> Hi guys, >>>> >&g

Re: GSoC applications and slots

Am 07.03.2016 um 09:26 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Hi guys, >> >> it seems there's the chance this year that we end up with more GSoC >> applications than available slots. Right now there are four people >&g

GSoC applications and slots

Hi guys, it seems there's the chance this year that we end up with more GSoC applications than available slots. Right now there are four people having expressed interest in it, and my impression so far is that the majority (or even all) may go the way through to an application. That raises the

Re: starting to contribute (GSoC)

Am 07.03.2016 um 05:48 schrieb Carl Sorensen: > On 3/6/16 9:33 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of Nathan Chou" on behalf of starry...@gmail.com> wrote: > > ... > >> Also regarding GSoC, currently allowing

Re: GSoC - ScholarLY

Hi Jeffery, Am 03.03.2016 um 06:03 schrieb jeffery shivers: > Dear LilyPond team, > > I'd like to apply for GSoC to contribute to ScholarLY as > a student with Urs Liska. This is great news! > > I've been a user of LilyPond and LaTeX for a while now, > and am intri

Re: Verifying issues

Am 02.03.2016 um 23:52 schrieb Simon Albrecht: > Hello, > > I noticed that there have been many ‘Issues to verify’ around, so I > started to catch up with these. Now the question is: Shouldn’t we only > mark issues as verified, when the change is already included in an > official release? > For

Re: starting to contribute (GSoC)

Hello Nathan, welcome to the lilypond-devel list. I hope we'll find a way for you to join us sustainably :-) Your post is not fully clear, though (at least to me), as I think it gives too little information to estimate your experience (combined with the willingness to learn). If you want to go

Re: Lose the tagline (permanently)

Hi Abraham, Am 23.02.2016 um 13:56 schrieb Abraham Lee: > Dear Dev team, > > ... > > I'm not sure what prompted > Han-wen or Jan or whoever to set a default value to it, but I wonder if > it's time for it to go? > > Just some thoughts. I love the quality of LP scores. Removing the default >

Re: Keep parsed document in memory

Hi Sharon, Am 22.02.2016 um 20:22 schrieb Sharon Rosner: >> I worked on a large score with about 100 A3 pages with 13 point staff >> size (~ 50 minutes of huge orchestra). >> >> Compiling the full score using manual breaks took around 7 minutes, with >> the console output seemingly indicating the

Re: Keep parsed document in memory

Am 22.02.2016 um 12:27 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> So, let's assume we already had implemented a server daemon mode for >> LilyPond. >> Would it be possible to make that daemon keep a representation of the >> *

Keep parsed document in memory (was: LilyPond as a service)

Hi David, thank you for your explanation, which is the base for a (presumably more complicated) follow-up question. Am 17.02.2016 um 23:31 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> I know this has been discussed in various flavors over the ye

GSoC invitations?

Hi all, now that our modified GSoC page is online we should think about spreading the word. Of course the mentoring project applications are not done yet, but I think we should act as if it were clear that we can offer that project. So, as the student application window starts March 14th I think

Re: Fwd: MusicXML

Am 18.02.2016 um 09:44 schrieb James Lowe: > I hope this isn't off-topic but could we get together with the > Philomelos people? > > https://github.com/Philomelos/lilypond-musicxml2ly-dev > > I am not sure of the motivation to fork, but if it was just because no > one was working on MusicXML and

Re: Fwd: MusicXML

Hi David, nice to read that. I think coming to GSoC with an idea is more important than the listed mentor availability. Continuing on the Scheme/XML track would be very rewarding. However, for some reasons I'd try to go into a more generic direction. This could be very suitable for

Re: LilyPond as a service

I'm sorry but I don't get this. Urs Am 17.02.2016 um 22:48 schrieb Abraham Lee: > This sounds a lot like lilybin.com <http://lilybin.com>... > > - Abraham > > On Wed, Feb 17, 2016 at 2:45 PM, Urs Liska <u...@openlilylib.org > <mailto:u...@openlilylib.org>>

LilyPond as a service

I know this has been discussed in various flavors over the years, but I need to raise the issue once more. Please note that this actually encloses two questions. Would it be possible to make LilyPond work in a server mode where the whole Guile environment is loaded only once and the running

Re: When to start patch review

Am 17.02.2016 um 17:47 schrieb Simon Albrecht: >> Waiting for a patch like that to pass before review is pointless if >> there is going to be a reluctance or even refusal to allow it to make >> it to master in the end. >> >> However, is there a particular reason for this question? > > No, just

Re: PATCHES: Countdown for February 15th

Am 13.02.2016 um 14:16 schrieb James Lowe: > Urs, > > On 12/02/16 11:47, Urs Liska wrote: >> >> Am 12. Februar 2016 12:41:30 MEZ, schrieb James <p...@gnu.org>: >>> Hello, >>> >>> Here is the current patch countdown list. The next countdown wi

Re: PATCHES: Countdown for February 15th

Am 12. Februar 2016 12:41:30 MEZ, schrieb James <p...@gnu.org>: >Hello, > >Here is the current patch countdown list. The next countdown will be on >February 15th. > ... > > >4763 Web: Review GSoC page - Urs Liska >https://sourceforge.net/p

Re: Web: Review GSoC page (issue 285400043 by g...@ursliska.de)

Am 8. Februar 2016 15:35:33 MEZ, schrieb paulwmor...@gmail.com: . > >> Hm, my intention was to draw the attention to the fact that this >project relates >> to actual engraving quality. But I've taken your suggestion. > >Hmm... that's a good idea. Maybe add this to the title? "Improve

Re: Mentors needed for GSoC suggestions

Am 03.02.2016 um 12:14 schrieb Federico Bruni: > Hi Urs > > I jump in late to ask if the transition to texi2any might be added to > the list. > It might not be a sexy project but it's very needed and we all know > how much the documentation is important for LilyPond. > > If Graham confirms his

Re: GSoC 2016

Hi Paul, Am 27.01.2016 um 02:37 schrieb Paul Morris: > While we’re at it, one thing I’ve thought about is simplifying vertical > spacing changes. Basically something like this[1] but possibly integrated > into LilyPond. One idea is that alongside padding, minimum-distance, and >

Re: Mentors needed for GSoC suggestions

d and Guile 2.0 interoperability? Like with mentors > from both > projects. I assume that would be too difficult a task at this point, at > least I think > that was the thinking last year. > Would be great to have ... Urs > -- Urs Liska www.openlilylib.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Mentors needed for GSoC suggestions

Hi developers, this is pretty urgent, and I start a new thread for all those who may not have followed up on http://lists.gnu.org/archive/html/lilypond-devel/2016-01/msg00139.html. We want to review our suggestions for Google Summer of Code projects. But it seems although the projects listed on

Mentor availability (was: GSoC 2016)

I wouldn't expect it from a novice. Of course, during the bonding period I might change my expectations. " Am 21.01.2016 um 17:02 schrieb Urs Liska: > Starting the next round somewhat earlier ... > > Surprisingly there also will be a Google Summer of Code 2016, and I > think

Re: GSoC 2016 - GNU website listing

Am 27.01.2016 um 21:02 schrieb Paul Morris: > So students can find us as one of the GNU projects, we should get LilyPond > listed on the GNU GSoC suggestions page. Here’s the one for last summer: > http://www.gnu.org/software/soc-projects/ideas-2015.html > > Seems we should just have a

Re: GSoC 2016

Am 26.01.2016 um 10:21 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Would it be an acceptable/interesting project to bring the ScholarLY >> library to a finished state and (optionally) integrate it with >> LilyPond? > Personally I d

Re: GSoC 2016

Am 27. Januar 2016 02:37:17 MEZ, schrieb Paul Morris : >> On Jan 26, 2016, at 5:24 AM, David Kastrup wrote: >> >>> So my question could be rephrased: Would it be acceptable to suggest >a >>> GSoC project if such an external library is *not* going to be

Re: Add ly:one-page-breaking (issue 288910043 by paulwmor...@gmail.com)

Am 27. Januar 2016 05:34:46 MEZ, schrieb paulwmor...@gmail.com: >Now that ly:one-line-auto-height is in master, this patch set updates >the docs so it and ly:one-page-breaking are both present and accounted >for. -Paul LGTM > >

Re: GSoC 2016

I forgot to mention that I asked those currently listed as mentors. I'll report when all have responded. -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: GSoC 2016

think this should be a project that can be handled successfully in a GSoC project (and most of it is *not* an all-or-nothing endeavour), and I would be willing to mentor it. Urs Am 21.01.2016 um 17:02 schrieb Urs Liska: > Starting the next round somewhat earlier ... > > Surprisingly t

Re: Behaviour of is-absolute?

Am 25.01.2016 um 11:55 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 25.01.2016 um 10:07 schrieb David Kastrup: >> >>> What actual problem are you trying to address here? >> LilyPond will consider "C:\\some\\path"

Re: text-replacements: add and the like (issue 281470043 bysimon.albre...@mail.de)

Am 26.01.2016 um 17:45 schrieb Trevor Daniels: > Simon Albrecht wrote Monday, January 25, 2016 8:03 PM > >> How should I (and James) interpret the silence here? Any more opinions? > If a user has requested additional characters which have an html character > (non-numeric) definition and a

Re: Behaviour of is-absolute?

Am 25.01.2016 um 10:07 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Hi all, >> >> now that is-absolute? is not broken anymore (see #4746 and #4747) I'd >> like to raise the question of its *behaviour* - which seems somewhat &g

Re: Web: edits to Google Summer of Code page (issue 282260043 by paulwmor...@gmail.com)

LGTM. There's the question about the mentors themselves. There are people on this list who don't seem to be around anymore. But we should deal with the *content* in a separate patch. Urs Am 24. Januar 2016 02:45:07 MEZ, schrieb paulwmor...@gmail.com: >Please review. Thanks, -Paul >

Behaviour of is-absolute?

Hi all, now that is-absolute? is not broken anymore (see #4746 and #4747) I'd like to raise the question of its *behaviour* - which seems somewhat inconsistent to me. Currently this function behaves differently on Windows and elsewhere, and I think this shouldn't be the case. is-absolute?

GSoC 2016

Starting the next round somewhat earlier ... Surprisingly there also will be a Google Summer of Code 2016, and I think we should be better prepared this time and not miss a slot due to lack of students. Mentoring organizations apply between 8-19 February, students 14-25 March. IIRC in our case

Result of (ly:get-option 'point-and-click)

Hi devs, please consider #(if (ly:get-option 'point-and-click) (let ((point-and-click (ly:get-option 'point-and-click))) (display point-and-click))) Can this ever print anything else than #t ? As far as I can see (ly:get-option 'point-and-click) can return either #t or #f, is

Re: How to create a restricted symbols context property

Am 18.01.2016 um 11:31 schrieb Urs Liska: > And how do I retrieve the value of the property in a C++ class? > I see this in bar-number-engraver.cc: > > SCM alternative_style = get_property > ("alternativeNumberingStyle"); > string text_tag = &

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

Am 18.01.2016 um 16:17 schrieb Paul Morris: >> On Jan 18, 2016, at 7:43 AM, g...@ursliska.de wrote: >> >> This is a great enhancement. > Thanks Urs. > >> I commented on one typo, but I saw two issues (I'll add images to the >> lilypond-devel copy of this message as soon as it pops up): >> >> 1)

How to create a restricted symbols context property

I have created a new boolean context property by - adding an entry in define-context-properties.scm - setting the default in engraver-init.ly - retrieving it in a class's (Beaming_option) from_context method However, I would like to add another context property (and modify the added one) from

Re: How to create a restricted symbols context property

Am 18.01.2016 um 11:31 schrieb Urs Liska: > I have created a new boolean context property by > - adding an entry in define-context-properties.scm > - setting the default in engraver-init.ly > - retrieving it in a class's (Beaming_option) from_context method > > However, I

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

Am 18.01.2016 um 13:43 schrieb g...@ursliska.de: > This is a great enhancement. > > I commented on one typo, but I saw two issues (I'll add images to the > lilypond-devel copy of this message as soon as it pops up): > > 1) > In one file the instrument name was severely truncated (BeiMannern ...

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

Am 18.01.2016 um 16:35 schrieb Urs Liska: >>> 2) >>> >> In another file with three staves (staff + piano staff) the vertical >>> >> spacing of the systems is unusably large. >> > How do these compare with ly:one-line-breaking ? (I might try

Re: Add RemoveEmptyStavesAll command (issue 283050043 by simon.albre...@mail.de)

Am 14.01.2016 um 16:34 schrieb Simon Albrecht: > On 14.01.2016 16:20, d...@gnu.org wrote: >> The name is rather clumsy (and it does not help that the issue report >> talks about "\RemoveEmptyStavesFirst" while the actual patch and the >> Rietveld review has "\RemoveEmptyStavesAll"). > > That’s

Re: Typo in the Contributor's Guide

Am 13.01.2016 um 13:55 schrieb Menu Jacques: > Hello folks, > > ‘sortly’ instead of ‘shortly’. Well, I think this is more a conceptual conflict than a typo :-/ > > JM > > -- > > 14.7 Grand LilyPond Input Syntax Standardization (GLISS) > > Summary > > • Start: sortly after 2.14 comes

Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

+0000 Von: Urs Liska <u-li-1...@users.sf.net> Antwort an: [testlilyissues:issues] <4...@issues.testlilyissues.p.re.sf.net> An: [testlilyissues:issues] <4...@issues.testlilyissues.p.re.sf.net> * *labels*: --> Fixed_2_19_35 * *status*: Started --> Fixed * *

Re: Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Am 28.12.2015 um 16:33 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Hi all, >> >> I've just pushed my patch for #4704, having reworked the branch to five >> discrete commits (removing detours but separating work on different >&

Re: Improve beam count handling with subdivided beams (issue 276560043 by g...@ursliska.de)

Am 23.12.2015 um 10:06 schrieb d...@gnu.org: > On 2015/12/23 07:59:26, git wrote: >> Revert changes to snippets file > > At the current point of time, you only added > Documentation/snippets/new/xxx.ly while keeping > Documentation/snippets/xxx.ly unchanged. That's the right organisation > for

Re: Improve beam count handling with subdivided beams (issue 276560043 by g...@ursliska.de)

Am 22.12.2015 um 20:51 schrieb Carl Sorensen: > Copy the snippet to Documentation/snippets/new. > > Remove the machine-generated header. > > Make your changes. > > Submit the patch. OK, that is more or less what I did (in patch set 2). The only thing that is left for me to update is *not* to

Re: Two git-cl questions

The editor that is opened depends on the EDITOR environment variable so you can use whatever you want. HTH Urs Am 21. Dezember 2015 20:14:57 MEZ, schrieb Simon Albrecht : >Hello, > >after a long time I’ve now tried and uploaded a patch again. Two >questions on the git

Where to edit "selected snippets"

Hi all, for a patch I'm currently finishing I have to update the documentation, concretely one of the "selected snippets". I'm not sure where I have to do that. Is that something I should do in Documentation/snippets or should that be done in the LSR? TIA Urs

Re: Where to edit "selected snippets"

Am 21.12.2015 um 22:19 schrieb Urs Liska: > Hi all, > > for a patch I'm currently finishing I have to update the documentation, > concretely one of the "selected snippets". > I'm not sure where I have to do that. Is that something I should do in > Documentation/sni

git cl wording issue

Just used the current git-cl for the first time and noticed a *minor* glitch. This link in the console output: Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4704/ points to the raw (JSON?) data. In order to provide a useful clickable link the "rest/" should be

Re: Retrieve (remaining) duration of beam (in C++)

Am 18.12.2015 um 17:49 schrieb Urs Liska: > I have > infos_[i].start_moment_ > to determine the moment of the *current* beam Oops, that should of course read "the current *stem*" ___ lilypond-devel mailing list lilypond-

Retrieve (remaining) duration of beam (in C++)

Hi, I just looked again at my attempts to get beam subdivision on the right track. Unfortunately I need some help understanding Beaming_pattern::beamify in beaming-pattern.cc. If I'm not mistaken the calculation of the beam count iterates over the infos_ struct, whose members contain information

Re: Retrieve (remaining) duration of beam (in C++)

Am 18.12.2015 um 18:35 schrieb Carl Sorensen: > > On 12/18/15 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of Urs Liska" <lilypond-devel-bounces+c_sorensen=byu@gnu.org on > behalf of u...@openlilylib.org> wrote: > > >> If

Re: [PATCH] musicxml2ly: Avoid duplicate "tr" if both and, are present

Am 15.12.2015 um 09:06 schrieb James: > Ticket created at: > https://sourceforge.net/rest/p/testlilyissues/issues/4698/ http://sourceforge.net/p/testlilyissues/issues/4698/ ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: improving ottavation

Am 28. November 2015 17:27:01 MEZ, schrieb Phil Holmes : >- Original Message - >From: "Kieren MacMillan" >To: "Phil Holmes" >Cc: "Lilypond-User Mailing List" ; >"lilypond-devel"

Fwd: [testlilyissues:issues] #4664 Ensure at least one beam is left with subdivideBeams

Is this correct in the new tracker: Update status and label but leave the issue open? I assume it will be closed after being veified? Urs Ursprüngliche Nachricht Von: Urs Liska <u-li-1...@users.sf.net> Gesendet: 25. November 2015 13:58:02 MEZ An: "[testlilyis

Re: SubdivideBeam gives undesired result when beaming over more thana quarter note

Am 20.11.2015 um 10:38 schrieb Phil Holmes: > - Original Message - From: "Urs Liska" <u...@openlilylib.org> > To: "Trevor Daniels" <t.dani...@treda.co.uk>; "James" <p...@gnu.org>; > "Phil Holmes" <m...@philholmes

Re: SubdivideBeam gives undesired result when beaming over more thana quarter note

Am 20.11.2015 um 00:57 schrieb Trevor Daniels: > Urs Liska wrote Thursday, November 19, 2015 11:20 PM > >> However, I have a question: Where are the CLI messages defined that are >> used in the git-cl process? This is still talking about Google issue >> tracker items. >

Re: SubdivideBeam gives undesired result when beaming over more than a quarter note

it. > > Now it should all work, > > James > > > > > > The Allura Server URL is > > On 19/11/15 13:57, Urs Liska wrote: >> I've implemented a fix for this (hey, my first working C++ patch :-) ) >> but now I'm stumbling over the new git-cl workflow (

Re: Allura account

-cl. That was the first thing I did when things didn't work ... Urs > > Trevor > > - Original Message - > From: "Trevor Daniels" <t.dani...@treda.co.uk> > To: "Urs Liska" <u...@openlilylib.org> > Cc: "Lily-Devel List" <lilypond-devel@gnu.o

Re: SubdivideBeam gives undesired result when beaming over more than a quarter note

e Oauth tab and create > your own 'Bearer token' - it should be obvious how to do that. Then you > can use that value as the final entry for your git-cl config when it > asks you for it. > > Now it should all work, > > James > > > > > > The Allura Server

<    1   2   3   4   5   6   7   8   >