У ср, 2010-02-03 у 23:53 +, Dositheos Rivocantus пише:
> operative system: Ubuntu 9.10 - the Karmic Koala
[...]
> \documentclass {article}
> \begin {document}
[...]
> 3: pdflatex jupp.tex
[...]
> ! Undefined control sequence.
That says pdflatex, not lilypond/lilypond-book.
Try to ask for
Updates:
Status: Accepted
Owner: ---
Labels: -fixed_2_13_12
Comment #12 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly
broken
http://code.google.com/p/lilypond/issues/detail?id=943
Sorry, I'm having "make check" problems again.
Or rather, the test-outp
Updates:
Owner: pnorcks
Comment #11 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly
broken
http://code.google.com/p/lilypond/issues/detail?id=943
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of
On Feb 3, 2010, at 5:44 PM, Hans Aberg wrote:
On 4 Feb 2010, at 00:13, Stan Sanderson wrote:
It seems that the 'lilypond' that is inside LilyPond.app*) on Mac
OS X (tried on 10.5.8) calls stuff in /usr/local/ which can cause
the program to fail by segmentation fault:
I just updated to gu
Updates:
Status: Fixed
Cc: -joeneeman
Labels: fixed_2_13_12
Comment #10 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly
broken
http://code.google.com/p/lilypond/issues/detail?id=943
Never mind. I found the culprit commit and pushed a fix.
--
You receiv
Updates:
Cc: joeneeman
Comment #9 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly
broken
http://code.google.com/p/lilypond/issues/detail?id=943
This broke between 2.13.3 and 2.13.4.
The problem doesn't appear when slurs cross line breaks on any system
besides the
fi
When setting vocal music, auto beaming is normally off, except during melisma.
I find myself constantly writing:
\autoBeamOn \melisma ... \melismaEnd\autoBeamOff
This is quite cumbersome, so much so that I normally write it like this instead:
[[ ... ]]
and run a perl script to pre-process
It may have to do with libtool, which has libltdl which Guile calls
when doing the extensibility stuff. I used libtool-2.2.6b when making
guile. So if LilyPond's guile was made with another version, but calls
stuff outside it directory, that might cause it.
Hans
__
On 4 Feb 2010, at 00:47, James Bailey wrote:
This may have to do with the order of things in your $PATH.
Possibly, unless 'lilypond' sets its own. But why is 'lilypond'
calling it? Library paths are hardcoded. And calling stuff that comes
with the OS should be called using full paths if it
operative system: Ubuntu 9.10 - the Karmic Koala
lilypond version : GNU LilyPond 2.12.2
latex:
pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6)
kpathsea version 3.5.6
Compiled with libpng 1.2.37; using libpng 1.2.37
Compiled with zlib 1.2.3.3; using zlib 1.2.3.3
Compiled with libpoppler ve
On 4 Feb 2010, at 00:13, Stan Sanderson wrote:
It seems that the 'lilypond' that is inside LilyPond.app*) on Mac
OS X (tried on 10.5.8) calls stuff in /usr/local/ which can cause
the program to fail by segmentation fault:
I just updated to guile-1.8.7 and gmp-4.3.1, and then both LilyPond
On 04.02.2010, at 00:13, Stan Sanderson wrote:
On Feb 3, 2010, at 4:20 PM, Hans Aberg wrote:
It seems that the 'lilypond' that is inside LilyPond.app*) on Mac
OS X (tried on 10.5.8) calls stuff in /usr/local/ which can cause
the program to fail by segmentation fault:
I just updated to g
On Feb 3, 2010, at 4:20 PM, Hans Aberg wrote:
It seems that the 'lilypond' that is inside LilyPond.app*) on Mac OS
X (tried on 10.5.8) calls stuff in /usr/local/ which can cause the
program to fail by segmentation fault:
I just updated to guile-1.8.7 and gmp-4.3.1, and then both LilyPond
It seems that the 'lilypond' that is inside LilyPond.app*) on Mac OS X
(tried on 10.5.8) calls stuff in /usr/local/ which can cause the
program to fail by segmentation fault:
I just updated to guile-1.8.7 and gmp-4.3.1, and then both LilyPond
2.13.7 and 2.13.11 failed - segmentation fault e
Carl Sorensen-3 wrote:
>
> On 2/2/10 1:31 AM, "David Kastrup" wrote:
>
>> Alexander Kobel writes:
>>
>>> NR 1.2.2, "Invisible rests", says that "\skip requires an explicit
>>> duration". But it is not mentioned / unspecified that this duration
>>> argument counterintuitively is not remember
On 2010-02-03, Graham Percival wrote:
> On Wed, Feb 03, 2010 at 12:17:13PM -0800, Patrick McCarty wrote:
> > On 2010-02-03, Graham Percival wrote:
> > > Yes, we've known about that for weeks. Patches accepted; I'm not
> > > interested in fixing it myself. The new website works.
> >
> > Would the
On Wed, Feb 03, 2010 at 12:17:13PM -0800, Patrick McCarty wrote:
> On 2010-02-03, Graham Percival wrote:
> > Yes, we've known about that for weeks. Patches accepted; I'm not
> > interested in fixing it myself. The new website works.
>
> Would the attached patch suffice for now?
Probably. Go ah
On 2010-02-03, Graham Percival wrote:
> Yes, we've known about that for weeks. Patches accepted; I'm not
> interested in fixing it myself. The new website works.
Would the attached patch suffice for now?
Thanks,
Patrick
>From 5b2a0425acaa67c0e11489de23ed197b2a446bbc Mon Sep 17 00:00:00 2001
Fro
Yes, we've known about that for weeks. Patches accepted; I'm not
interested in fixing it myself. The new website works.
Cheers,
- Graham
On Wed, Feb 3, 2010 at 1:31 PM, Dmytro O. Redchuk
wrote:
> Hi.
>
> http://lilypond.org/doc/v2.13/Documentation/ shows just Apache's
> "directory index" (an
Hi.
http://lilypond.org/doc/v2.13/Documentation/ shows just Apache's
"directory index" (and signature, "Apache/1.3.34 Server at lilypond.org
Port 80").
--
Dmytro O. Redchuk
LEGAL DISCLAIMER: This email was sent in hope in can help. If it is not,
feel free to ignore it or send back any helpfu
Hi.
A question: issue 999 has been merged into 305 --- does this mean that
fixing 305 will automatically fix 999?
I believe, 999 should be marked as "Verified" only if a solution for
305 fixes 999 too, that's why i'm asking.
Thanks!
___
http://code.google.com/p/lilyp
On Wed, Feb 3, 2010 at 5:11 AM, Graham Percival
wrote:
> Why forward it?
I should have added "... so I can remember to deal with it".
Cheers,
V.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
22 matches
Mail list logo
