2.20 announcements/publicity

Hello everybody, I’ve been more or less lurking on the lists for quite a while now and I’m sorry for not contributing myself these days. I’m thrilled about the boost to development efforts that could be seen and immensely grateful for all of you keeping up the good work, especially completing

Re: Re: An exciting new release… of Sibelius!!!

Let's be honest, they really had to get their stuff together to keep any ground all against Dorico. Best, Simon > On 27.03.2020 - 15:26, Shane Brandes wrote: > > > They are really on the ball on that one. > > > -Shane > > > On Fri, Mar 27, 2020 at 10:09 AM Valentin Villenave > wrote: > >

GS version conflict in packaged 2.20 and 2.21

Hello everyone, it appears from this exchange that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known issue? Best, Simon

Re: GS version conflict in packaged 2.20 and 2.21

On 18.04.20 01:46, Simon Albrecht wrote: Hello everyone, it appears from this exchange <https://lists.gnu.org/archive/html/lilypond-user/2020-04/msg00294.html> that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known

Re: GS version conflict in packaged 2.20 and 2.21

On 19.04.20 16:56, Valentin Villenave wrote: Yes, a French user also had some gs issues that I think may be related to yours: https://lists.gnu.org/archive/html/lilypond-user-fr/2020-04/msg00164.html That seems to be the same usage issue—see my parallel reply or the -user thread. Best, Simo

Re: GS version conflict in packaged 2.20 and 2.21

On 19.04.20 20:27, Werner LEMBERG wrote: Do we have a warning somewhere in the LilyPond documentation that people must not use the binary directly but the wrapper? Simon, have you tried to find something in the docs? If yes, what keywords were you looking for? I have no idea from where I mig

‘Know which branch we’re on’ on Ubuntu 16

Hello, finally I’ve managed to get Ubuntu 16.04 working, and copied all of my previous home directory including .bashrc. However, the ‘export PS1’ trick suggested in with the following line in .bashrc: expo

Re: ‘Know which branch we’re on’ on Ubuntu 16

On 04.06.2017 19:02, David Kastrup wrote: Simon Albrecht writes: Hello, finally I’ve managed to get Ubuntu 16.04 working, and copied all of my previous home directory including .bashrc. However, the ‘export PS1’ trick suggested in <http://lilypond.org/doc/v2.19/Documentation/contribu

Re: VirtualBox error

On 07.06.2017 01:27, Kieren MacMillan wrote: Hello all, I'm trying to set up LilyDev. Running Mac OS X 10.12.5 on an iMac with 16GB RAM. 1. Downloaded the most recent VirtualBox — no problem. 2. Installed VirtualBox — no problem. 3. Launched VirtualBox — no problem. 4. Created my LilyDev vir

Re: connecting lines (spanners?) between arbitrary grobs/locations

On 14.06.2017 19:51, Kieren MacMillan wrote: I've attached a screenshot of a Schenker graph That seems to have gone amiss… Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: connecting lines (spanners?) between arbitrary grobs/locations

On 14.06.2017 22:44, Kieren MacMillan wrote: Hi Simon, On 14.06.2017 19:51, Kieren MacMillan wrote: I've attached a screenshot of a Schenker graph That seems to have gone amiss… That's the second time I've posted a screenshot, and the second time it didn't make it to the list. Is there somet

Re: connecting lines (spanners?) between arbitrary grobs/locations

On 14.06.2017 22:53, Kieren MacMillan wrote: Here's a 71KB version. I can see it displayed below the footer in Thunderbird, though not as an ordinary attachment and it’s not a Schenker graph, but 7 staves of ordinary notation plus some annotations… Best, Simon __

Re: True Hand-engraved Dashed Slurs

On 27.06.2017 22:15, tisimst wrote: How often are these split slurs used? I personally have never had a reason to use them, but I guess they must be used somewhere. They’re used in scientific editions e.g. if a slur is begun before the line break, but not continued after in the source. Any

Re: PDF landscape issue

On 01.07.2017 18:44, Francisco Vila wrote: Hello, I'd like to know if something has changed recently about the way LilyPond creates landscape documents. In 2.19.58, a landscape document looks right in Evince and in Frescobaldi music PDF preview. In 2.19.62, the same document is rotated 90º coun

Re: Some questions related to score video generation

On 07.07.2017 15:00, Knut Petersen wrote: I Fyrreskoven. Excellent! I love it. Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

On 20.07.2017 00:45, Dan Eble wrote: 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 t

