Re: Non-numeric time signatures

Hello Dan, I think the double c and double cut c symbols are very much non-standard, unlike single cut c for 4/2, which I consider to be in use very widely. With this difference in frequency of use I don’t find your suggestion convincing. What made me suggest the 'style option is the strong

Re: Language selection code

Am 27.03.2015 um 09:24 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Hello, triggered by a discussion on -user I have begun to implement a new \language command which in addition to setting the note names input language Why would you set the note names input language

Re: Reasons for cross-voice limitations?

Am 29.03.2015 um 23:46 schrieb Kevin Barry: For sure the voice context limitations are a pain, and if I knew how, I would write a function for starting and finishing slurs without the need for creating a hidden voice, but I don't even know if it is possible. In my own head, I imagine that

Re: Language selection code

Am 27.03.2015 um 10:39 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Am 27.03.2015 um 09:24 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Hello, triggered by a discussion on -user I have begun to implement a new \language command which

Re: Language selection code

Am 27.03.2015 um 14:38 schrieb David Nalesnik: Hi Simon, On Thu, Mar 26, 2015 at 6:43 PM, Simon Albrecht simon.albre...@mail.de mailto:simon.albre...@mail.de wrote: [...] So the roadmap would include – discussing design and coding (?) I haven't gone through this thoroughly, but I

Re: Language selection code

Am 27.03.2015 um 10:39 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Am 27.03.2015 um 09:24 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Hello, triggered by a discussion on -user I have begun to implement a new \language command which

Language selection code

Hello, triggered by a discussion on -user I have begun to implement a new \language command which in addition to setting the note names input language also automatically translates the default text fields in tagline and table of contents, or may be used for both tasks separately. By now, with

Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)

Hello, I’d also vote for the three-ways distinction relative/absolute/octave as put by Trevor. Am 06.05.2015 um 20:43 schrieb David Kastrup: Werner LEMBERG w...@gnu.org writes: Probably the best name is \octave, which was used for something similar until version 0.1.19 \octave c''

Re: absolute pitch entry: accept an offset octave (issue 235010043 by k-ohara5...@oco.net)

