Re: Ties within chords inconsistency

Simon Albrecht writes: > Am 10.09.2015 um 01:13 schrieb Simon Albrecht: > >> How would you code something like > > [chord-entry-1.png] > >> >> or > > [chord-entry-2.png] > >> >> (and there are many such examples in the piece I’m engraving) in >> LilyPond? Use <> for every single chord? If you wa

Re: problems with build and/or test-baseline

Il giorno gio 10 set 2015 alle 0:24, Thomas Morley ha scritto: Btw, 1) the CG states: " Finally, and in some ways most importantly, let’s make sure that we know what branch we’re on. If you’re not using LilyDev, add this to your ‘~/.bashrc’: export PS1="\u@\h \w\$(__git_ps1)$ " You may need

Re: Automatically avoiding multi-measure rest creation

On Sep 9, 2015, at 03:32 , David Kastrup wrote: > > If you basically have some "multi-measure rest whenever there is no > music" functionality, it would seem to make sense to give the end > spanner a proper event as well so that you don't have to write > << \music #(multi-measure-rest-of-length m

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 writes: Hello David, pardon if I insist another time. Am 09.09.2015 um 22:40 schrieb David Kastrup:

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 i

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

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.) — Dan > Begin forwarded message: > > From: "Simon Albrecht" > Subject: [testlilyissues:issues] #1677 Partcombine misses notes (r

Re: Ties within chords inconsistency

Am 09.09.2015 um 23:41 schrieb David Kastrup: Simon Albrecht writes: 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 woul

Re: problems with build and/or test-baseline

2015-09-09 23:57 GMT+02:00 Federico Bruni : > Il giorno mer 9 set 2015 alle 23:09, Thomas Morley > ha scritto: >> >> But I have some problems (being on LilyDev3): >> >> 1) >> ~/lilypond-git/build (master)$ ../configure >> returns: >> ERROR: Please install required programs: TeX Gyre fonts OTF

Re: problems with build and/or test-baseline

Il giorno mer 9 set 2015 alle 23:09, Thomas Morley ha scritto: But I have some problems (being on LilyDev3): 1) ~/lilypond-git/build (master)$ ../configure returns: ERROR: Please install required programs: TeX Gyre fonts OTF (make sure the fc-list utility can see them, e.g. 'sudo apt-get

Re: Ties within chords inconsistency

Joram writes: > Hi David, > >> Why wouldn't it be a chord? > > That's why I wrote »Or is it a real chord?«. > >> Articulations and ties not written _inside_ of a chord do not belong to >> "single notes". They belong to a moment in time. > > This was the missing piece for my understanding. I woul

Re: Ties within chords inconsistency

Hi David, > Why wouldn't it be a chord? That's why I wrote »Or is it a real chord?«. > Articulations and ties not written _inside_ of a chord do not belong to > "single notes". They belong to a moment in time. This was the missing piece for my understanding. I would have expected that an a and

Re: Ties within chords inconsistency

Simon Albrecht writes: > 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 wo

Re: Ties within chords inconsistency

Joram writes: > Hi David, > > hm. So, this << { } { } >> can be used to combine notes into a chord, > except that it is not real chord but just notes at the same point in > time in the same voice. What do you think a chord is? It is just notes at the same point in time in the same voice. > Whi

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 works as long as you k

Re: problems with build and/or test-baseline

2015-09-09 16:02 GMT+02:00 Masamichi HOSODA : >> Hi, >> >> I newly nuked my \build-directory in order to get a fresh one. >> >> But I have some problems (being on LilyDev3): >> >> 1) >> ~/lilypond-git/build (master)$ ../configure >> returns: >> ERROR: Please install required programs: TeX Gyre fon

Re: problems with build and/or test-baseline

2015-09-09 13:38 GMT+02:00 James : > > > On 09/09/15 01:03, Thomas Morley wrote: >> Hi, >> >> I newly nuked my \build-directory in order to get a fresh one. >> >> But I have some problems (being on LilyDev3): >> >> 1) >> ~/lilypond-git/build (master)$ ../configure >> returns: >> ERROR: Please insta

Re: Ties within chords inconsistency

Hi David, hm. So, this << { } { } >> can be used to combine notes into a chord, except that it is not real chord but just notes at the same point in time in the same voice. Which looks like a chord and (from the music point of view) is a chord (what else?) but isn't (at least for LP)? Or is it a r

Re: Ties within chords inconsistency

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. Per-chord ties don't magically turn into in-chord ties, but if you really need in-chord ties, nobody keeps you from writing th

Re: Ties within chords inconsistency

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. Cheers, Joram ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Ties within chords inconsistency

Hi, >> For me the question arises: what to expect from this syntax: >> \new Voice << { c''^~ c'' } { a'_~ a' } >> ? >> Two voices in the same voice? > > How would LilyPond start new voices when it's already at bottom level? Excatly, that was my question. > When at bottom level, << >> without \\

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'' } { a'

Re: Ties within chords inconsistency

Joram writes: > 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'' } { a'_~ a' } >>

Re: Ties within chords inconsistency

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'' } { a'_~ a' } >> ? Two voices in the same voic

Re: Ties within chords inconsistency

Simon Albrecht writes: > Am 09.09.2015 um 08:28 schrieb David Kastrup: >> >>> >>> >>> My ‘possibly related’ statement was only supposed to indicate that >>> these issues have similar topics and are likely concerned with similar >>> parts of

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

Re: Allura: next/previous issue buttons?

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? > Trevor, is it realistic to have something like that implemented?

Re: problems with build and/or test-baseline

> Hi, > > I newly nuked my \build-directory in order to get a fresh one. > > But I have some problems (being on LilyDev3): > > 1) > ~/lilypond-git/build (master)$ ../configure > returns: > ERROR: Please install required programs: TeX Gyre fonts OTF (make > sure the fc-list utility can see them,

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'_~ a' } >> \new Voice << { c'' } { a' } >>

Re: Allura code highlighting

Am 09.09.2015 um 15:56 schrieb Simon Albrecht: > 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. Unfort

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: 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). On 2

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 ___

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

Thank you Simon and David for the info. Will look closely into that. Best Karim Haddad > 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.

Re: problems with build and/or test-baseline

On 09/09/15 01:03, Thomas Morley wrote: > Hi, > > I newly nuked my \build-directory in order to get a fresh one. > > But I have some problems (being on LilyDev3): > > 1) > ~/lilypond-git/build (master)$ ../configure > returns: > ERROR: Please install required programs: TeX Gyre fonts OTF (make >

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

Werner LEMBERG wrote Wednesday, September 09, 2015 5:37 AM > >> Further to this, there are over 300 issues containing rests in >> square brackets, of which 77 are still active (i.e. they have a >> Status of Accepted Started or New.) So we really ought to fix those >> if it is at all possible. >

Re: Automatically avoiding multi-measure rest creation

Dan Eble writes: > To fix a defect in \partcombine, I think I want the > Multi_measure_rest_engraver to refrain from creating its grobs in > measures that have interesting musical content. If you basically have some "multi-measure rest whenever there is no music" functionality, it would seem to