Hello,
Sorry, I didn't know that attachments are being filtered out. So here is
the .ly-code (sorry, it is a little bit long)
--- snip ---
\version "2.1.34"
\header {
title = "Jaegerchor"
subtitle = "Aus dem Freischuetz"
composer = "Carl Maria von Weber"
pagenumbe
I finally managed to reproduce the funny tie I mentioned some days ago.
The tie should actually arch upwards (the notes stems point down) but it
is nearly flat with a slight downward curve. This appears to happen
under certain size and horizontal spacing contstraints.
-David
\version "2.1.34"
Hi.
Version 2.1.34 of convert-ly appears broken.
I see:
convert-ly (GNU LilyPond) 2.1.34
Processing `CwmRhondda-old.ly' ... Applying conversions: 1.5.33,
1.5.38, 1.5.40, 1.5.49, 1.5.52, 1.5.56, 1.5.58, 1.5.59, 1.5.62,
1.5.67, 1.5.68, 1.5.71, 1.5.72, 1.6.5, 1.7.1, 1.7.2, 1.7.3, 1.7.4,
1.7.5, 1.7.6
In my old score I had:
\property ChoirStaff.autoBeamSettings \override #'(end * * * *)
= #(make-moment 1 4)
convert-ly converts this to
#(override-auto-beam-setting '(end * * * *) 1 4)
To get the same semantics that should be
#(override-auto-beam-setting '(end * * *
If you look in the mailing lists, you'll find that this is one of the
most reported bugs the last days. As far as I can see Han-Wen corrected
it in the CVS Tue Mar 23 18:45:07.
/Mats
Peter Chubb wrote:
Hi.
Version 2.1.34 of convert-ly appears broken.
I see:
convert-ly (GNU LilyPond) 2.1.34
Proc
V Pá, 26. 03. 2004 v 01:29, Han-Wen Nienhuys píše:
> [EMAIL PROTECTED] writes:
> >
> > find -type f -a \! -name '*.scm' -exec sh -c '
> > sed '\''s:\(head\|tail\) -\([0-9]\):\1
> > -n\2:g;s:\(%{_prefix}/\)\(man\|info\):%{_\2dir}:g'\'' <{} >{}~
> > if ! cmp -s {} {}~ ; then cat {}~ >{} ; fi ; rm {
I got it to work now, but perhaps the instructions on the website for an
install on Windows (at least on my version of Windows, which is W2K) need to
be updated. Double-clicking on the file does not generate the pdf, neither
does entering the command 'lilypond test.ly'. But I found that if I ent
You must have found a very old version of LilyPond.
The current instructions are fully relevant for lilypond version 2.0.1,
which is what you will find on all Cygwin mirrors that have been
updated during the last months.
/Mats
Jonathan den Hartog wrote:
I got it to work now, but perhaps the in
Oh, now I can see your problem.
You haven't installed the latest (2.0.1-1) version. Just one more (or less
:-) )click in Cygwin setup.
Bert
> -Original Message-
> From: Jonathan den Hartog [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 26, 2004 4:55 PM
> To: [EMAIL PROTECTED]; [EMAIL PR
hi,
I just got a whole bunch of new programming errors. This fairly short snippet
produces:
1. A couple of these:
programming error: minimise_least_squares (): Nothing to minimise
(Continuing; crossing fingers)
2. The following warning:
/tmp/bee/progerror/piano.ly:5:10: warning: Programming e
1. The R rests are misplaced (too high in the upper, too low in the lower
staff).
2. If you comment out \key c\major (which does nothing), you get the following
warning:
warning: Change_iterator::process (): Staff = `up':
/tmp/bee/piano.ly:6:21: warning: can't change `Staff' to `down': I'm on
On Friday 26 March 2004 01.49, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > the following:
> >
> > \version "1.8.0"
> > \score {
> > \notes \grace {\property Voice.Stem \set #'stroke-style = #'() c4}
> > }
> >
> > is converted to:
> >
> > \version "1.9.0"
> > \score {
> > \notes \grace {
On Friday 26 March 2004 01.47, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > It might be too much to demand that convert-ly should upgrade
> > #'(italic "Simile")
> > to
> > \markup {\italic { "Simile" }}
> > , but the movement of a parenthesis movement is IMHO a clear bug, as
> > opposed
I sent a bug report earlier today called "funny tie". I was playing
with it a bit just now and made a discovery. The problem seems to occur
only when, as in the test file below, the line:
\override StaffSymbol #'staff-space = #(magstep -2)
The magstep is set specifically to -2.
-David
\versio
[EMAIL PROTECTED] writes:
> On Friday 26 March 2004 01.47, Han-Wen Nienhuys wrote:
> > [EMAIL PROTECTED] writes:
> > > It might be too much to demand that convert-ly should upgrade
> > > #'(italic "Simile")
> > > to
> > > \markup {\italic { "Simile" }}
> > > , but the movement of a parenthesis move
> > Really? Doing _nothing_ would actually be satisfactory.. The problem is
> > that one parenthesis is moving:
> > 1.8: a4_#'(italic "Simile") c
> > 1.9: a4_#'(italic "Simile" c)
> > so if you just would detect the #', you could assume that it would be
> > followed by a nonempty balanced parenthes
[EMAIL PROTECTED] writes:
> > Yes it would, but how would you parse a balanced parenthesis
> > expression using regular expressions?
>
> Ah.. So you're somehow limited to regexps.. explains everything :)
>
> I have to admit that for a while, I thought it was due to laziness that you
> left
Possible bug: if you specify the instrument name in the \header block,
it can throw off the justification of the music. Setting raggedright to
##f doesn't fix this; and the problem is stranger than that.
- Doug
\version "2.1.34"
\header {
title = "Suite No. 3"
composer = "J.S. Bach"
inst
The web docs mention 1.8.2 on the main site and on the bottom of the page.
http://lilypond.org/doc/v1.8/Documentation/out-www/ mentions that it is for
1.8.1 though. I don't know if correcting the webview is still preferred for
old versions or not, but if so I mentioned a finding.
_
On Friday March 26 2004 17:00, Han-Wen Nienhuys wrote:
>
> [EMAIL PROTECTED] writes:
> > > Yes it would, but how would you parse a balanced parenthesis
> > > expression using regular expressions?
> >
> > Ah.. So you're somehow limited to regexps.. explains everything :)
> >
> > I have to ad
http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Titling.html#Titling
mentions that \header can occur under \score. I used that to start
retypesetting some of my private lessons sheets. I started putting some
similar ones into a single file, but found the composer only stated
21 matches
Mail list logo