Hello Wol, most of this has been discussed already: Am 08.05.2015 um 20:40 schrieb Wols Lists: On 07/05/15 16:19, Paul Morris wrote: On May 7, 2015, at 10:43 AM, Paul Morris p...@paulwmorris.com wrote: \relative [optional pitch] { ... \absolute [no pitch] { ... \octave [obligatory

Re: Compile LilyPond for NaCl

Am 13.05.2015 um 18:50 schrieb Carl Sorensen: On 5/12/15 4:50 PM, Trevor trevordi...@gmail.com wrote: Could any useful part of LilyPond be compiled for NaCl https://developer.chrome.com/native-client/overview#why-use-native-client ? Is that at all within the realm of possibility? I'm not an

Re: Add sans-serif and monospace fonts (issue 224800043 by truer...@gmail.com)

Am 09.04.2015 um 07:14 schrieb d...@gnu.org: On 2015/04/08 20:18:55, lemzwerg wrote: I like the current overall look for _this_ choice of fonts better afterwards as compared to before, even though the C glyph has a more conspicuous rounding and the G glyph has the well-known somewhat

Re: Language selection code

unnecessarily) difficult… Yours, Simon Am 27.03.2015 um 00:43 schrieb Simon Albrecht: Hello, triggered by a discussion on -user I have begun to implement a new \language command which in addition to setting the note names input language also automatically translates the default text fields

Fwd: LilyDev Docker image?

Janek, does this come too late? Dénes, I assume that you meant ‘building LilyDev’ in your first sentence. Yours, Simon Weitergeleitete Nachricht Betreff:LilyDev Docker image? Datum: Thu, 25 Jun 2015 20:14:26 + (UTC) Von:Dénes Harmath harmathde...@gmail.com An:

Issues contributorship

Hello team, in order for me to fulfill my new duty as a Bug Squad member, could someone please add me as a contributor to the Issues database? (if also it will be for two months only with google code :-)) I’m registered there with this e-mail address, pseudonym ‘Ton Mahler’. Thanks, Simon

Re: Issues contributorship

Thanks. Am 17.06.2015 um 16:13 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Hello team, in order for me to fulfill my new duty as a Bug Squad member, could someone please add me as a contributor to the Issues database? (if also it will be for two months only

Re: add stencil-whiteout-outline function (issue 236480043 by paulwmor...@gmail.com)

LGTM. ~ Simon Am 01.06.2015 um 17:50 schrieb paulwmor...@gmail.com: But I think I prefer the following which has a consistent parallel structure across all the categories and where the new style of whiteout is named in a way that conveys that it is the default, with the old box style getting a

Re: add stencil-whiteout-outline function (issue 236480043 by paulwmor...@gmail.com)

Hello, Am 31.05.2015 um 03:07 schrieb k-ohara5...@oco.net: I realize I am changing my opinion here on a few points: […] (A convert-ly rule may be needed… maybe in any case to change whiteout to whiteout-box? ...or maybe not?) Looking at the existing uses of \whiteout Xxx.whiteout, it

Scheme coding style

Hello, a while ago I found this document on what appear to be very widely accepted standards for formatting scheme code: http://community.schemewiki.org/?scheme-style. I find it very useful and it seems to be altogether uncontroversial while warranting good legibility. Do we also accept

Re: Scheme coding style

Am 29.05.2015 um 22:30 schrieb Thomas Morley: 2015-05-29 21:25 GMT+02:00 Simon Albrecht simon.albre...@mail.de: Hello, a while ago I found this document on what appear to be very widely accepted standards for formatting scheme code: http://community.schemewiki.org/?scheme-style. I find it very

Re: Scheme coding style

Am 29.05.2015 um 22:25 schrieb Carl Sorensen: On 5/29/15 1:25 PM, Simon Albrecht simon.albre...@mail.de wrote: Hello, a while ago I found this document on what appear to be very widely accepted standards for formatting scheme code: http://community.schemewiki.org/?scheme-style. I find

Re: Scheme coding style

I’ll come up with some text suggestions, or a patch, but not tonight. Greetings, Simon Am 29.05.2015 um 23:10 schrieb Carl Sorensen: On 5/29/15 2:30 PM, Thomas Morley thomasmorle...@gmail.com wrote: 2015-05-29 21:25 GMT+02:00 Simon Albrecht simon.albre...@mail.de: Hello, a while ago I found

Re: PATCHES: Countdown for August 26th 2015 - IMPORTANT UPDATE TO PATCH REVIEW PROCESS - PLEASE READ

Hello James, so many thanks for all the managing work you are doing here! It’s priceless in keeping our project going, I think. Am 23.08.2015 um 18:58 schrieb James Lowe: I'm not sure what the bug squad want to do with regard to new bugs that need 'tracking', How about managing this through

Re: Music glyph design choices

Am 10.08.2015 um 22:10 schrieb tisimst: Yes and no. I don't feel super comfortable putting together an official .PATCH, but I can definitely post my proposed changes or send updated files to anyone who has more experience getting these officially in the assembly line. FWIW I took the liberty to

Add music-type-predicate function (issue 255910043 by d...@gnu.org)

LGTM. https://codereview.appspot.com/255910043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Reasons why a LilyPond-to-MEI conversion should be developed

On 24.10.2015 16:54, David Kastrup wrote: They are not in LilyPond. There is no tangible or recognizable thing like a "music stream" […] chances are rather slim that parts of the code could be usefully adapted to work with LilyPond these days. What a pity, it would have seemed a nice

Re: Reasons why a LilyPond-to-MEI conversion should be developed

On 25.10.2015 09:15, Urs Liska wrote: if LilyPond should consume >>MEI > >Interesting thought. I should be surprised if MEI were to consent in >granting LilyPond this honour (as which I’d consider it). Given the >‘universal’ intent of MEI, they might not want to ‘take sides’ with >LilyPond (as

Re: My finances for working on LilyPond

On 22.10.2015 19:21, David Kastrup wrote: As you all know, my sole source of income are donations from happy LilyPond users. It would appear that LilyPond users have stopped being happy with my work. You must know that this is not the case. I should be much surprised if I were the only one

Re: Issue 4504 whiteout-style

Hello Paul, On 25.10.2015 20:39, Paul Morris wrote: Introduce whiteout-style, with options of 'box and 'outline, as a grob property to be used with the whiteout grob property, and as an optional property of the whiteout markup command. Remove the whiteout-box grob

Re: My finances for working on LilyPond

On 26.10.2015 04:04, Paul Morris wrote: Maybe “contributing” is a good heading for all these things, i.e. we could have a single “contributing” page instead of “help us” and “sponsoring” pages? ‘Contributing’ is the more technical term and to me it’s associated with doing actual work on the

Re: Reasons why a LilyPond-to-MEI conversion should be developed

On 24.10.2015 03:18, Paul Morris wrote: LilyPond’s internal scheme data structure is a good target for import and export Or even more so the music stream internally used by LilyPond after Erik Sandberg’s work. IIUC there is some doubt as to how complete the features he describes in his

Re: Cropped SVG Output

Hello David, On 28.10.2015 22:05, David Sankel wrote: Would anyone object to a patch where I add a '-dpreview-include-all-systems' option to lilypond? Generally I’d say that patches are welcome, but certainly it makes sense to find out if the feature is desired before putting too much work

Re: Reasons why a LilyPond-to-MEI conversion should be developed

On 23.10.2015 17:44, Urs Liska wrote: Hello devs, I would like to get some feedback for use when preparing the mei2ly application. I will deliberately not say what I think about the topic to get less influenced opinions. We will have to define a scope for the project that is sufficiently big

Feature Requests (was: Re: My finances for working on LilyPond)

On 23.10.2015 20:31, Bernardo Barros wrote: Something I requested many years ago was the support for quarter-tone tablatures notation, which seems to work but is actually buggy at the moment, it generates wrong tablatures in strings with quarter-tones alterations etc. Did it receive some

Re: Feature Requests

On 24.10.2015 00:26, Simon Albrecht wrote: On 23.10.2015 20:31, Bernardo Barros wrote: Something I requested many years ago was the support for quarter-tone tablatures notation, which seems to work but is actually buggy at the moment, it generates wrong tablatures in strings with quarter-tones

Re: Beginning contributor needs mentor

On 10.11.2015 16:36, John Gourlay wrote: I’m a recently retired software engineer highly experienced with C++, less with Unix and open-source development, and not at all with Scheme. I fear that you may not get around learning some scheme, since our C++ source is quite interlinked with

New issue (4661): Improve naming of music functions `overrideProperty` and `propertyOverride`

Hello, please comment (preferably in the tracker, I think): "All of the names |overrideProperty| and |property[Override|Revert|Set|Tweak|Unset]| are not quite descriptive, which is a hurdle in understanding their function, small for the latter but large for the former. Also,

Re: plan for 2.20 release?

On 14.11.2015 14:40, Federico Bruni wrote: Hi There's any plan for the next stable release? Good question. It’s odd to keep telling people on -user how they should upgrade to an unstable version, which some don’t dare do, although it’s actually quite stable. I'm asking out of curiosity

Re: Implement make-bow-stencil, make-tie-stencil for use in markup-commands undertie and overtie (issue 270640043 by thomasmorle...@gmail.com)

Man, sorry, while not being up to your coding skills, I can make nitpicks… https://codereview.appspot.com/270640043/diff/1/scm/stencil.scm File scm/stencil.scm (right): https://codereview.appspot.com/270640043/diff/1/scm/stencil.scm#newcode50 scm/stencil.scm:50: @var{bow-height} determines the

Regtest dynamics-broken-hairpin.ly

Hello, forgive if this should be an unnecessary question, but: does this regtest do what it should? The description says: \header{ texidoc = Broken crescendi should be open on one side. } but the code reads \relative { c''1 \ \break c1\! \ \break c1\! } so each hairpin actually ends

Re: Regtest dynamics-broken-hairpin.ly

you could add this as an issue, but not follow up with a fix to git? Yes. I’ve yet to follow up with that bit of knowledge… But I’ll create an issue on bug-lilypond. Thanks, Simon -- Phil Holmes - Original Message - From: Simon Albrecht simon.albre...@mail.de To: ly-devel lilypond

Re: TextScript automatically italic in Dynamics context

Am 26.08.2015 um 22:50 schrieb Wols Lists: On 26/08/15 21:42, Abraham Lee wrote: Why is that? I see no reason that text in this context *must* be italic by default (and I know it can be changed back). Can someone help me understand the logic there? Because, in pretty much every score I know,

Re: Learning about Allura

Am 30.08.2015 um 22:27 schrieb Trevor Daniels: @Bug Squad I've noticed a couple of things about Allura which are worth mentioning: a) When you add a new issue or change the status, patch, label, etc, of an existing one, it takes some time, i.e. several minutes, before it shows up

CL output language within lily-git.tcl

Hello, I’m quite surprised that the command line output of Git displayed in lily-git.tcl is in German – if I run Git directly from the terminal, it’s English, and indeed I’ve even changed the language of my whole system to English by now (that was before I had lily-git.tcl). How can I fix

Re: CL output language within lily-git.tcl

Am 30.08.2015 um 22:29 schrieb Simon Albrecht: Hello, I’m quite surprised that the command line output of Git displayed in lily-git.tcl is in German While the messages from lily-git itself are English… – if I run Git directly from the terminal, it’s English, and indeed I’ve even changed

Fix regtest "dynamics-broken-hairpin.ly" (issue 258470044 by simon.albre...@mail.de)

Reviewers: , Message: My first patch :-) Description: Fix regtest "dynamics-broken-hairpin.ly" Change regtest to match its title, including an updated description. Please review this at https://codereview.appspot.com/258470044/ Affected files (+9, -5 lines): M

Re: thinking twice about the new issue tracker

Am 02.09.2015 um 09:33 schrieb David Kastrup: Federico Bruni writes: Hi folks I know that a lot of time has been invested on Allura, especially by Trevor. So I feel uneasy in writing this email, but I have the feeling that the time costraint didn't help to make the best

Re: Google-to-Allura port adds brackets around rests

Am 07.09.2015 um 20:09 schrieb Dan Eble: Compare https://code.google.com/p/lilypond/issues/detail?id=1677 https://sourceforge.net/p/testlilyissues/issues/1677/ The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.

Re: Google-to-Allura port adds brackets around rests

Am 08.09.2015 um 00:23 schrieb Trevor Daniels: Simon Albrecht wrote Monday, September 07, 2015 7:16 PM Am 07.09.2015 um 20:09 schrieb Dan Eble: Compare https://code.google.com/p/lilypond/issues/detail?id=1677 https://sourceforge.net/p/testlilyissues/issues/1677/ <https://sourceforge.ne

Re: Scheme output changes in ly:make-duration and ly:make-pitch

Am 08.09.2015 um 17:51 schrieb Karim Haddad: Hello, I have written a parser that transcribes lilypond scheme output from \displayMusic . Something has drastically changed (?) since version 2.19.x It is not documented yet (?) the format in 2.18.x was (ly:make-duration 2 0 1) in 2.19 :

Re: Issue 4595: NR: Describe default fonts as TeX Gyre fonts (issue 268780043 by truer...@gmail.com)

https://codereview.appspot.com/268780043/diff/1/Documentation/notation/text.itely File Documentation/notation/text.itely (right): https://codereview.appspot.com/268780043/diff/1/Documentation/notation/text.itely#newcode1460 Documentation/notation/text.itely:1460: (alias of TeX Gyre Cursor). I’d

Improve wording for an NR paragraph (issue 259710043 by simon.albre...@mail.de)

Reviewers: , Message: I came across this rather mishapen wording in NR 4.6.2 – so I changed it. Description: Improve wording for an NR paragraph The paragraph from "Avoid (or reduce)" in spacing.itely used 'for example' twice in a row. The description of the 'volta bracket' issue was unclear

Re: Improve wording for an NR paragraph (issue 259710043 by simon.albre...@mail.de)

Thanks for the input. https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right): https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely#newcode3489

Re: thinking twice about the new issue tracker

Am 02.09.2015 um 11:27 schrieb Federico Bruni: Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels ha scritto: meanwhile we use Bitbucket or Github? Not Free services, I know, but at least their business model seems honest. This is on the GC FAQ covering migration

Re: thinking twice about the new issue tracker

Am 02.09.2015 um 11:59 schrieb Federico Bruni: Il giorno mer 2 set 2015 alle 11:41, Simon Albrecht <simon.albre...@mail.de> ha scritto: I made the bitbucket repository public: https://bitbucket.org/fedelibre/lilyissues/issues?status=new=open ‘Access denied’ for me…

Re: Small error in Allura issue import

Am 04.09.2015 um 13:17 schrieb Trevor Daniels: Simon Albrecht wrote Friday, September 04, 2015 12:50 AM I won’t fix this now, because we have no solution for the problem that all comments on the issue are deleted if e.g. the summary is changed – a quite unpleasant ‘feat’ of Allura which I

Small error in Allura issue import

Hello, I just came across a small error in the issue import: in the summary for , " <> " has been omitted. It’s present in the Google Code DB. I won’t fix this now, because we have no solution for the problem that all comments on the issue

Allura: next/previous issue buttons?

Hello, one feature which I miss in Allura is having buttons to go to the next/previous issue from one issue’s page, such as were present in Google Code. Trevor, is it realistic to have something like that implemented? Whom might we ask that? Thanks, Simon

Allura code highlighting

Hello, Trevor has already introduced a warning to use delimiting for .ly code blocks. Now I noticed that Allura imposes some code highlighting by default, and pygments (the tool used) doesn’t make a good guess on the language. Unfortunately, it doesn’t support LilyPond (yet?). I couldn’t

Re: Ties within chords inconsistency

Am 09.09.2015 um 08:28 schrieb David Kastrup: Simon Albrecht <simon.albre...@mail.de> writes: Am 04.09.2015 um 04:09 schrieb David Kastrup: Simon Albrecht <simon.albre...@mail.de> writes: Hello, consider the following example: \version "2.19.25" \

Re: Ties within chords inconsistency

Am 09.09.2015 um 23:41 schrieb David Kastrup: Simon Albrecht <simon.albre...@mail.de> writes: Hello David, pardon if I insist another time. Am 09.09.2015 um 22:40 schrieb David Kastrup: Joram <joram.no...@gmx.de> writes: Hi Simon, I see. The difference is: I would not h

Re: Fwd: [testlilyissues:issues] #1677 Partcombine misses notes (r after R)

Am 10.09.2015 um 01:14 schrieb Dan Eble: Simon, do you know why I might have received this email? It does not seem that anything in the ticket was updated. (I also received a similar email about #4550.) I clicked ‘Edit’ and ‘Save’ without making any changes. This is a workaround for a bug

Re: info-lilypond?

Am 14.09.2015 um 09:03 schrieb Phil Holmes: I'm the only one who would normally post to it. It requires posters to be "whitelisted", which I am. However, anything I send to it does not appear, for reasons I don't understand. Shouldn’t we get that fixed, then? I don’t know who could help

info-lilypond?

Hello, I see that there have been no notifications on info-lilyp...@gnu.org since 2.19.13 in September 2014; should we remove (or comment) the respective notice on ? Yours, Simon ___ lilypond-devel mailing list

Fwd: [forge:site-support] #11241 Bug with issue import and <> in summary

89/ Thanks SourceForge Support *[site-support:#11241] <http://sourceforge.net/p/forge/site-support/11241/> Bug with issue import and <> in summary* *Status:* assigned *Labels:* engr nf-7989 *Created:* Mon Sep 14, 2015 01:49 PM UTC

Re: Issues list status

Am 15.09.2015 um 15:39 schrieb David Kastrup: Phil Holmes writes: A comment and a question about the status field of the issues list. Comment: with Google code, the status was automatically set to "Accepted" for issues manually entered by a registered user. I see no

Re: Ties within chords inconsistency

Sorry, I see pasting images inline has completely failed. See below and attached. Am 10.09.2015 um 01:13 schrieb Simon Albrecht: Am 09.09.2015 um 23:41 schrieb David Kastrup: Simon Albrecht <simon.albre...@mail.de> writes: Hello David, pardon if I insist another time. Am 09.09.2015

Re: Allura: next/previous issue buttons?

Am 09.09.2015 um 19:41 schrieb Simon Albrecht: You can raise tickets against Allura development by clicking on the Support Request link at the bottom of the LilyPond Issues page. I’ll do so. <http://sourceforge.net/p/forge/site-support/11227/> Though I’m not quite sure if it’s the

Fwd: ly musicxml export

Hello Martin, there might be more right addressees for this at the frescobaldi mailing list. Forwarding. Yours, Simon Forwarded Message Subject:ly musicxml export Date: Mon, 28 Sep 2015 15:32:34 +0200 (CEST) From: Martin Tarenskeen

Re: Allura: next/previous issue buttons?

Am 09.09.2015 um 18:48 schrieb Trevor Daniels: Simon Albrecht wrote Wednesday, September 09, 2015 2:17 PM one feature which I miss in Allura is having buttons to go to the next/previous issue from one issue’s page, such as were present in Google Code. Where are they? Have a look at <ht

Re: Ties within chords inconsistency

Am 09.09.2015 um 21:04 schrieb Joram: Hi, I apologize already for entering a discussion I might not be able to follow due to a lack of knowledge. The in-chord out-of-chord difference makes sense to me. For me the question arises: what to expect from this syntax: \new Voice << { c''^~ c'' } {

Re: Ties within chords inconsistency

Hello David, pardon if I insist another time. Am 09.09.2015 um 22:40 schrieb David Kastrup: Joram writes: Hi Simon, I see. The difference is: I would not have expected that to work. But I can see the benefit if it would, now. Sigh. It works perfectly. Of course it

Re: List of Issues with 'patch_abandoned' assigned to them - as of September 2015

On 20.09.2015 23:10, James Lowe wrote: My thinking is like this; I pick an issue to work on, I do some stuff, make a patch, have a discussion, then get bored and go silent. The issue is now patch_abandoned. What is the benefit of leaving this label (or even having it in the first place) One

Re: New Issue: Disallow uncontained context-spec-music on top level

On 23.09.2015 16:52, David Kastrup wrote: Simon Albrecht <simon.albre...@mail.de> writes: <https://sourceforge.net/p/testlilyissues/issues/4617/> If $ git grep'= #(context-spec-music' Documentation/snippets/additional-voices-to-avoid-collisions.ly:voiceFive= #(co ly/

New Issue: Disallow uncontained context-spec-music on top level

If $ git grep'= #(context-spec-music' Documentation/snippets/additional-voices-to-avoid-collisions.ly:voiceFive= #(co ly/declarations-init.ly:melisma= #(context-spec-music (make-property-set 'melis ly/declarations-init.ly:melismaEnd=

Re: New Issue: Disallow uncontained context-spec-music on top level

On 23.09.2015 17:57, David Kastrup wrote: Simon Albrecht <simon.albre...@mail.de> writes: On 23.09.2015 16:52, David Kastrup wrote: and that error is based exclusively on the _content_ of ")" and not related to any independently produced warnings. For example, you can write

Re: List of Issues with 'patch_abandoned' assigned to them - as of September 2015

On 21.09.2015 00:18, James Lowe wrote: The 'new' status was for those issues that had been added by random Joes (not members of the bug squad) and then it was changed to 'Accepted' once the issue was checked - else it would be marked invalid or duplicate (or even merged). If we're going to keep

Re: Allura at SF is ready

Am 28.08.2015 um 17:14 schrieb Trevor Daniels: The migration of the tracker from GC to Allura at SF has gone well. Very good! Thank you. Attachments are present and searches work (in the Allura style, which takes some getting used to, but is pretty comprehensive.) I've set up some common

Fwd: [testlilyissues:issues] #4696 Hairpin shouldn’t be ‘shut up’ by cross-staff stem

understand enough to figure out how to make a change like this. Developers, am i thinking in the right direction? --- ** [issues:#4696] Hairpin shouldn’t be ‘shut up’ by cross-staff stem** **Status:** Accepted **Created:** Sun Dec 13, 2015 10:46 PM UTC by Simon Albrecht **Last Updated:** Sun Dec

Re: Musicians prefer LilyPond scores, study finds

On 17.12.2015 18:57, Trevor Daniels wrote: Francisco Vila wrote Thursday, December 17, 2015 4:53 PM I just gained my PhD. My humble thesis tells the design and results of an experiment with a number of musicians, comparing lilypond scores with the originals which those scores were copied from.

NR 3.3.2: nitpicks in lily example (issue 284060044 by simon.albre...@mail.de)

Reviewers: , Message: Sorry, I made a mess and had to create a new Rietveld issue. I’m not quite familiar with the process yet… Well, this is to Harm’s comments. I wasn’t quite sure about indenting arguments to \partcombine, but I prefer having all in one line anyway. Description: NR 3.3.2:

4717: Replace incorrect naming rule in LM (issue 284070043 by simon.albre...@mail.de)

Reviewers: , Message: I promise to learn how to use git cl correctly :-/ For now, it’s no real problem that it’s an entirely new Rietveld issue, since I didn’t retain anything from the first approach. Upon your comments, I replaced the former incorrect wording by a statement merely expressing

NR 3.3.2: nitpicks in lily example (issue 284060043 by simon.albre...@mail.de)

Reviewers: , Message: Please review. Description: NR 3.3.2: nitpicks in lily example add a missing space and use a layout block instead of duplicating code Please review this at https://codereview.appspot.com/284060043/ Affected files (+7, -3 lines): M Documentation/notation/input.itely

Re: LM 2.4.1: More accurate description of variable naming rules (issue 280560043 by simon.albre...@mail.de)

On 29.12.2015 23:01, pkx1...@gmail.com wrote: https://codereview.appspot.com/280560043/diff/20001/Documentation/learning/common-notation.itely File Documentation/learning/common-notation.itely (right):

Re: git cl problem: Couldn’t create Allura issue

On 29.12.2015 15:38, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> Sent: Monday, December 28, 2015 10:12 PM Subject: git cl problem: Couldn’t create Allura issue Hello

Re: Error in git-cl creating a new issue

On 06.01.2016 13:26, Trevor Daniels wrote: John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM I just submitted a small change to the Contributors Guide using git-cl. The patch got into codereview.appspot.com, but not into sourceforge.net/p/testlilyissues/issues/. I let git-cl

Re: Error in git-cl creating a new issue

On 06.01.2016 12:48, Thomas Morley wrote: 2016-01-06 4:07 GMT+01:00 John Gourlay : I just submitted a small change to the Contributors Guide using git-cl. The patch got into codereview.appspot.com, but not into sourceforge.net/p/testlilyissues/issues/. I let git-cl

Re: Error in git-cl creating a new issue

On 06.01.2016 15:10, Trevor Daniels wrote: Simon Albrecht, you wrote Wednesday, January 06, 2016 1:14 PM On 06.01.2016 13:26, Trevor Daniels wrote: John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM I just submitted a small change to the Contributors Guide using git-cl. The patch

Re: LilyPond boolean syntax? \true and \false

On 05.01.2016 18:45, David Kastrup wrote: Paul Morris writes: Thanks to David Kastrup’s work there’s now much less need to use scheme syntax in overrides etc. (e.g. the dot syntax instead of #' and no longer needing # for numbers). This has really simplified things for

Re: Document all outside-staff-priority values; neaten table (issue 280580043 by philehol...@googlemail.com)

On 01.01.2016 13:43, philehol...@googlemail.com wrote: Reviewers: , Message: Please review. Description: Follows on from a question on -user. There aren't that many values of outside-staff-priority, so it seems easiest to list them all if we're going to list most. The adjustments to the

ly:moment<=? ??

Hello, while getting to terms with the accidentalStyle code I found that it would be useful (currently only for dodecaphonic-no-repeat-rule, scm/music-functions.scm:line 1682f.) to have a ly:moment<=? Scheme predicate function. It’s easy to do in Scheme: (define (ly:moment<=? a b) (or

Re: Two git-cl questions

On 21.12.2015 22:09, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> Sent: Monday, December 21, 2015 7:14 PM Subject: Two git-cl questions Hello, after a long time I’v

Re: Two git-cl questions

On 21.12.2015 22:17, Thomas Morley wrote: 2015-12-21 20:14 GMT+01:00 Simon Albrecht <simon.albre...@mail.de>: Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process: What exact value should I use for ‘Allura server’? I didn’t get that

Re: Store accidental styles in an alist (issue 280510043 by simon.albre...@mail.de)

Sorry that this is such a large and convoluted patch. It had to be done this way. The actual functionality should be unchanged, only the structure is disentangled and made accessible for custom additions. In the course of action, I corrected one or two typos in comments – hope that’s OK. Should

Re: ly:moment<=? ??

On 21.12.2015 02:23, David Nalesnik wrote: On Sun, Dec 20, 2015 at 7:08 PM, Simon Albrecht <simon.albre...@mail.de <mailto:simon.albre...@mail.de>> wrote: Hello, while getting to terms with the accidentalStyle code I found that it would be useful (cu

Two git-cl questions

Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process: What exact value should I use for ‘Allura server’? I didn’t get that right. And, please, is there a way to upload a patch and edit the message without vi? I have absolutely no experience

Re: Store accidental styles in an alist (issue 280510043 by simon.albre...@mail.de)

On 22.12.2015 15:39, d...@gnu.org wrote: https://codereview.appspot.com/280510043/diff/20001/scm/music-functions.scm#newcode1702 scm/music-functions.scm:1702: (define-public accidental-styles The only rationale for making this a public variable is if the user is expected to be able to change

git cl problem: Couldn’t create Allura issue

Hello, sorry, but I still don’t seem to get along with git cl. I just uploaded a patch and it went fine until: ~/lilypond-git (dev/doc)$ git cl upload origin/master Documentation/learning/common-notation.itely | 25 +++-- 1 file changed, 23 insertions(+), 2

Re: Crash with tupletFullLength = ##t

Hello Mark, this would have been in the domain of the bug list. On 23.12.2015 19:58, Mark Knoop wrote: When tupletFullLength is set to ##t, the TupletBracket is actually *shortened* by a following RehearsalMark. This doesn't happen with tupletFullLength = ##f. This is merely ugly when a

git cl issue: Changing Allura patch status for updated patch set

(putting this into an extra e-mail) Hello Phil, when uploading a new version of a patch set already on Rietveld, git cl sports an error message about how it couldn’t update the Patch status on Allura. Can you fix this? Thanks for providing the tool! Simon

Re: Store accidental styles in an alist (issue 280510043 by simon.albre...@mail.de)

On 23.12.2015 14:52, James wrote: Simon, On 22/12/15 23:36, Simon Albrecht wrote: On 22.12.2015 15:39, d...@gnu.org wrote: https://codereview.appspot.com/280510043/diff/20001/scm/music-functions.scm#newcode1702 scm/music-functions.scm:1702: (define-public accidental-styles The only rationale

  1   2   3   >