Re: Unable to find file "ice-9/boot-9.scm" in load path

Am 02.02.2012 19:18, schrieb Ralph Palmer: On Tue, Jan 31, 2012 at 2:03 AM, Helge Krusewrote: I think this is better in the bug mailing list. Thererfore I sent it here again. I try to follow the instructions on this page: http://lilypond.org/doc/v2.14/**Documentation/extending/** scheme-sandbo

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Comment #18 on issue 2109 by benko@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 ah, you compare _those_ two versions. I attached the state between d10ec4f5 and 9f24e79a. look how the middle staff is broken; I trac

Re: Issue 2268 in lilypond: Patch: Gets left Beam bounds correct with tempo indications

Updates: Labels: -Patch-review Patch-countdown Comment #4 on issue 2268 by colinpkc...@gmail.com: Patch: Gets left Beam bounds correct with tempo indications http://code.google.com/p/lilypond/issues/detail?id=2268 (No comment was entered for this change.) ___

Re: Issue 1022 in lilypond: \chordmode neglects point-and-click

Updates: Labels: -Patch-countdown Patch-push Comment #8 on issue 1022 by colinpkc...@gmail.com: \chordmode neglects point-and-click http://code.google.com/p/lilypond/issues/detail?id=1022 Counted down to 20120202, saw a shadow, please push

Re: Issue 2263 in lilypond: Reimplement chord repetition

Updates: Labels: -Patch-countdown Patch-push Comment #15 on issue 2263 by colinpkc...@gmail.com: Reimplement chord repetition http://code.google.com/p/lilypond/issues/detail?id=2263 Counted down to 20120202, saw a shadow, please push

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Comment #17 on issue 2109 by k-ohara5...@oco.net: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 The regression test 'rest-on-nonstandard-staff.ly' has input indicating half-rest half-rest | whole-rest | whole-rest | in parallel in

Re: Issue 2243 in lilypond: Incorrect subdivision of beams

Updates: Labels: Patch-new Comment #3 on issue 2243 by carl.d.s...@gmail.com: Incorrect subdivision of beams http://code.google.com/p/lilypond/issues/detail?id=2243#c3 Fix tuplet subdivision (issue 2243) http://codereview.appspot.com/5623051

Re: Issue 990 in lilypond: automatically include property-init.ly in docs

Comment #5 on issue 990 by gra...@percival-music.ca: automatically include property-init.ly in docs http://code.google.com/p/lilypond/issues/detail?id=990 Many users can't find this file because they don't know where to look; the docs could use better direction towards this. I could discus

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Comment #16 on issue 2109 by elu...@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 maybe a little note/warning/"known issue" in the docs would reduce more confusion: in NR after: "1.2.2 Writing rests Rests are entered

Re: Issue 990 in lilypond: automatically include property-init.ly in docs

Comment #4 on issue 990 by tdaniels...@gmail.com: automatically include property-init.ly in docs http://code.google.com/p/lilypond/issues/detail?id=990 I agree with David's comment 3. We certainly don't want to include the whole of ly/property-init.ly in the docs - all users can see this f

Re: Issue 2274 in lilypond: Patch: Typo fixes

Updates: Labels: -Patch-review Patch-push Comment #2 on issue 2274 by gra...@percival-music.ca: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 2275 in lilypond: Patch: Doc: simplify example for unpure-pure containers

Updates: Labels: Patch-review Comment #2 on issue 2275 by lilypond...@gmail.com: Patch: Doc: simplify example for unpure-pure containers http://code.google.com/p/lilypond/issues/detail?id=2275#c2 Patchy the autobot says: LGTM. ___ bug-lily

Re: Issue 2274 in lilypond: Patch: Typo fixes

Updates: Labels: Patch-review Comment #1 on issue 2274 by lilypond...@gmail.com: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org ht

Re: Issue 857 in lilypond: translations status html->texinfo

Updates: Status: Verified Comment #7 on issue 857 by gra...@percival-music.ca: translations status html->texinfo http://code.google.com/p/lilypond/issues/detail?id=857 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Comment #15 on issue 2109 by benko@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 the regression test demonstrates that pitched rests were not always at the prescribed vertical position and now they are; default whole

Re: Issue 990 in lilypond: automatically include property-init.ly in docs

Comment #3 on issue 990 by d...@gnu.org: automatically include property-init.ly in docs http://code.google.com/p/lilypond/issues/detail?id=990 I am not sure what to make of this issue. property-init.ly _is_ included in the documentation (check out \xNotesOn in "Available music functions")

Issue 2275 in lilypond: Patch: Doc: simplify example for unpure-pure containers

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2275 by plros...@gmail.com: Patch: Doc: simplify example for unpure-pure containers http://code.google.com/p/lilypond/issues/detail?id=2275 Doc: simplify example for unpure-pure containers Use of ly:event-property only conf

Re: Issue 2275 in lilypond: Patch: Doc: simplify example for unpure-pure containers

Comment #1 on issue 2275 by plros...@gmail.com: Patch: Doc: simplify example for unpure-pure containers http://code.google.com/p/lilypond/issues/detail?id=2275 That's how the new output would look like Attachments: output.png 17.0 KB ___

Issue 2274 in lilypond: Patch: Typo fixes

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2274 by plros...@gmail.com: Patch: Typo fixes http://code.google.com/p/lilypond/issues/detail?id=2274 Typo fixes Fix unneeded "ll" in "canceled", "canceling" and "labeled". Replace "and" with "an" in the documentation about

Re: Unable to find file "ice-9/boot-9.scm" in load path

