Updates:
Status: Verified
Comment #26 on issue 887 by brownian.box: Non-ASCII characters in textedit
URIs should be percent-encoded
http://code.google.com/p/lilypond/issues/detail?id=887
(No comment was entered for this change.)
--
You received this message because you are listed in
Updates:
Status: Verified
Comment #3 on issue 1003 by brownian.box: Chord repetition: 'q' shall not
repeat fingerings
http://code.google.com/p/lilypond/issues/detail?id=1003
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or
Updates:
Status: Verified
Comment #3 on issue 981 by brownian.box:
input/regression/fermata-rest-position.ly
http://code.google.com/p/lilypond/issues/detail?id=981
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields
Comment #13 on issue 943 by n.puttock:
input/regression/slur-broken-trend.ly broken
http://code.google.com/p/lilypond/issues/detail?id=943
Hi Patrick,
I have a patch which works, but I'm hesitant to push it since I can't
explain why
commit 861b7b causes the bug.
The after-line-breaking p
Wilbert Berendsen xs4all.nl> writes:
> Can't you just write:
>
> \autoBeamOff
> a c d e[ f g] a
>
> when autobeam is off, the manual beams already trigger a melisma in the
> lyrics.
No, this does not do the same thing. Take this example
extracted from a Tallis mass:
\version "2.12.3"
\conte
As discussed on:
http://lilypond.org/doc/v2.13/Documentation/contributor/checking-and-verifying-issues#Checking-and-verifying-issues
Please check the regtest comparison, and verify any items that you can
verify. If you don't feel confident about judging an issue, leave it
alone. In a few days,
У ср, 2010-02-03 у 12:40 -0800, Patrick McCarty пише:
> On 2010-02-03, Graham Percival wrote:
> > On Wed, Feb 03, 2010 at 12:17:13PM -0800, Patrick McCarty wrote:
> > > Would the attached patch suffice for now?
> >
> > Probably. Go ahead and commit. If the website breaks in an hour
> > or two (w
They say on the Bug-Libtool list that the behavior might be changed
using 'install_name_tool'.
Hans
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Thanks. I searched both the client and the server to see if any font cache
files were being created elsewhere and this doesn't seem to be the case. I
do have the following the client's system.log file however:
Feb 2 11:26:29 camil15 kernel[0]: encodings.dir/rsrc: file access by
'/rsrc' was depr
>
> Thanks. I searched both the client and the server to see if any font cache
> files were being created elsewhere and this doesn't seem to be the case. I
> do have the following the client's system.log file however:
Feb 2 11:26:29 camil15 kernel[0]: encodings.dir/rsrc: file access by
'/rsrc'
I have done some more debugging, and the result is surprising:
When I move only /usr/local/lib/libltdl.7.dylib to another name, then
lilypond works; however, dtruss shows that it calls /usr/lib/libltdl.
7.dylib !
So lilypond may never have called
/Applications/LilyPond.app/Contents/Resourc
\version "2.13.10"
%{
When a secondary score has a piece or opus header (i.e. it prints something
above it) the score is put closer to the preceding score than when there is
no header in the secondary score.
%}
\header {
title = "Title"
}
\paper {
ragged-last-bottom = ##f
}
music = \r
Op donderdag 04 februari 2010 schreef Russ:
> \autoBeamOn \melisma ... \melismaEnd\autoBeamOff
Can't you just write:
\autoBeamOff
a c d e[ f g] a
when autobeam is off, the manual beams already trigger a melisma in the
lyrics.
best regards,
Wilbert Berendsen
--
Frescobaldi, LilyPond editor
Addition:
The Guile manual, sec. 4.2.1, says:
It will look in the places that are usual for your operating
system, and it
will additionally look into the directories listed in the
LTDL_LIBRARY_PATH
environment variable.
So guile is probably hardwired to look into /usr/local/lib/. It m
One can use 'dtruss lilypond empty', which the writes the stuff below.
So for some reason, lilypond does call stuff in /usr/local/lib/. And
it seems, as I thought, that it is libltdl that is the problem - I
used a different version.
The Guile manual, sec. 4.2.1, says that it uses LTDL_LIBRA
On 4 Feb 2010, at 04:59, Stan Sanderson wrote:
I just tested it on my PPC 10.5.8 with Lily 2.13.10. It was a
relatively short .ly file, but there were no errors reported.
Tested what?
My apologies if it wasn't clear that I compiled a .ly source file
using Lilypond 2.13.10 without moving a
16 matches
Mail list logo
