Re: Key list in lyricmode

Simon Albrecht writes: > Hello everybody, (well, to be honest, hello David :-) ) > > I’m sorry, but I still need some enlightenment on the new alist > variable feature. What’s the problem with the following snippet? > > %%% > \version "2.19.39" > > cantus.1 = { e'

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

Noeck writes: > And I was not up-to-date in a previous mail: Python 3 is already the > default in the latest Ubuntu release. How do you figure that? I have an up-to-date Ubuntu and calling "python --version" gives 2.7.11+. -- David Kastrup

Guitar bend error

I’m transcribing a rock guitar solo, and to engrave the many string bends I’m using Stephen MacNeil’s LilyPond code library, available here: http://mglessons.com/lilypond/ If I use the “definitions_No-Tab.ly” file, LilyPond engraves the file with no hiccups. However, if I use the

Re: What is the proper way of programmatically generating markup?

> On 24 Apr 2016, at 1:38 PM, Paul Morris wrote: > >> On Apr 23, 2016, at 11:00 PM, Matt Hood > > wrote: >> >> **So my second question is: How do I programmatically generate markup from >> information taken from a list,

Re: What is the proper way of programmatically generating markup?

> On Apr 23, 2016, at 11:00 PM, Matt Hood wrote: > > **So my second question is: How do I programmatically generate markup from > information taken from a list, and then put it into a single markup > variable?** Hi again, I’d suggest looking at snippets in the LSR,

Re: ANN: Frescobaldi 2.19.0

On Sat 23 Apr 2016 at 22:09:55 (+0200), Noeck wrote: > Hi, > > print 'foo' vs. print('foo') is usually the most frequent difference and > writing code for a 'common subset' in most cases requires at least some > from __future__ imports to ensure compatibility. All my programs converted perfectly

Re: What is the proper way of programmatically generating markup?

> On Apr 23, 2016, at 11:00 PM, Matt Hood wrote: > > does anyone know where can I find the source (scm or otherwise) for > \compoundMeter? You’ll find it in ly/music-functions-init.ly Hope that helps, -Paul___ lilypond-user

What is the proper way of programmatically generating markup?

Hi everyone, So I’m writing a function that reimplements the ‘\compoundMeter’ command with an Orff-style time signature, whereby the denominator of the signature is a note head (as opposed to a number), e.g. 4/4 = 4/crotchet, 9/8 = 3/dotted-crotchet, 15/16+2/4 = 5/dotted-quaver + 2/crotchet.

Re: Multi-measure rests and mark collisions ...

On Sat 23 Apr 2016 at 11:25:05 (+0100), Wols Lists wrote: > On 22/04/16 19:36, David Wright wrote: > > On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: > >> On 22/04/2016 14:31, Kieren MacMillan wrote: > >>> David K wrote: > > Hm? How could you even have a compressed

Key list in lyricmode

Hello everybody, (well, to be honest, hello David :-) ) I’m sorry, but I still need some enlightenment on the new alist variable feature. What’s the problem with the following snippet? %%% \version "2.19.39" cantus.1 = { e' } cantus.lyr.1 = \lyricmode { Mi } << { \cantus.1 }

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

On Sat, 23 Apr 2016, Noeck wrote: And I was not up-to-date in a previous mail: Python 3 is already the default in the latest Ubuntu release. Fedora: https://fedoraproject.org/wiki/Changes/Python_3_as_Default -- MT ___ lilypond-user mailing

Re: Multi-measure rests and mark collisions ...

On 23/04/2016 12:23, Kieren MacMillan wrote: Hi Wol, if I use "extra-spacing-width" (which iirc works fine with multi-measure-rests), as soon as I have another part which actually has some notes in the first bar of the MMR, that first bar will be the same width as the markup so that then looks

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

And I was not up-to-date in a previous mail: Python 3 is already the default in the latest Ubuntu release. Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

2016-04-23 15:19 GMT+02:00 Federico Bruni : > I guess that in 4 years Linux distros will "have to" (?) migrate to > python3. > Currently new Debian packages written in Python 2 should be refused: https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html

Re: ANN: Frescobaldi 2.19.0

Hi, print 'foo' vs. print('foo') is usually the most frequent difference and writing code for a 'common subset' in most cases requires at least some from __future__ imports to ensure compatibility. However, the 2to3 tool is handy and there are very sane and good guidelines for porting python

Re: Scheme optional arguments, number-list

Thomas Morley writes: > my-time = > #(define-music-function (v1 v2)(scheme? scheme?) > #{ \time $v1 $v2 #}) > %% doesn't work > { > %% \time redefined with comma-separated list > \my-time 2,2,1 5/8 > g'8 8 8 8 8 > %% or > \my-time 1,1,2,1 5/8 > g'8 8 8 8

Re: Scheme optional arguments, number-list

Mark Knoop writes: > In this instance single number lists are not relevant anyway. So I've > tried this method: > > #(define (multi-number-list? x) > (and (list? x) >(< 1 (length x)) >(every number? x))) > > testfn = #(define-void-function > (a)

Re: ANN: Frescobaldi 2.19.0

On Fri, 22 Apr 2016 10:22:23 +0200 Urs Liska wrote: > Am 22.04.2016 um 10:19 schrieb Johan Vromans: > >> Frescobaldi 2.19.0 has been released into the wild. > > Good job! Thanks! > > > >> - The new LilyPond feature to embed source code files in the PDF > >> (LilyPond

Re: Scheme optional arguments, number-list

2016-04-23 16:27 GMT+02:00 Mark Knoop : > Thanks David, > > At 15:01 on 23 Apr 2016, David Kastrup wrote: >>Mark Knoop writes: >>> On upgrading to 2.19.32, one of my regular functions no longer works. >>> It seems that a single number as the first argument is now

Re: Scheme optional arguments, number-list

Thanks David, At 15:01 on 23 Apr 2016, David Kastrup wrote: >Mark Knoop writes: >> On upgrading to 2.19.32, one of my regular functions no longer works. >> It seems that a single number as the first argument is now accepted >> as a number-list whereas before it was not and thus

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

Federico Bruni writes: > On Sat, Apr 23, 2016 at 02:56:47PM +0200, David Kastrup wrote: >> >> Upgrading to a newer version of GCC stopped our release process from >> working for several months. That's exactly the kind of "it should not >> be a big deal" that you are talking

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

On Sat, Apr 23, 2016 at 02:56:47PM +0200, David Kastrup wrote: > > Upgrading to a newer version of GCC stopped our release process from > working for several months. That's exactly the kind of "it should not > be a big deal" that you are talking about here. > That's why the upgrades should be

Re: ANN: Frescobaldi 2.19.0

2016-04-22 7:55 GMT+02:00 Wilbert Berendsen : > Frescobaldi 2.19.0 has been released into the wild. Precompiled application for (Mac) OS X are now available. Download: http://frescobaldi.org/download Best wishes. Davide ___

Re: Scheme optional arguments, number-list

Mark Knoop writes: > On upgrading to 2.19.32, one of my regular functions no longer works. > It seems that a single number as the first argument is now accepted as a > number-list whereas before it was not and thus became the second > argument. > > Whilst the new possibility to

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

Andrew Bernard writes: > Hi David, > > But lilypond ships its own internal version of python in > …lilypond/usr/bin. Assuming that you install from our precompiled binary packages. Obviously, that's not what the developers do since they need to run LilyPond right after

Scheme optional arguments, number-list

On upgrading to 2.19.32, one of my regular functions no longer works. It seems that a single number as the first argument is now accepted as a number-list whereas before it was not and thus became the second argument. Whilst the new possibility to write lists as 1,2,3,4 is very nice, is there any

Re: partcombine and tag

Thank you David, that's clear! g. On Sat, Apr 23, 2016 at 11:08 AM, David Kastrup wrote: > Gianmaria Lari writes: > > > What if I change this > > > > note = \partcombine {e'} {\tag #'pdfOut c' \tag #'midiOut c'} > > > > > > in this: > > > > note = { \new

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

Hi David, But lilypond ships its own internal version of python in …lilypond/usr/bin. Is this not to shield lilypond from system versions? In my Ubuntu I have: $ uname -a Linux fivefold 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $

Re: Multi-measure rests and mark collisions ...

Hi Wol, > if I use "extra-spacing-width" (which iirc works fine with > multi-measure-rests), as soon as I have another part which actually has > some notes in the first bar of the MMR, that first bar will be the same > width as the markup so that then looks awful \textLengthOff ? Hope this

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

Andrew Bernard writes: >> On 23/04/2016, 6:33 PM, "David Kastrup" wrote: >> >>>Well, unless there are really compelling reasons otherwise, sticking >>>with a common subset (namely making it work with Python 3 while keeping >>>it working with Python 2)

Re: Multi-measure rests and mark collisions

On 23/04/16 01:52, Kieren MacMillan wrote: > Hi David, > >> It strikes me as conceptually problematic to try to put a fermata on a >> multi-measure rest. >> Who does this, and what does it mean, musically? >> In this example, you are actually placing a fermata on a single bar of rest. >> In

Re: Multi-measure rests and mark collisions ...

On 22/04/16 19:36, David Wright wrote: > On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: >> On 22/04/2016 14:31, Kieren MacMillan wrote: >>> David K wrote: > Hm? How could you even have a compressed multi-measure rest when there > is anything like an "8-bar phrase" in

Re: ANN: Frescobaldi 2.19.0

2016-04-22 7:55 GMT+02:00 Wilbert Berendsen : > Frescobaldi 2.19.0 has been released into the wild. Precompiled application for (Mac) OS X coming in a few hours. Best wishes. Davide ___ lilypond-user mailing list lilypond-user@gnu.org

Re: ANN: Frescobaldi 2.19.0

2016-04-22 19:08 GMT+02:00 Steve Noland : > When do you expect it to appear in MacPorts? I'm updating the Portfiles right now. After I submit them, I expect the usual 1-3 days for approval. Best wishes. Davide ___ lilypond-user

Python 3, was Re: ANN: Frescobaldi 2.19.0

Pardon my ignorance but why do you want to support a common subset? For what purpose? The whole point of Python 3 is that it breaks 2 in order to become a superior and more consistent langauge. It’s been out since 2008, an eternity in IT terms. Please help me understand. Andrew On

Re: partcombine and tag

Gianmaria Lari writes: > What if I change this > > note = \partcombine {e'} {\tag #'pdfOut c' \tag #'midiOut c'} > > > in this: > > note = { \new Voice << {e'} {\tag #'pdfOut c' \tag #'midiOut c'}>>} > > > Now it works, but should I expect any side effects? It is

Re: partcombine and tag

What if I change this note = \partcombine {e'} {\tag #'pdfOut c' \tag #'midiOut c'} in this: note = { \new Voice << {e'} {\tag #'pdfOut c' \tag #'midiOut c'}>>} Now it works, but should I expect any side effects? It is equivalent? Thanks, g. ___

Re: partcombine and tag

Ciao David you wrote: [...] > \partcombine runs and creates a common score. Since none of the tags is > removed, the result contains both c4 and c'4. This is stored in \note. > thank you for you explanation now it is perfectly clear what happens. > I don't remember: doesn't partcombine

Re: ANN: Frescobaldi 2.19.0

Andrew Bernard writes: > Hi Martin, > > I have brought this topic up before, but it keeps getting knocked back > by naysayers. > > I am volunteering to bring lilypond to Python 3. It would be helpful > in many ways. Are there objections, folks? Well, unless there are

Re: ANN: Frescobaldi 2.19.0

Hi Martin, I have brought this topic up before, but it keeps getting knocked back by naysayers. I am volunteering to bring lilypond to Python 3. It would be helpful in many ways. Are there objections, folks? Andrew On 23/04/2016, 4:49 PM, "Martin Tarenskeen"

Re: ANN: Frescobaldi 2.19.0

Il giorno sab 23 apr 2016 alle 8:49, Martin Tarenskeen ha scritto: - Why isn't LilyPond bundled with at least Python 2.7? Are there any known issues with Python 2.7? It seems to work fine here on my Fedora box. - If future versions of Frescobaldi will require

Re: tempo and different staves

Solved. Sorry for the noise m > Il giorno 23 apr 2016, alle ore 08:03, matpen3@gmail ha > scritto: > > Hi David, > > thanks. > > I’d like to have tempos above the voice staff and above the piano part, so, > reading manuals and forums, it seems you have to remove them

Re: Multi-measure rests and mark collisions

On 23.04.2016 02:06, Flaming Hakama by Elaine wrote: It strikes me as conceptually problematic to try to put a fermata on a multi-measure rest. Who does this, and what does it mean, musically? You must be kidding. While calling R1 a MultiMeasureRest may be slightly confusing in LilyPond

Re: tempo and different staves

Hi, I don't know why that matters, but you can omit the line \consists "Metronome_mark_engraver" in the pianostaff \with block and put it in the \with block of the upper ("right") Staff. That works for me. Cheers, Joram ___ lilypond-user mailing

Re: ANN: Frescobaldi 2.19.0

On Fri, 22 Apr 2016, Paul Morris wrote: Um, so... 2.19 still uses Qt4. In the future, version 3.0 will require Qt5 (and Python3). So future Frescobaldi 3.x version will require Python3. Python scripts in the LilyPond package currently need Python2. On Linux Fedora I'm running it with

Re: ANN: Frescobaldi 2.19.0

Il giorno sab 23 apr 2016 alle 2:12, Andrew Bernard ha scritto: On Debian 8.4, the current git master builds after a long session struggling to manually solve dependenices, and then when run, simply unceremoniously dumps core. I have a pristine, newly installed Debian

Re: tempo and different staves

Hi David, thanks. I’d like to have tempos above the voice staff and above the piano part, so, reading manuals and forums, it seems you have to remove them from score and assign to single staves. m > Il giorno 23 apr 2016, alle ore 07:58, David Kastrup ha > scritto: > >