On Tue, Jan 31, 2012 at 2:03 AM, Helge Kruse wrote: > I think this is better in the bug mailing list. Thererfore I sent it here > again. > > I try to follow the instructions on this page: > http://lilypond.org/doc/v2.14/**Documentation/extending/** > scheme-sandbox.html

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Comment #14 on issue 2109 by k-ohara5...@oco.net: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 Assuming the input code for comment 13 was \new Staff \with { \override StaffSymbol #'line-count = 6 % also 5, and 7 } \relative

Issue 2273 in lilypond: Links in the translated documentation should point to the appropriate language if available

Status: Accepted Owner: Labels: Type-Documentation New issue 2273 by pkx1...@gmail.com: Links in the translated documentation should point to the appropriate language if available http://code.google.com/p/lilypond/issues/detail?id=2273 On http://lilypond.org/doc/v2.14/Documentation/learn

Re: Incorrect links in explicitly localized documentation

Hello, On 1 February 2012 20:52, Hans Aikema wrote: > On 1-2-2012 21:18, James wrote: >> >> Hello, >> >> On 1 February 2012 20:06, Hans Aikema  wrote: >>> >>> When explicitly browsing to a specific-language version of the userguides >>> the >>> internal links link to the 'browser preferred langua

Re: Incorrect links in explicitly localized documentation

On 1-2-2012 21:18, James wrote: Hello, On 1 February 2012 20:06, Hans Aikema wrote: When explicitly browsing to a specific-language version of the userguides the internal links link to the 'browser preferred language' version of the Userguide rather than the currently displayed version E.g. w

Re: Long monosyllabic words collide with barlines

Hi Patrick, On Thu, Feb 02, 2012 at 12:47:05PM +0100, pls wrote: > I guess this is related to Issue 2061 > (http://code.google.com/p/lilypond/issues/detail?id=2061). Even though the > status of Issue 2061 is set to fixed long monosyllabic words still collide > with barlines in LilyPond v2.15.2

Issue 2272 in lilypond: Long monosyllabic words collide with barlines

Status: New Owner: Labels: Type-Ugly New issue 2272 by colingh...@gmail.com: Long monosyllabic words collide with barlines http://code.google.com/p/lilypond/issues/detail?id=2272 Reported by Patrick http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/32939 This seems to be related t

Re: Issue 2271 in lilypond: 2.15.27 won't open on Mac 10.4 PPC

Comment #1 on issue 2271 by d...@gnu.org: 2.15.27 won't open on Mac 10.4 PPC http://code.google.com/p/lilypond/issues/detail?id=2271 According to Wikipedia, Mac OSX 10.4 "Tiger" was released in 2005, was superseded in 2007, and got its last security update in 2009 (with another security upda

Re: Issue 2270 in lilypond: Feature request: cross-staff chords

Comment #1 on issue 2270 by paconet@gmail.com: Feature request: cross-staff chords http://code.google.com/p/lilypond/issues/detail?id=2270 MS has announced a patch that implements a barebones version. This is to remind that I have promised 50 EUR to reward this feature. ___

Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time

Updates: Labels: Patch-needs_work Comment #22 on issue 2260 by lilypond...@gmail.com: line-broken spanners start too far to the right, with \tempo and \time http://code.google.com/p/lilypond/issues/detail?id=2260#c22 Patchy the autobot says: this loses the spanner in text-spanner-full

Re: Issue 1461 in lilypond: Unexpected behavior of pitchedTrill within tablature

Updates: Labels: Patch-review Comment #4 on issue 1461 by lilypond...@gmail.com: Unexpected behavior of pitchedTrill within tablature http://code.google.com/p/lilypond/issues/detail?id=1461#c4 Patchy the autobot says: LGTM. ___ bug-lilypon

Long monosyllabic words collide with barlines

Hey all, I guess this is related to Issue 2061 (http://code.google.com/p/lilypond/issues/detail?id=2061). Even though the status of Issue 2061 is set to fixed long monosyllabic words still collide with barlines in LilyPond v2.15.27. (Short) syllables don't collide: \version "2.15.27" global =

Re: Issue 1461 in lilypond: Unexpected behavior of pitchedTrill within tablature

Updates: Labels: Needs-design Comment #3 on issue 1461 by d...@gnu.org: Unexpected behavior of pitchedTrill within tablature http://code.google.com/p/lilypond/issues/detail?id=1461 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1461 in lilypond: Unexpected behavior of pitchedTrill within tablature

Updates: Labels: Patch-new Comment #2 on issue 1461 by d...@gnu.org: Unexpected behavior of pitchedTrill within tablature http://code.google.com/p/lilypond/issues/detail?id=1461#c2 Remove Pitched_trill_engraver from TabVoice context (issue 1461) Well, this is the first step for fixin

Re: Issue 1416 in lilypond: Point-and-click URIs for embedded LilyPond expressions are malformed

Updates: Status: Fixed Owner: d...@gnu.org Labels: Fixed_2_15_21 Comment #2 on issue 1416 by d...@gnu.org: Point-and-click URIs for embedded LilyPond expressions are malformed http://code.google.com/p/lilypond/issues/detail?id=1416 Since 2.15.21, the reported problem s

Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time

Comment #21 on issue 2260 by mts...@gmail.com: line-broken spanners start too far to the right, with \tempo and \time http://code.google.com/p/lilypond/issues/detail?id=2260#c21 Overhauls broken bound coordinate checking http://codereview.appspot.com/5602054 ___

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Comment #13 on issue 2109 by elu...@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 it is too confusing with these 5, 6 or 7 lines - I simply attach 2 files with the output of version 2.15.1 and 27: may somebody else try