Comment #1 on issue 1722 by x.sche...@gmail.com: Lyrics hyphen's visibility
after line break should be controllable
http://code.google.com/p/lilypond/issues/detail?id=1722
This request was also made on the French Users mailing list.
Does someone know a workaround one could use for now?
Updates:
Labels: Patch-new
Comment #9 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#c9
Uses break_align_width for bound placement of ottava bracket
http://codereview.ap
Comment #10 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#c10
Uses break_align_width for bound placement of ottava bracket
http://codereview.appspot.com/5602052
_
Comment #11 on issue 2260 by d...@gnu.org: line-broken spanners start too
far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
It is great to see progress on this one. The report is about "line
spanners", the patch appears to address ottava bracke
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2267 by mts...@gmail.com: Patch: Gets left Hairpin bounds correct
with tempo indications
http://code.google.com/p/lilypond/issues/detail?id=2267
Gets left Hairpin bounds correct with tempo indications
http://codereview.apps
Updates:
Labels: -Type-Enhancement Type-Critical
Comment #1 on issue 2267 by mts...@gmail.com: Patch: Gets left Hairpin
bounds correct with tempo indications
http://code.google.com/p/lilypond/issues/detail?id=2267
Same critical regression as 2260 but reported as a separate issue becau
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2268 by mts...@gmail.com: Patch: Gets left Beam bounds correct
with tempo indications
http://code.google.com/p/lilypond/issues/detail?id=2268
Gets left Beam bounds correct with tempo indications
http://codereview.appspot.co
Updates:
Labels: -Type-Enhancement Type-Critical
Comment #1 on issue 2268 by mts...@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.)
__
Comment #2 on issue 2268 by m...@apollinemike.com: Patch: Gets left Beam
bounds correct with tempo indications
http://code.google.com/p/lilypond/issues/detail?id=2268
After looking through the code base, this problem actually touches a lot of
grobs.
Most (if not all) of the grobs have a ca
Updates:
Labels: Patch-review
Comment #2 on issue 2267 by lilypond...@gmail.com: Patch: Gets left Hairpin
bounds correct with tempo indications
http://code.google.com/p/lilypond/issues/detail?id=2267#c2
Patchy the autobot says: LGTM.
___
b
Updates:
Labels: Patch-review
Comment #3 on issue 2268 by lilypond...@gmail.com: Patch: Gets left Beam
bounds correct with tempo indications
http://code.google.com/p/lilypond/issues/detail?id=2268#c3
Patchy the autobot says: LGTM.
___
bug-
Updates:
Labels: Patch-review
Comment #12 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#c12
Patchy the autobot says: LGTM.
___
Comment #13 on issue 2260 by n.putt...@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
@ David: the bug already existed before Jan made tempo marks
break-alignable. You can see this if you use a long
Updates:
Labels: Patch-new
Comment #14 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#c14
Overhauls broken bound coordinate checking
http://codereview.appspot.com/560205
Comment #15 on issue 2260 by m...@apollinemike.com: line-broken spanners
start too far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
This tackles the problem from a different angle that's more generic & in
keeping w/ the behavior for PaperColumn
Updates:
Labels: -Patch-new Patch-needs_work
Comment #16 on issue 2260 by d...@gnu.org: line-broken spanners start too
far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
Writing "internals.texi"...
fatal error: cannot find description for p
Updates:
Labels: Patch-new
Comment #17 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#c17
Overhauls broken bound coordinate checking
http://codereview.appspot.com/560205
Comment #18 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#c18
Overhauls broken bound coordinate checking
http://codereview.appspot.com/5602054
___
Updates:
Labels: -Patch-new Patch-needs_work
Comment #19 on issue 2260 by d...@gnu.org: line-broken spanners start too
far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
Processing
`/tmp/lilypond-autobuild/build/out/lybook-testdb/16/lily-
Updates:
Labels: Patch-new
Comment #5 on issue 451 by d...@gnu.org: Enhancement: a more flexible
\parallelMusic syntax when used with \relative
http://code.google.com/p/lilypond/issues/detail?id=451#c5
Allow music-wrapper-music as toplevel of \parallelMusic
Addresses issue 451 by all
On Tue, 31 Jan 2012 21:27:37 +0100
"m...@apollinemike.com" wrote:
> I have a patch that implements a barebones version of this that I
> haven't tinkered with for some time because of the issue of
> NoteCollision grobs.
That's great news! I'm looking forward seeing it on the issue page.
Even an
Updates:
Labels: Patch-review
Comment #6 on issue 451 by lilypond...@gmail.com: Enhancement: a more
flexible \parallelMusic syntax when used with \relative
http://code.google.com/p/lilypond/issues/detail?id=451#c6
Patchy the autobot says: LGTM.
__
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. when browsing to
http://lilypond.org/doc/v2.14/Documentation/learning/index.nl.html
with
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. when browsing to
> http:
Updates:
Status: Fixed
Labels: -Patch-push
Comment #7 on issue 2255 by pkx1...@gmail.com: Doc: NR Add @warning for
Margin adjustment'
http://code.google.com/p/lilypond/issues/detail?id=2255
committer James Lowe
Wed, 1 Feb 2012 20:22:10 + (20:22 +)
Updates:
Status: Fixed
Labels: -Patch-push
Comment #20 on issue 2189 by pkx1...@gmail.com: Doc: NR add to \partial
for clearer understanding
http://code.google.com/p/lilypond/issues/detail?id=2189
committer James Lowe
Wed, 1 Feb 2012 20:25:00 + (20:25
Updates:
Status: Fixed
Labels: -Patch-push
Comment #11 on issue 2162 by pkx1...@gmail.com: Patch: Doc: NR added
@knownissue for beam properties
http://code.google.com/p/lilypond/issues/detail?id=2162
committer James Lowe
Wed, 1 Feb 2012 20:27:11 + (20:
Updates:
Status: Fixed
Labels: -Patch-push
Comment #9 on issue 2040 by pkx1...@gmail.com: Documentation for
unpure-pure-containers
http://code.google.com/p/lilypond/issues/detail?id=2040
committer James Lowe
Wed, 1 Feb 2012 20:29:52 + (20:29 +)
co
Updates:
Status: Fixed
Labels: -Patch-push
Comment #6 on issue 2179 by pkx1...@gmail.com: Improve warnings about
spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\
{...} >> constructs
http://code.google.com/p/lilypond/issues/detail?id=2179
committer
In http://code.google.com/p/lilypond/issues/detail?id=2026#c32
Ian Hulin wrote:
This is fixed if we move the definition of the \null markup to the
before the empty-markup declaration and change empty-markup to
(define-public (empty-markup)
make-null-markup))
...
It's built the docs successfu
Comment #2 on issue 1722 by thomasmo...@gmail.com: Lyrics hyphen's
visibility after line break should be controllable
http://code.google.com/p/lilypond/issues/detail?id=1722
Hi Xavier,
this is a ugly work-around, because I didn't manage to manipulate the
LyricHyphen after the line-break, i
Comment #11 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
I'd say this too is "invalid" or "needs evidence" since "if I extend the
staff by a line..." (http://codereview.appspot.com/5434061/) move
Updates:
Labels: -Patch-needs_work Patch-new
Comment #20 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
(No comment was entered for this change.)
__
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2269 by ma...@gregoriana.sk: If piece begins with
\cueDuringWithClef, ambitus is shown in cue's clef
http://code.google.com/p/lilypond/issues/detail?id=2269
Reported by Ole V. Villumsen:
http://lists.gnu.org/archive/html/bug-lilypond/20
Hello,
2012/1/31 Ole V. Villumsen
> Cues are often used at or near the beginning of a piece. Furthermore, a
> cue is
> frequently in a different clef, so the \cueDuringWithClef command is handy.
> However, using this command at the beginning of a piece conflicts with
> displaying ambitus: The am
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 2270 by ma...@gregoriana.sk: Feature request: cross-staff chords
http://code.google.com/p/lilypond/issues/detail?id=2270
By Pavel Roskin:
http://lists.gnu.org/archive/html/bug-lilypond/2012-01/msg01274.html
In my opinion, Lilypond
Hello,
2012/1/31 Pavel Roskin
> In my opinion, Lilypond should be able to support chords with noteheads on
> different staves. This is especially important within staff groups for
> keyboard instruments.
>
This has been added as
http://code.google.com/p/lilypond/issues/detail?id=2270.
Marek Kl
Status: Accepted
Owner:
Labels: Type-Critical Regression
New issue 2271 by ma...@gregoriana.sk: 2.15.27 won't open on Mac 10.4 PPC
http://code.google.com/p/lilypond/issues/detail?id=2271
Reported by James Worlton:
http://lists.gnu.org/archive/html/bug-lilypond/2012-01/msg01272.html
I downl
Hello,
2012/1/31 James Worlton
> I downloaded the most recent development version for my Mac PPC (10.4)
> system,
> and double-clicked the LilyPond.app after extracting the .tar.bz2 file.
> Normally
> this opens up the test file that you can save & compile. This time,
> though, the
> program woul
Comment #12 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
I'd say this too is "invalid" or "needs evidence" since "if I extend the
staff by a line..." (http://codereview.appspot.com/5434061/) m
40 matches
Mail list logo