Re: Should we have a from-barline property in analogy to to-barline ?

On 24.07.2017 13:58, David Kastrup wrote: Seems like an obvious addition. Would make stuff (like slurs, hairpins and so on) starting at the bar move backwards to the bar line. Probably also useful for non-spanners like a \fermata ? I have difficulty imagining use cases. Is to-barline really u

Re: Should we have a from-barline property in analogy to to-barline ?

On 24.07.2017 15:30, David Kastrup wrote: Making a bar line an event would then place per-chord articulation marks of the following note on the bar line. You mean { c1 \bar "||" \fermata \bar "|." \fermata } would place both fermatas on the barlines? I don't think that this idea

Re: New repeat type

On 30.08.2017 23:42, Dan Eble wrote: The disease is that Lilypond needs to see lyrics for multiple stanzas encoded as simultaneous music in order to set them one below another, and the right action is to cure that I find the metaphor slightly too strong, since I think the ‘cure’ is merely in

Re: How to locate all layout-property values for a particular LayoutObject in the source files?

On 24.09.2017 14:30, James wrote: Where would I go to see the 'complete list' of all possible NoteHead.style values – the description of the style property isn’t helpful (since it summarises the use of that p

Re: Fwd: \tempo feature requests

On 10.10.2017 13:57, Malte Meyn wrote: I made a patch for this (only snippet 1008, not yet 574). Because that’s not a bugfix but an extension to LilyPond, should this first be discussed on this list or on the issue tracker? Or should I upload it right now to Rietveld and discuss then? Especi

Re: Terminology of baseMoment, beats, groups

On 11.11.2017 12:30, David Kastrup wrote: I have a hard time seeing a "beat" as something that can have different lengths. Musical notation isn’t well-defined in a mathematical or programming sense, so there are no such strict rules as all beats of a measure having to be the same length. If n

Octave check warning

Hello, here’s a kind of pet peeve of mine: With a warning like warning: octave check failed; expected "a", found: "a," I always have to look twice what the difference between the two is. It might be easier to read as warning: octave check failed; expected "a" and found "a," (or: ‘but found’)

Re: access to the issue tracker

On 06.12.2017 14:31, Phil Holmes wrote: - Original Message - From: "Семен Миргородский" To: Sent: Wednesday, December 06, 2017 5:23 AM Subject: access to the issue tracker Hi! My name is Semyon and I'm trying to translate documentation to russian language. Please, give me access to

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

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 ‘end-of-section mark’ in your head, but \depart seems far to

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

On 07.02.2018 10:37, Torsten Hämmerle wrote: So why not using something like *\repeatMark*, *\markRepeat* or *\markRepetition*, ...? Seen that way, even \repeatMark "Fine" feels natural to me, because - like an ordinary RehearsalMark, or a MetronomeMark, it's just a new kind of Mark, which is, wi

Re: Chromatic solfedge

On 14.02.2018 23:01, Joseph Austin wrote: Is it feasible to use the \language feature or some other facility to enter music with solfedge abbreviations for note-names, e.g. " d r m f s l t " (for Do Re Mi Fa Sol La Ti) instead of " c d e f g a b? It should be straightforward to define your own

Web/Easier editing update

Hi everybody, I noticed slight glitches when having a look at the ‘Easier editing’ page on the website. This is the text about Frescobaldi: > Frescobaldi is a lightweight, yet powerful, music and text editor with many features added and enhanced particularly for LilyPond. Major features incl

Re: Web/Easier editing update

On 28.02.2018 19:03, Kieren MacMillan wrote: Frescobaldi is a lightweight, yet powerful, music and text editor with many features added and enhanced particularly for LilyPond. Major features include point-and-click links between the code and music views, detailed score wizards, built in LilyPo

Replacement for gmane to post bug reports

Hi, it seems that the functionality to report bugs without subscribing to the bug list is missed. (Gianmaria Lari just contacted me privately, and I told him that it’s possible to subscribe to the list and turn off mail delivery – probably one solution.) Is there anything similar to the gman

Re: Web/Easier editing update

On 28.02.2018 19:05, Kieren MacMillan wrote: No commas at all: “Frescobaldi is a lightweight yet powerful music and text…” Thanks! Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Problem with showing git status in bash

Hello everybody, I just applied the suggestion from the CG to add export PS1="\u@\h \w\$(__git_ps1)$ " export GIT_PS1_SHOWDIRTYSTATE=true export GIT_PS1_SHOWUNTRACKEDFILES=true export GIT_PS1_SHOWUPSTREAM=auto to ~/.bashrc in order to show the status of a git repository in the command prompt.

Re: Problem with showing git status in bash

On 01.03.2018 20:59, Joram wrote: The git-part you want to add is just the '$(__git_ps1)' part. So you can use the original $PS1 and add that part if you don't want other changes. Thanks, that’s what I did, ending up with this monster: export PS1="\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_

Re: Issue 3128: add Haydn-style turns to Feta (issue 340660043 by lilyp...@maltemeyn.de)

On 08.04.2018 19:08, nine.fierce.ball...@gmail.com wrote: Is there a performance difference between these two scripts?  I read quickly through the thread referenced in the ticket, but I couldn't find the answer. I’m not sure what exactly the difference in performing is, but that’s not for us

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

On 20.04.2018 15:43, Torsten Hämmerle wrote: What do you think about making skylines consider the grob properties rotation and extra-offset? (1) keep everything as it is (2) skylines should reflect both grob rotation and grob extra-offset (3) skylines should reflect grob rotation only (4) skylin

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

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" When should the version number be updated? Only if new features

No hint on outdated translated docs

Hello everybody, Bernhard Kleine has pointed out that while it has been problematic for years already to use e.g. the German version of the docs, because the translation hasn’t been updated in a long time and many new features are missing, the German docs do not make any hint of that circumsta

Re: No hint on outdated translated docs

On 30.06.2018 21:33, Federico Bruni wrote: Hi Simon There's already an open issue about this request. Opened by me, IIRC. I also suggested to move the language selection from the footer to the header of each page. In another issue.. It's all in the tracker. We miss someone willing to work on

melismaBusyProperties: scheme syntax vs. lily syntax

Hello everybody, I just noticed that it’s possible to use the LilyPond symbol list/key list syntax when setting melismaBusyProperties. However, the doc string reads "A list of properties (symbols) to determine whether a melisma is playing. Setting this property will influence how lyrics are a

Re: melismaBusyProperties: scheme syntax vs. lily syntax

On 16.07.2018 02:51, Carl Sorensen wrote: On 7/15/18, 3:29 PM, "lilypond-devel on behalf of David Kastrup" wrote: Simon Albrecht writes: > Hello everybody, > > I just noticed that it’s possible to use the LilyPond symbol list/key > li

Re: Appearance of S-curves

Hi, I find the second one with crossing beziers mich more pleasant, but I'm sure the question is easily settled by looking at any good hand-engraved example (I'm travelling right now and don't have any at hand, sorry). Best, Simon > On 26.04.2019 - 13:10, Thomas Morley wrote: > > > Hi, > > cu

Re: What is holding up 2.20 release?

I would like to give whatever small contribution I can make to this without knowing so much on the technical levels; please do tell me whether I say below is considered helpful. On 18.11.19 18:10, Jonas Hahnfeld wrote: 965a607096 Fix #1367: NoteNames context in any language not sure, has qui

Re: vim script for transpositions

Hello, thanks for your interest in sharing. LilyPond’s code base doesn’t contain any tools like this. There are of course LilyPond’s built-in music functions for transposing, but that’s a slightly different use case. What’s more comparable are the tools for manipulating input code contained

Re: LilyPond 2.22.2 released

On 22/02/2022 14:07, Phil Holmes wrote: We are proud to announce the release of GNU LilyPond 2.22.2 on 2-22-22 (i.e. February the 22nd, 2022). Fabulous ;) Thanks to everyone involved!

