Hey all,
I'm running LilyPond on the command line from Mac OS X and it is hanging right
after printing the version. I downloaded several versions (stable, unstable,
previous unstable) and it happens with all of them. This is a recent-ish
development (about 5 days ago or so).
Is there a tool
m...@mikesolomon.org m...@mikesolomon.org writes:
Hey all,
I'm running LilyPond on the command line from Mac OS X and it is
hanging right after printing the version. I downloaded several
versions (stable, unstable, previous unstable) and it happens with all
of them. This is a recent-ish
http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely#newcode1017
Documentation/notation/input.itely:1017: @item (on-page nmbr)
http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely#newcode1017
Documentation/notation/input.itely:1017: @item (on-page nmbr)
On 2012/07/06 07:38:05, dak wrote:
Yes, it's best to drop the verb. That is more consistent
with the rest of the table. But we are nitpicking here, aren't we :)
Done.
http://codereview.appspot.com/6347062/
___
lilypond-user mailing list
At 11:38 on 04 Jul 2012, Nathan wrote:
Here's a solution using markup paths and text spanners:
%%%
\version 2.14.2
hauptstimmeStart = \markup {
\path #0.25 #'((moveto 0 0)
(lineto 0 -2)
(moveto 0 -1)
(lineto 1 -1)
(moveto 1
On 05/07/12 22:03, David Kastrup wrote:
It also means bad compatibility with GPL. And a license change.
What's the bad compatibility you have in mind? AGPLv3 is compatible with any
code licensed GPLv2 or later. LilyPond is already on GPLv3 or later, which
has the same issues with
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes:
On 05/07/12 22:03, David Kastrup wrote:
It also means bad compatibility with GPL. And a license change.
What's the bad compatibility you have in mind? AGPLv3 is compatible
with any code licensed GPLv2 or later.
I don't see that
2012/7/6 Mark Knoop m...@opus11.net:
At 11:38 on 04 Jul 2012, Nathan wrote:
Here's a solution using markup paths and text spanners:
%%%
\version 2.14.2
hauptstimmeStart = \markup {
\path #0.25 #'((moveto 0 0)
(lineto 0 -2)
(moveto 0 -1)
Am 04.07.2012 20:55, schrieb Nick Baskin:
On Wed, Jul 4, 2012 at 2:40 PM, Thomas Morley
thomasmorle...@googlemail.com mailto:thomasmorle...@googlemail.com
wrote:
2012/7/4 Nick Baskin amphio...@gmail.com
mailto:amphio...@gmail.com:
Hey all,
Is there any way to create
Patrick or Cynthia Karl pck...@mac.com writes:
The LSR snippet Controlling of the pitch range in a score contains
the code for a function, colorizeOutOfRange. This function works at
2.14.2, but doesn't at 2.15.40.
This can be demonstrated by compiling the following:
\include ./colorize.ly
- Original Message -
From: Patrick or Cynthia Karl pck...@mac.com
To: lilypond-user@gnu.org
Sent: Friday, July 06, 2012 5:07 PM
Subject: LSR snippet Controlling of the pitch range in a score broken
at2.15.40
The LSR snippet Controlling of the pitch range in a score contains the
Phil Holmes m...@philholmes.net writes:
colorizeOutOfRange = #(define-music-function (parser location
low-note high-note music )(ly:music?
ly:music? ly:music?)
Colorizes in red notes out of range `low-note `high-note
(let* (
(low-elts (ly:music-property low-note
One suggestion, otherwise LGTM. Thanks.
http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.itely
File Documentation/notation/vocal.itely (right):
http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.itely#newcode1327
On Mon, 02 Jul 2012 21:03:46 +0400, Aleksandr Andreev
aleksandr.andr...@gmail.com wrote:
Why is this important? It would need to be possible to support
Znamenny neumatic notation, as in the following example, done in
Finale: http://ecmr.t5.fi/Transcripta/KalSamogl.pdf (except that
Finale
Hi David!
I feel very sorry that I didn't manage to make a good example for LSR that
days. Assembling the real scores was so exciting. If you will be so kind
to help me to accomplish this work, I'll make files for LSR till this
weekend.
Hoping, that you'll excuse me,
Svetlana.
On Mon,
On 06/07/12 14:49, David Kastrup wrote:
I don't see that GPLv2 permits additional restrictions to be added to
the work as a whole. The requirement to make the source available to
anybody using a service supplied by the software is an additional
restriction.
GPLv2 or later means that you can
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes:
On 06/07/12 14:49, David Kastrup wrote:
I don't see that GPLv2 permits additional restrictions to be added to
the work as a whole. The requirement to make the source available to
anybody using a service supplied by the software is
18 matches
Mail list logo
