Comment #8 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
We had some ghostscript changes for 2.13.33, IIRC. (it may have been .34
or .32) It could well have broken then, especially since th
Hello,
-Original Message-
From: Graham Percival [mailto:gra...@percival-music.ca]
Sent: Sun 10/10/2010 22:29
To: James Lowe
Cc: bug-lilypond@gnu.org
Subject: Re: Problem with volta bracket going over to next line
On Sun, Oct 10, 2010 at 04:54:17PM -0400, James Lowe wrote:
> This is the
On Sun, Oct 10, 2010 at 11:24 PM, James Lowe wrote:
> "...It can run on any platform, no matter how old or exotic, has thousands of
> users and hundreds of contributors, and makes it possible to write simple
> scores (a couple of hours is all it takes to get started) as well as complex
> 500-pa
Comment #7 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
The regression test "lyric-tie.ly" also has this problem, as you can see on
the 2.13 regtest page.
Some observations:
- In the GUB regtest ta
Hello
-Original Message-
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org on behalf of Phil
Holmes
Sent: Sat 09/10/2010 14:17
To: bug-lilypond@gnu.org
Subject: Re: Lilypond crash
Does anyone know what's the biggest single score compiled with LilyPond?
I've done the first ha
On Sun, Oct 10, 2010 at 04:54:17PM -0400, James Lowe wrote:
> This is the snippet that is as small as I can seem to get it (from a piece I
> was engraving).
What if you force a line-break with \break ? I expect that this
example could be reduced to 3 or 4 lines, using c1 and \break.
Cheers,
- G
Updates:
Labels: -Priority-Low Priority-Medium
Comment #1 on issue 1319 by v.villenave: Enhancement: an engraver for
other-hand brackets
http://code.google.com/p/lilypond/issues/detail?id=1319
Comment from Nick Payne:
" Something along these lines would also simplify the indicating o
Hello,
I did look through the tracker but nothing obvious. I have also tested this
with 2.12.latest and get the same issue.
This is the snippet that is as small as I can seem to get it (from a piece I
was engraving).
\relative c'' {
\time 6/8
\repeat volta 2 {
c8 ees, c c' ees, c |
}
Updates:
Labels: Priority-Medium
Comment #1 on issue 1268 by percival.music.ca: [PATCH] span-bar problem
http://code.google.com/p/lilypond/issues/detail?id=1268
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilyp
Updates:
Labels: Priority-Medium
Comment #1 on issue 1238 by percival.music.ca: [PATCH] Extra check in
define-event-class
http://code.google.com/p/lilypond/issues/detail?id=1238
(No comment was entered for this change.)
___
bug-lilypond ma
Updates:
Labels: Priority-Medium
Comment #1 on issue 1211 by percival.music.ca: [PATCH]Optimizations for
pure-height approximations. (issue1817045)
http://code.google.com/p/lilypond/issues/detail?id=1211
(No comment was entered for this change.)
_
Updates:
Labels: -Priority-High Priority-Medium Type-Enhancement
Comment #1 on issue 1310 by percival.music.ca: [Patch] Page breaking for
multiline embedded score
http://code.google.com/p/lilypond/issues/detail?id=1310
Issues need a type.
Updates:
Labels: Type-Enhancement
Comment #1 on issue 1315 by percival.music.ca: [Patch] Power Chords
notation for guitar tablatures
http://code.google.com/p/lilypond/issues/detail?id=1315
Issues need a type.
___
bug-lilypond mailing list
On Sun, Oct 10, 2010 at 4:03 AM, Valentin Villenave
wrote:
> On Wed, Mar 3, 2010 at 8:12 PM, Valentin Villenave
> wrote:
>> On Wed, Mar 3, 2010 at 1:58 PM, Bernard Hurley wrote:
>>> I should have come back on this one. I have taken on the task of organising
>>> a concert for a course I'm
>>> a
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1319 by v.villenave: Enhancement: an engraver for other-hand
brackets
http://code.google.com/p/lilypond/issues/detail?id=1319
This feature has been requested several times in the past[0]:
sometimes in piano music, o
On Sun, Oct 10, 2010 at 8:13 PM, Ole Schmidt wrote:
> I just checked convert-ly and musicxml2y- both work fine here with 2.13.35
> and with 2.12.3 (on a MacBook Pro 3,1 with Mac OS X 10.6.4)
OK, then Philippe must have done something wrong with his LilyPond
installation :-)
Thanks for the mid
On Oct 10, 2010, at 7:14 PM, Valentin Villenave wrote:
> On Sun, Oct 10, 2010 at 6:21 PM, James Bailey
> wrote:
>> On 10.6.4, I get this error:
>> RuntimeWarning: Python C API version mismatch for module midi: This Python
>> has API version 1013, module midi has version 1012
>> But I do get a l
On Sun, Oct 10, 2010 at 6:21 PM, James Bailey
wrote:
> On 10.6.4, I get this error:
> RuntimeWarning: Python C API version mismatch for module midi: This Python
> has API version 1013, module midi has version 1012
> But I do get a lilypond file produced, version 2.7.18…
>
> I should note that thi
Status: Accepted
Owner:
Labels: Type-Defect Priority-High OpSys-OSX midi2ly
New issue 1318 by v.villenave: midi2ly broken on Mac OS X
http://code.google.com/p/lilypond/issues/detail?id=1318
Mac OS 10.6.4 produces the following error:
RuntimeWarning: Python C API version mismatch for modul
On Sun, Oct 10, 2010 at 6:20 PM, James Bailey
wrote:
> On 10.6.4, I get this error:
> RuntimeWarning: Python C API version mismatch for module midi: This Python
> has API version 1013, module midi has version 1012
> But I do get a lilypond file produced, version 2.7.18…
I assume you're referrin
On Oct 10, 2010, at 4:30 PM, Valentin Villenave wrote:
> On Sun, Oct 10, 2010 at 4:28 PM, Valentin Villenave
> wrote:
>> Looks like there's a problem with Python libraries path variables on
>> OSX, can anyone confirm?
>
> Looks very much like http://code.google.com/p/lilypond/issues/detail?id=7
On Oct 10, 2010, at 4:30 PM, Valentin Villenave wrote:
> On Sun, Oct 10, 2010 at 4:28 PM, Valentin Villenave
> wrote:
>> Looks like there's a problem with Python libraries path variables on
>> OSX, can anyone confirm?
>
> Looks very much like http://code.google.com/p/lilypond/issues/detail?id=7
On Sun, Oct 10, 2010 at 4:28 PM, Valentin Villenave
wrote:
> Looks like there's a problem with Python libraries path variables on
> OSX, can anyone confirm?
Looks very much like http://code.google.com/p/lilypond/issues/detail?id=764
but this one had been fixed at some point, could something have
On Mon, May 17, 2010 at 12:05 AM, flup2 wrote:
> Since a few versions (in the development branch, now 2.13.21), I get that
> kind of message while running converters included in Lilypond. This is the
> message shown when running midi2ly from the Terminal under Mac OS X
>
> Could not find platform
On Sat, Oct 9, 2010 at 2:41 PM, Marten Visser wrote:
> In addition, the staff space (measured in pixels) for the default settings
> (in the example you attached) is not exaclty constant as well (I expected it
> to be). The spacing for size 0 is the smallest, and __both__ size +3 and -3
> have larg
Status: Accepted
Owner:
CC: joeneeman
Labels: Type-Defect Priority-Medium Spacing
New issue 1317 by v.villenave: between-staff-spacing doesn't scale when
changing staff size
http://code.google.com/p/lilypond/issues/detail?id=1317
% Reported by Marten Visser
http://lists.gnu.org/archive
From: Štěpán Němec
The function has been obsoleted for a long time, and recently removed
from the development version of GNU Emacs. Wrapping it in an `fboundp'
test solves the problem.
---
elisp/lilypond-mode.el |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/elisp/lil
Status: Accepted
Owner:
CC: kie...@alumni.rice.edu
Labels: Type-Enhancement Priority-Postponed Syntax
New issue 1316 by v.villenave: Enhancement: improved << \\ >> polyphonic
shortcut notation
http://code.google.com/p/lilypond/issues/detail?id=1316
The << \\ >> construct has its flaws, a
Updates:
Status: Verified
Comment #4 on issue 1207 by v.villenave: Add request to web for further
uses of or references to LilyPond
http://code.google.com/p/lilypond/issues/detail?id=1207
Implemented as @macro contactUsAbout{topic}
That's clever :-)
_
Updates:
Status: Verified
Comment #4 on issue 1280 by v.villenave: \displayMusic does not properly
quote cons lilypond properties
http://code.google.com/p/lilypond/issues/detail?id=1280
(No comment was entered for this change.)
___
bug-lil
Updates:
Status: Verified
Comment #3 on issue 1241 by v.villenave: old .bib files contain
latex-accents
http://code.google.com/p/lilypond/issues/detail?id=1241
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lil
Status: Accepted
Owner:
CC: Carl.D.Sorensen
Labels: Patch tablatures Priority-Medium
New issue 1315 by v.villenave: [Patch] Power Chords notation for guitar
tablatures
http://code.google.com/p/lilypond/issues/detail?id=1315
Patrick Schmidt has been working on adding support for power cho
Updates:
Status: Verified
Comment #5 on issue 1282 by v.villenave: the example in the third entry of
NR "4.6.2 Changing spacing" is inaccurate
http://code.google.com/p/lilypond/issues/detail?id=1282
(No comment was entered for this change.)
__
Updates:
Status: Verified
Comment #10 on issue 1244 by v.villenave: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
Closing. See issue 1272 et al. for follow-up.
___
bug-lilypond mailing list
bug-lilypond@gnu
Updates:
Status: Verified
Comment #11 on issue 1033 by v.villenave: Documentation: \new Score must die
http://code.google.com/p/lilypond/issues/detail?id=1033
From what I can see, \new Score is still used in several regtests. I have
removed it where it was absolutely unnecessary:
http
"Valentin Villenave" wrote in message
news:aanlkti=++rd-pbvcqeqm_94rnsrmatpb+cxq_tkcu...@mail.gmail.com...
Wow.
http://lsr.dsi.unimi.it/LSR/Item?id=692
http://lsr.dsi.unimi.it/LSR/Item?id=693
Cheers,
Valentin
There's a couple of unapproved ones, too. I've not approved them since I've
no cl
Updates:
Status: Verified
Comment #15 on issue 389 by v.villenave: \t -> tab in LSR snippets
http://code.google.com/p/lilypond/issues/detail?id=389
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
h
Updates:
Summary: Dynamics collide with cross-staff barlines when attached to
skips
Owner: ---
Labels: Collision
Comment #1 on issue 631 by v.villenave: Dynamics collide with cross-staff
barlines when attached to skips
http://code.google.com/p/lilypond/issues/detail?id
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1314 by v.villenave: Hairpins should not collapse into flat lines
http://code.google.com/p/lilypond/issues/detail?id=1314
% Reported by Arno months ago:
http://lists.gnu.org/archive/html/lilypond-devel/2010-03/msg00174.ht
On Wed, Mar 3, 2010 at 8:12 PM, Valentin Villenave
wrote:
> On Wed, Mar 3, 2010 at 1:58 PM, Bernard Hurley wrote:
>> I should have come back on this one. I have taken on the task of organising
>> a concert for a course I'm
>> attending and haven't had the time to investigate this further. If you
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium engraving-nitpick
New issue 1313 by v.villenave: Polyphonic rests should be centered with
simultaneous noteheads
http://code.google.com/p/lilypond/issues/detail?id=1313
This was reported (and fairly documented) by Francisco
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1312 by v.villenave: LilyPond may unrequestedly switch fonts when
using non-roman scripts
http://code.google.com/p/lilypond/issues/detail?id=1312
This report was sent on Feb 18. 2010 by John Bryant
but was blocked f
Status: Accepted
Owner:
Labels: Regression Priority-Medium Type-Defect
New issue 1311 by v.villenave: New spacing code affects user-created
pseudo-staff contexts
http://code.google.com/p/lilypond/issues/detail?id=1311
%% In the following example, a pseudo-staff context (LyricStaff) is cr
Status: Accepted
Owner:
Labels: Patch Priority-High
New issue 1310 by v.villenave: [Patch] Page breaking for multiline embedded
score
http://code.google.com/p/lilypond/issues/detail?id=1310
This patch from Boris addresses the issue raised on
http://old.nabble.com/Page-breaking-fails-for-
On Oct 10, 2010, at 12:36 AM, Graham Percival wrote:
>
> It's unfortunate that this wasn't changed ages ago... the text said
> "lilypond.org", but the target was "lilypond.org/web/", which would
> make it harder for a casual user to diagnose.
I only noticed it because of the pre-release checklis
Status: Accepted
Owner:
Labels: Type-Defect Regression Priority-Medium Spacing
New issue 1309 by v.villenave: Consecutive interrupted lyrics from
different staves are no longer aligned
http://code.google.com/p/lilypond/issues/detail?id=1309
This was reported by Dmytro months ago:
http://
Wow.
http://lsr.dsi.unimi.it/LSR/Item?id=692
http://lsr.dsi.unimi.it/LSR/Item?id=693
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Comment #3 on issue 975 by v.villenave: Font caching problem with networked
home folders
http://code.google.com/p/lilypond/issues/detail?id=975
Jake posted the following log on bug-lilypond (I know, better late than
never):
http://old.nabble.com/Re%3A-bug-lilypond-Digest%2C-Vol-87%2C-Issue
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium OpSys-OSX
New issue 1307 by v.villenave: LilyPond uses /usr/local libs rather than
its own on Mac OSX
http://code.google.com/p/lilypond/issues/detail?id=1307
This problem has been reported several times in the past:
http://old.n
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Postponed Syntax
New issue 1308 by v.villenave: Enhancement: shortcut syntax for melismas
http://code.google.com/p/lilypond/issues/detail?id=1308
This proposal was made by Russ Ross on bug-lilypond a while back:
http://old.nabble.com
Comment #4 on issue 975 by v.villenave: Font caching problem with networked
home folders
http://code.google.com/p/lilypond/issues/detail?id=975
Patrick added the following comment:
http://old.nabble.com/Bug%3A-font-caching-on-OS-X-w--networked-home-folders-tp26697903p27496213.html
"""
A quic
51 matches
Mail list logo