Alteration value in localAlterations can now be 'tied?

Hello everybody, I hope it is appropriate for me to post this here, I haven’t closely followed development for a long time. I have a custom accidental style following 18th century usage (example attached) which fails in 2.23.6 because the internals have changed. Namely, for the sixth note in

Re: Slanted Beams thickness

Hi everyone, On 25/03/2022 01:44, Valentin Petzel wrote: Hello, Lilypond handles slanted Beams in a geometrically weird way, that is, the thickness is not measured as the shortest distance between the opposing sides of the boundary, but as vertical distance. This results in Beams getting optica

Issue with download link

Hello everyone, On 24/07/2022 19:44, Jonas Hahnfeld via LilyPond user discussion wrote: Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.23/Documentation/learning/installing This link leads to a 2.23

[WISH] ‘smart’ punctuation for Lyrics

Dear devs, when I use tags to differentiate lyrics in different parts, I often have to complicate the source file and duplicate code in order because of different punctuation that results from different repetitions and/or elisions. Very much boiled down: \lyricmode {   yes   \tag alto,bass {

General appreciation

Hello development team, I can’t exactly see where my life is going and whether I might be able to contribute more to the project in the future. In the meantime, I want to say that I’m really happy to look at the progress that is happening and grateful for all of you that make it possible. Ev

Re: LilyPond Visual Index for forthcoming version 2.26

Hi Werner, the Index looks great, thanks a lot for your work on this! I have two minor points of feedback on the second page: There should IMO be some padding between the boxed (magenta) headings, and they should always be in the order *Score, *Staff, *Voice, *Lyrics. I hope this is a good p

Re: Website Indices

On 23.03.24 03:20, Christopher Heckman wrote: The Lilypond website has two indices: a command index, and a (generic) index. From the descriptions, it seems like the generic index includes everything in the command index and then some. Would it be possible to combine them into one index? When I lo

Visual Index Manual where?

Hi everyone, I was reading through the Changes document for 2.25.15 and wanted to look at the Visual Index, which it says is now included as a manual. However, I couldn’t find it on the overview page for the manuals nor as appendix to any manual that it would fit in. Am I missing something?

Re: Visual Index Manual where?

On 22.04.24 15:26, Werner LEMBERG wrote: I was reading through the Changes document for 2.25.15 and wanted to look at the Visual Index, which it says is now included as a manual. However, I couldn’t find it on the overview page for the manuals nor as appendix to any manual that it would fit in.

Re: question about frescobaldi/python-ly

Hi Begüm, since nobody replied: Unfortunately the frescobaldi project isn’t properly maintained at the moment, as was discussed on the lilypond-user list starting April 28th. Best, Simon On 29.05.24 13:34, begum onal wrote: Dear community, My name is Begüm Önal, I also wrote to the Frescoba

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 an

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: Language selection code

Am 27.03.2015 um 09:24 schrieb David Kastrup: Simon Albrecht 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? Huh? That’s only what

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 mailto:simon.albre...@mail.de>> wrote: [...] So the roadmap would include – discussing design and coding (?) I haven't gone through this thoroughly, but I did not

Re: Language selection code

Am 27.03.2015 um 10:39 schrieb David Kastrup: Simon Albrecht writes: Am 27.03.2015 um 09:24 schrieb David Kastrup: Simon Albrecht 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

Re: Language selection code

Am 27.03.2015 um 10:39 schrieb David Kastrup: Simon Albrecht writes: Am 27.03.2015 um 09:24 schrieb David Kastrup: Simon Albrecht 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

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 LilyPon

Re: Language selection code

erhaps 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 fie

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: 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 writes: Probably the best name is \octave, which was used for something similar until version 0.1.19 \octave c'' {c4 e g c e g 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 wrote: \relative [optional pitch] { ... \absolute [no pitch] { ... \octave [obligatory pitch] { … The downside

Re: Compile LilyPond for NaCl

Am 13.05.2015 um 18:50 schrieb Carl Sorensen: On 5/12/15 4:50 PM, "Trevor" wrote: Could any useful part of LilyPond be compiled for NaCl

Scheme coding style

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

Re: Scheme coding style

Am 29.05.2015 um 22:30 schrieb Thomas Morley: 2015-05-29 21:25 GMT+02:00 Simon Albrecht : 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

Re: Scheme coding style

Am 29.05.2015 um 22:25 schrieb Carl Sorensen: On 5/29/15 1:25 PM, "Simon Albrecht" 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 it ve

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" wrote: 2015-05-29 21:25 GMT+02:00 Simon Albrecht : Hello, a while ago I found this document on what appear

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 does

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 m

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 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 with google code :-)) I’m

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 An: bug-lilyp...@gnu.o

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: 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 p

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 t

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, d

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"

her. I'm assuming 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" To: "ly-

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

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 tha

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 in

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 input/regression/dynamics-brok

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 decision for the new

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 to GitHub: Error "Pro

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 ha scritto: I made the bitbucket repository public: https://bitbucket.org/fedelibre/lilyissues/issues?status=new&status=open ‘Access denied’ for me… I made the repository public,

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 in

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 Documentation/notation/spacing.itely:348

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

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

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”. Oh

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 : (ly:make-

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

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 writes: Am 04.09.2015 um 04:09 schrieb David Kastrup: Simon Albrecht writes: Hello, consider the following example: \version "2.19.25" \new Voice << { c''^~ c'' } { a

  1   2   3   >