Updates:
Labels: Patch-new
Comment #6 on issue 2113 by carl.d.s...@gmail.com: Beamlet points the wrong
way when tuplet sixteenths are beamed with eighths
http://code.google.com/p/lilypond/issues/detail?id=2113#c6
Fix beamlet pointing wrong way when tuplet 16th beamed with 8th (issue 2
Comment #10 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of
StringNumber leads to "programming error" messages
http://code.google.com/p/lilypond/issues/detail?id=2085
Another solution is to \override 'stencil to 'point-stencil instead of #f.
This is described in the Learning
Comment #5 on issue 1392 by pkx1...@gmail.com: Internals Reference should
document \paper variables
http://code.google.com/p/lilypond/issues/detail?id=1392
Here is a very rough and ready file - just here for anyone else to
use/change etc.
All done alphabetically taking the define-paper-va
Updates:
Labels: -Patch-review Patch-needs_work
Comment #3 on issue 2115 by pkx1...@gmail.com: Documentation: Add note to
show how to find valid entries for \language in Usage
http://code.google.com/p/lilypond/issues/detail?id=2115
Comments from Graham.
_
This bug is still present in 2.15.22 that was just released
Thomas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Comment #3 on issue 2112 by pkx1...@gmail.com: documentation: precising
-dpreview
http://code.google.com/p/lilypond/issues/detail?id=2112
Made a trivial edit from Ian H (removed the word 'The') I don't think this
needs another LGTM from Patchy.
James
Comment #4 on issue 2114 by pkx1...@gmail.com: documentation: more
nitpicking on application usage
http://code.google.com/p/lilypond/issues/detail?id=2114
Made a trivial edit from Ian H (removed the word 'The') I don't think this
needs another LGTM from Patchy.
__
Updates:
Labels: Patch-review
Comment #1 on issue 2116 by lilypond...@gmail.com: Patch: Shows Flags in
tabFullNotation
http://code.google.com/p/lilypond/issues/detail?id=2116#c1
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Updates:
Labels: Patch-review
Comment #5 on issue 2113 by lilypond...@gmail.com: Beamlet points the wrong
way when tuplet sixteenths are beamed with eighths
http://code.google.com/p/lilypond/issues/detail?id=2113#c5
Patchy the autobot says: LGTM.
Updates:
Labels: Patch-review
Comment #9 on issue 2085 by lilypond...@gmail.com: Overriding stencil of
StringNumber leads to "programming error" messages
http://code.google.com/p/lilypond/issues/detail?id=2085#c9
Patchy the autobot says: LGTM.
___
Updates:
Labels: Patch-review
Comment #3 on issue 2114 by lilypond...@gmail.com: documentation: more
nitpicking on application usage
http://code.google.com/p/lilypond/issues/detail?id=2114#c3
Patchy the autobot says: LGTM.
___
bug-lilypond
Updates:
Labels: Patch-review
Comment #2 on issue 2112 by lilypond...@gmail.com: documentation: precising
-dpreview
http://code.google.com/p/lilypond/issues/detail?id=2112#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
bug
lilyp...@googlecode.com writes:
> Comment #4 on issue 2099 by gra...@percival-music.ca: texi2pdf --quiet
> hides too much
> http://code.google.com/p/lilypond/issues/detail?id=2099
>
> if it's undefined in texinfo, then why did makeinfo accept it with no
> fuss?
> Anyway, in this case I would rath
Status: Accepted
Owner:
Labels: Type-Build
New issue 2117 by philehol...@gmail.com: Update git-cl to use Type-Patch
http://code.google.com/p/lilypond/issues/detail?id=2117
Patches on Rietveld being tracked here should now have their type label set
to Type-Patch. Line 74 of projecthosting
Updates:
Labels: Patch-new
Comment #8 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of
StringNumber leads to "programming error" messages
http://code.google.com/p/lilypond/issues/detail?id=2085#c8
Allow string numbers to have #f stencil without programming error (Issue
On Dec 17, 2011, at 4:39 PM, Thomas Morley wrote:
> Hi,
>
> this doesn't print flags with "2.15.20", but it does with "2.14.2".
>
>
> \version "2.14.2"
> %\version "2.15.20"
> \new TabStaff { \tabFullNotation c8 }
>
>
> Cheers,
> Harm
Thanks.
There is a patch up to fix this as
http://code
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2116 by mts...@gmail.com: Patch: Shows Flags in tabFullNotation
http://code.google.com/p/lilypond/issues/detail?id=2116
Shows Flags in tabFullNotation
http://codereview.appspot.com/5494063
___
Updates:
Labels: Patch-new
Comment #4 on issue 2113 by carl.d.s...@gmail.com: Beamlet points the wrong
way when tuplet sixteenths are beamed with eighths
http://code.google.com/p/lilypond/issues/detail?id=2113#c4
Fix beamlet pointing wrong way when tuplet 16th beamed with 8th (issue 2
Comment #4 on issue 2099 by gra...@percival-music.ca: texi2pdf --quiet
hides too much
http://code.google.com/p/lilypond/issues/detail?id=2099
if it's undefined in texinfo, then why did makeinfo accept it with no
fuss? I wish that programs would immediately give an error instead of
accept
Hi,
this doesn't print flags with "2.15.20", but it does with "2.14.2".
\version "2.14.2"
%\version "2.15.20"
\new TabStaff { \tabFullNotation c8 }
Cheers,
Harm
<><>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/li
Comment #3 on issue 2099 by d...@gnu.org: texi2pdf --quiet hides too much
http://code.google.com/p/lilypond/issues/detail?id=2099
That is not "for some reason" but because you write @\ in the middle, and
that is undefined in Texinfo. You probably wanted to write @@ instead.
Since @verbatim
Comment #2 on issue 2099 by gra...@percival-music.ca: texi2pdf --quiet
hides too much
http://code.google.com/p/lilypond/issues/detail?id=2099
ok, that file had what I needed. So yes, printing something that points to
that file if that part of the build fails would be great.
For the recor
Comment #1 on issue 2099 by philehol...@gmail.com: texi2pdf --quiet hides
too much
http://code.google.com/p/lilypond/issues/detail?id=2099
I've just been checking this, and in essence this already happens. When
texi2pdf runs, it always (AFAICS) writes a log of progress to DocName.log
in
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_23
Comment #13 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -
behavior of make doc
http://code.google.com/p/lilypond/issues/detail?id=2075
Pushed as 06aadb4af78fb061726d9f91ab7e2bb52eab59e8
Comment #2 on issue 2114 by pkx1...@gmail.com: documentation: more
nitpicking on application usage
http://code.google.com/p/lilypond/issues/detail?id=2114
*new* Patch uploaded
http://codereview.appspot.com/5496063
Includes issue 2112
James
___
Updates:
Owner: pkx1...@gmail.com
Labels: Patch-new
Comment #1 on issue 2112 by pkx1...@gmail.com: documentation: precising
-dpreview
http://code.google.com/p/lilypond/issues/detail?id=2112
Patch uploaded
http://codereview.appspot.com/5496063
Includes issue 2114
__
Updates:
Labels: Patch-review
Comment #3 on issue 2113 by lilypond...@gmail.com: Beamlet points the wrong
way when tuplet sixteenths are beamed with eighths
http://code.google.com/p/lilypond/issues/detail?id=2113#c3
Patchy the autobot says: LGTM.
Updates:
Labels: Patch-review
Comment #2 on issue 2115 by lilypond...@gmail.com: Documentation: Add note
to show how to find valid entries for \language in Usage
http://code.google.com/p/lilypond/issues/detail?id=2115#c2
Patchy the autobot says: LGTM.
___
Updates:
Labels: Patch-review
Comment #3 on issue 2090 by lilypond...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090#c3
Patchy the autobot says: LGTM.
___
bug-lilypo
Updates:
Labels: Patch-review
Comment #7 on issue 2085 by lilypond...@gmail.com: Overriding stencil of
StringNumber leads to "programming error" messages
http://code.google.com/p/lilypond/issues/detail?id=2085#c7
Patchy the autobot says: LGTM.
___
Updates:
Labels: -Patch-new Patch-needs_work
Comment #2 on issue 2113 by carl.d.s...@gmail.com: Beamlet points the wrong
way when tuplet sixteenths are beamed with eighths
http://code.google.com/p/lilypond/issues/detail?id=2113
(No comment was entered for this change.)
_
Updates:
Status: Started
Labels: Patch-new
Comment #1 on issue 2114 by pkx1...@gmail.com: documentation: more
nitpicking on application usage
http://code.google.com/p/lilypond/issues/detail?id=2114
Patch uploaded
http://codereview.appspot.com/5492066
James
"James" wrote in message
news:CA+T3wFkwPpSLDgkFNg7-6N6SX4j3Ee=vc_78h+pcsd0dbx+...@mail.gmail.com...
Hello,
http://code.google.com/p/lilypond/issues/detail?id=2115
Hope the bug squadders don't mind.
--
James
Nope. You're an associate.
--
Phil Holmes
Bug Squad
_
Updates:
Owner: pkx1...@gmail.com
Labels: Patch-new
Comment #1 on issue 2115 by pkx1...@gmail.com: Documentation: Add note to
show how to find valid entries for \language in Usage
http://code.google.com/p/lilypond/issues/detail?id=2115
Patch uploaded
http://codereview.appspot
Comment #6 on issue 1995 by pkx1...@gmail.com: scheme-tutorial.itely: avoid
unnecessary copying
http://code.google.com/p/lilypond/issues/detail?id=1995
Thanks David, of course I wasn't casing aspersions on your Tex knowledge :)
but just offering to do the 'dull' work while you get on with the
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2115 by pkx1...@gmail.com: Documentation: Add note to show how to
find valid entries for \language in Usage
http://code.google.com/p/lilypond/issues/detail?id=2115
in
http://lilypond.org/doc/v2.15/Documentation/usage-big-page#e
Hello,
On 17 December 2011 11:22, -Eluze wrote:
>
> sorry to not come up with all these things together - here are 2 new request
> for small adaptations in AU
>
> again under
> http://lilypond.org/doc/v2.15/Documentation/usage-big-page#command-line-options-for-lilypond
> you can find options encl
Status: Accepted
Owner: pkx1...@gmail.com
Labels: Type-Documentation
New issue 2114 by pkx1...@gmail.com: documentation: more nitpicking on
application usage
http://code.google.com/p/lilypond/issues/detail?id=2114
sorry to not come up with all these things together - here are 2 new request
fo
Comment #5 on issue 1995 by d...@gnu.org: scheme-tutorial.itely: avoid
unnecessary copying
http://code.google.com/p/lilypond/issues/detail?id=1995
Hi James,
I don't have a problem with Texinfo, but the basic statement of the review
was that the whole section should be rewritten rather than
sorry to not come up with all these things together - here are 2 new request
for small adaptations in AU
again under
http://lilypond.org/doc/v2.15/Documentation/usage-big-page#command-line-options-for-lilypond
you can find options enclosed in apostrophs:
-d,--define-default=var=val
…
Here are a
Updates:
Labels: -Patch-abandoned
Comment #4 on issue 1995 by pkx1...@gmail.com: scheme-tutorial.itely: avoid
unnecessary copying
http://code.google.com/p/lilypond/issues/detail?id=1995
@Ian H and @David K (mainly)
Looking over this, it seems to me that this was about 80% 'there', I'
Comment #1 on issue 2111 by pkx1...@gmail.com: documentation of
include-settings in Usage
http://code.google.com/p/lilypond/issues/detail?id=2111
You didn't really give me much constructive to work with here.
The reason is probably because either no one has had an issue with it
before, no
Comment #1 on issue 1999 by pkx1...@gmail.com: Nonsensical example in
programming-interface.itely
http://code.google.com/p/lilypond/issues/detail?id=1999
The current problematic example is here:
http://lilypond.org/doc/v2.15/Documentation/extending-big-page#inline-scheme-code
Anyone who und
Updates:
Status: Started
Owner: pkx1...@gmail.com
Labels: Patch-new
Comment #2 on issue 2090 by pkx1...@gmail.com: Add documentation for
command line quoting on Windows
http://code.google.com/p/lilypond/issues/detail?id=2090
Patch uploaded:
http://codereview.appspot.c
Werner LEMBERG writes:
>> Come to think of it, the least invasive strategy might be hybrid:
>> one does not try tracking the relation between q and the preceding
>> chord at all but leaves it in the input side. \relative just throws
>> away the existing contents of any q it encounters and replac
Comment #15 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Well, for things like fingerings, I don't think the difference can easily
go away: inside of a chord, fingerings will need to ge
Comment #12 on issue 2102 by k-ohara5...@oco.net: vertical spacing of a
nonstaff line below the system
http://code.google.com/p/lilypond/issues/detail?id=2102
The initial example is an example of the situation that Carl brings up.
The patch handles the case of Dynamics, with 'staff-affinity=
47 matches
Mail list logo
