On Sun, May 20, 2012 at 08:53:05AM +0200, Janek Warchoł wrote:
> On Sun, May 20, 2012 at 2:32 AM, Neil Thornock wrote:
> > Not sure why nothing was mentioned on the website.
>
> I'm not happy with this practice, either.
I eagerly await your patch. If it looks ok I'll tell you to push
directly t
On Sun, May 20, 2012 at 2:32 AM, Neil Thornock wrote:
> According to this list:
>
> http://code.google.com/p/lilypond/issues/list
>
> it looks like critical issues were found.
Yes, they were.
> Not sure why nothing was mentioned on the website.
I'm not happy with this practice, either.
On the o
Il 19/05/2012 19:47, Bernardo Barros ha scritto:
On 05/19/2012 09:47 AM, Federico Bruni wrote:
If you want to keep the easy to use interface, you can use SparkleShare,
free alternative to Dropbox:
http://sparkleshare.org/
Free in what sense? Do they encrypt your data, in a way that only the
o
On Thu, May 17, 2012 at 12:36:35PM +0200, Christian Andersson wrote:
> Now, sit down and await all flames from proponents of all the other tools!
Saving different versions of files to floppy disks and writing a
label in a thick pen was good enough for us in 1986. Especially
when we re-used a flop
According to this list:
http://code.google.com/p/lilypond/issues/list
it looks like critical issues were found. Not sure why nothing was
mentioned on the website.
On Fri, May 18, 2012 at 4:51 PM, Tom Cloyd wrote:
> I've had it marked on my calendar for days that May 17 is the scheduled
> relea
Hi,
today i've found this snippet: http://lsr.dsi.unimi.it/LSR/Item?id=646
> The description says that it needs manual beaming to work, but i've
> tried using it with 2.15.36 and manual beaming was not necessary!
> The only downside i see is that non-kneed tuplets are positioned
> wrongly, so one
[Trying again on this one, to see if my posts are finally getting
through...]
Urs,
I'm not much of a programmer, but to me this seems to be both a good
idea and an easy one to implement. Here's how I'd do it, since [a] I
don't program in Scheme at all, and [b] I do have some skills in Ruby:
On Sat, May 19, 2012 at 5:02 PM, David Nalesnik wrote:
> I'll have to investigate, but possibly the actual override of 'Y-offset
> (or calling other functions related to Y) is having new effects. (You can
> see one effect by adding \override TupletBracket #'bracket-visibility = ##t
> -- no eff
Hi Janek,
today i've found this snippet: http://lsr.dsi.unimi.it/LSR/Item?id=646
> The description says that it needs manual beaming to work, but i've
> tried using it with 2.15.36 and manual beaming was not necessary!
> The only downside i see is that non-kneed tuplets are positioned
> wrongly, s
Urs,
I'm not much of a programmer, but to me this seems to be both a good
idea and an easy one to implement. Here's how I'd do it, since [a] I
don't program in Scheme at all, and [b] I do have some skills in Ruby:
1. Insert all comments in the source with a leading "%|". The second
character
Hi,
Have you tried doxygen? It's pretty wide used among C/C++ developers
to produce documentation. You just need to override comment characters
and I believe you're done.
--
Thanks, Andriy Senkovych
2012/5/19 Urs Liska :
> Hi list,
>
> any ideas/experience on parsing lilypond input files for sp
I cannot post to the list, for some reason.
Have been a list member for years.
Can anyone help with this?
This post is being made using the resource at -
http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general
t.
___
lilypond-user m
Congratulations for touching upon a "hot" subject, pretty much like asking
people what text editor to use, something that has been debated for decades
without any objective conclusion.
Personally I tend to prefer git, not only for lilypond score projects, but
for anything text-oriented. This is ma
Hi,
I'm using git as well to write notes for my ensemble and host them on
github[1]. There's at least one more person hosting notes there
(actually, contributing for the Mutopia project)[2] so I believe it's
pretty common to use a VCS tool of someone's choice. You may browse
the links and get the
I've had it marked on my calendar for days that May 17 is the scheduled
release date, " If no Critical bugs are found..." (Ly website).
The website in no way indicates that this occurred, nor are there any
announcements that I can find on this list.
Can someone provide a status update re: thi
Dear Scheme Heroes,
today i've found this snippet: http://lsr.dsi.unimi.it/LSR/Item?id=646
The description says that it needs manual beaming to work, but i've
tried using it with 2.15.36 and manual beaming was not necessary!
The only downside i see is that non-kneed tuplets are positioned
wrongly,
Here is an experiment I did with a hybrid web/notation approach:
http://soupgreens.com/goodbyebooze/
Notice that everything but the notes is the standard browser stack.
As an example of the benefit, the lyrics scale nicely if you zoom in or out
with the browser. Or you could easily embed a commen
On 05/19/2012 09:47 AM, Federico Bruni wrote:
>
> If you want to keep the easy to use interface, you can use SparkleShare,
> free alternative to Dropbox:
> http://sparkleshare.org/
Free in what sense? Do they encrypt your data, in a way that only the
owner have access to it?
--
Bernardo Barros
Hi Derek,
> Do you have any ideas how I could print a two-line copyright notice on the
> first page?
copyright = \markup \column { ... }
Read the markup docs for more details.
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.
I have noticed that for each field in the header of a piece, there is only one
line allowed. In some cases I have used two separate fields to print a header on
two lines, such as:
composer = "Words and music by"
arranger = "composer's name"
In some pieces, I would like to have the copyright field
Il 17/05/2012 13:11, Francisco Vila ha scritto:
2012/5/17 Urs Liska:
OK, but please keep in mind everybody that I specifically asked for the use
with lilypond projects ...
It's no need to be specifically for lilypond to be perfect for
lilypond. It only has to be perfect for text files, and git
Hi David,
On Sat, May 19, 2012 at 3:30 PM, David Nalesnik
wrote:
> This isn't a bug: cross-staff arpeggios belong to a different context. In
> your case, they are a part of PianoStaff, so the override will have no
> impact.
Ah, silly me! Thank you very much!
And by the way, once again you gave
Hi Janek,
On Sat, May 19, 2012 at 8:17 AM, Janek Warchoł wrote:
> Hi David,
>
> On Sat, May 19, 2012 at 2:56 PM, David Nalesnik
> wrote:
> > OK, this incorporates your idea of looping. You specify a list as the
> > argument of the function, and that grouping will loop until the end. The
> > ex
Hi Janek,
On Sat, May 19, 2012 at 8:03 AM, Janek Warchoł wrote:
> Hi David & all,
>
> i want to make arpeggios longer (so that they overshoot the chords a
> bit). I've modified your offsetBeamPositions function to work on
> Arpeggios instead of Beams (that was easy), but i'm quite surprised to
>
Hi David,
On Sat, May 19, 2012 at 2:56 PM, David Nalesnik
wrote:
> OK, this incorporates your idea of looping. You specify a list as the
> argument of the function, and that grouping will loop until the end. The
> example below shows how you would get four measures per line. The score
> ends w
There seems to be some conceptual overlap here with "literate
programming" tools such as WEB (http://en.wikipedia.org/wiki/WEB).
Whether there's enough overlap to be useful ... that I must leave
you to decide.
/Christopher/.
On 2012-05-19 14:56, lilypond-user-requ...@gnu.org wrote:
Subject
Hi Johan,
Please submit to LSR...
Will do. The LSR is running 2.14.2 right now, so I'll have to make some
changes. (In particular, the function uses David Kastrup's make-engraver
macro which is fairly recent.)
-David
___
lilypond-user mailing list
l
Hi David & all,
i want to make arpeggios longer (so that they overshoot the chords a
bit). I've modified your offsetBeamPositions function to work on
Arpeggios instead of Beams (that was easy), but i'm quite surprised to
find that it doesn't work correctly with cross-staff arpeggios. Do
you have
Hi again Janek,
On Sat, May 19, 2012 at 6:40 AM, David Nalesnik wrote:
> Hi Janek,
>
> On Sat, May 19, 2012 at 4:27 AM, Janek Warchoł
> wrote:
>
>> David,
>>
>> a couple of thoughts:
>> - what about looping the break pattern? I.e. \consists
>> #(custom-line-breaks-engraver '(2 3 4)) = \consists
Hi Janek,
On Sat, May 19, 2012 at 4:27 AM, Janek Warchoł wrote:
> David,
>
> a couple of thoughts:
> - what about looping the break pattern? I.e. \consists
> #(custom-line-breaks-engraver '(2 3 4)) = \consists
> #(custom-line-breaks-engraver '(2 3 4 2 3 4 2 3 4 ... 2 3 4))?
>
Great idea--this m
2012/5/19 Helge Kruse :
> I have a score with "da capo al coda". And the coda is exactly one measure.
> Therefore I don't want to put the coda on a new line. But it should be a gap
> between the last measure of the main part and the coda. Additionally I would
> like to indicate that the last measur
David Nalesnik writes:
> Hope this proves useful!
Please submit to LSR...
-- Johan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi list,
any ideas/experience on parsing lilypond input files for special
comments and produce some documentation from it?
I would love to write editorial comments directly in the lilypond source.
Some script could then read these from the source and produce html or
OpenDocumentText or some l
David,
a couple of thoughts:
- what about looping the break pattern? I.e. \consists
#(custom-line-breaks-engraver '(2 3 4)) = \consists
#(custom-line-breaks-engraver '(2 3 4 2 3 4 2 3 4 ... 2 3 4))?
- i'm not sure if this is desired or not, but changing current
barNumber confuses your function:
I have a score with "da capo al coda". And the coda is exactly one
measure. Therefore I don't want to put the coda on a new line. But it
should be a gap between the last measure of the main part and the coda.
Additionally I would like to indicate that the last measure _is_ the coda.
I have wri
David:
8O
I think this is worth including in LilyPond itself!!
Try to beat this, Finale! Hahaha!
On Sat, May 19, 2012 at 9:31 AM, ole wrote:
> Just want to report that the improved version gives the following error:
>
> /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ly/init.
Am 19.05.2012 um 04:19 schrieb David Nalesnik:
> Hi,
>
> On Fri, May 18, 2012 at 7:38 PM, Jay Anderson wrote:
>
>> Slightly better would be to get rid of the bars-per-line define so
>> it's self-contained:
>>
>
> True, thank you--I've incorporated your suggestion below.
>
> Thinking about t
37 matches
Mail list logo
