Comment #1 on issue 2215 by mts...@gmail.com: lost commits jan 7
http://code.google.com/p/lilypond/issues/detail?id=2215
Perhaps a stupid question...when I check my local repo for these two
commits in staging-broken-jan-7, I do not find either of them. Are they in
another branch?
___
Comment #7 on issue 2191 by gra...@percival-music.ca: Web: update to
version 2.15, use it in the "site:" part
http://code.google.com/p/lilypond/issues/detail?id=2191
If you pushed that patch as-is I wouldn't complain, but please add:
to the top of the file and then push.
Comment #19 on issue 2171 by gra...@percival-music.ca: Patch: Implements
DOM-id property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
Unless Julien has any ideas, expect to wait until summer 2012. I think you
can push this now.
_
Updates:
Labels: patch-new
Comment #1 on issue 2200 by k-ohara5...@oco.net: Dots shouldn't always be
placed in one column
http://code.google.com/p/lilypond/issues/detail?id=2200
The textbooks (Ross, p170) set dots set independently for each voice. Only
dots in a chord within one voi
Comment #8 on issue 2180 by mts...@gmail.com: beams are detached from stems
http://code.google.com/p/lilypond/issues/detail?id=2180#c8
Sketch for DotColumn not triggering vertical alignment.
http://codereview.appspot.com/5538049
___
bug-lilypond mai
Comment #18 on issue 2171 by m...@apollinemike.com: Patch: Implements
DOM-id property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
I'm gonna hold off on pushing until I get a response back about build
system stuff so that I can implement a regtest that checks the SVG d
Updates:
Status: Fixed
Comment #4 on issue 2204 by mts...@gmail.com: Patch: Gets rid of PostScript
in bar-chords-notation-for-guitar--with-text-spanner.ly
http://code.google.com/p/lilypond/issues/detail?id=2204
Pushed as 5e4ca892097b1adc64c12cb75e4057e091994e04.
Updates:
Labels: Patch-new
Comment #2 on issue 2220 by julien.r...@gmail.com: Undefined references to
node in translated manuals
http://code.google.com/p/lilypond/issues/detail?id=2220#c2
Undefined references in translated manuals (issue 2220).
http://codereview.appspot.com/5539052
Updates:
Labels: Patch-new
Comment #2 on issue 2221 by julien.r...@gmail.com: Duplicate node errors in
snippets
http://code.google.com/p/lilypond/issues/detail?id=2221#c2
Add a node prefix to snippets, preventing duplicate node errors (issue
2221).
http://codereview.appspot.com/55
Issue 2221: Duplicate node errors in snippets
http://code.google.com/p/lilypond/issues/detail?id=2221
This issue is now blocking issue 2219.
See http://code.google.com/p/lilypond/issues/detail?id=2219
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Issue 2220: Undefined references to node in translated manuals
http://code.google.com/p/lilypond/issues/detail?id=2220
This issue is now blocking issue 2219.
See http://code.google.com/p/lilypond/issues/detail?id=2219
--
You received this message because you are listed in the owner
or CC fields
Updates:
Blockedon: 2220 2221
Comment #2 on issue 2219 by julien.r...@gmail.com: Set makeinfo and
texi2html error limit to zero
http://code.google.com/p/lilypond/issues/detail?id=2219
About 60 errors from translated manuals and 160 from snippets.tely
Status: Started
Owner: julien.r...@gmail.com
Labels: Type-Maintainability
New issue 2221 by julien.r...@gmail.com: Duplicate node errors in snippets
http://code.google.com/p/lilypond/issues/detail?id=2221
Some lilypond snippets are included more than once in the doc, under
different tags. For
Status: Started
Owner: julien.r...@gmail.com
Labels: Type-Maintainability
New issue 2220 by julien.r...@gmail.com: Undefined references to node in
translated manuals
http://code.google.com/p/lilypond/issues/detail?id=2220
There are a number of errors from texi2html about undefined references
Comment #1 on issue 2219 by lemzw...@gmail.com: Set makeinfo and texi2html
error limit to zero
http://code.google.com/p/lilypond/issues/detail?id=2219
I support that. BTW, how many errors from texi2html do you actually get?
___
bug-lilypond mail
Status: Started
Owner: julien.r...@gmail.com
Labels: Type-Build
New issue 2219 by julien.r...@gmail.com: Set makeinfo and texi2html error
limit to zero
http://code.google.com/p/lilypond/issues/detail?id=2219
Let's have strict error checking as part of the build process, in order to
catch an
Updates:
Labels: -Patch-review Patch-needs_work
Comment #11 on issue 2125 by julien.r...@gmail.com: Patch: Build: Don't
rebuild everything each time unless necessary.
http://code.google.com/p/lilypond/issues/detail?id=2125
make[2]: Circular out-www/essay.texi <- essay.tely dependency
Updates:
Labels: -Patch-countdown Patch-push
Comment #9 on issue 2158 by colinpkc...@gmail.com: Patch: Sketch of not
remaking html files
http://code.google.com/p/lilypond/issues/detail?id=2158
If Julien can accept the os.link code as is, then:
Counted down to 20120112, please push
Updates:
Labels: -Patch-countdown Patch-needs_work
Comment #17 on issue 2171 by colinpkc...@gmail.com: Patch: Implements
DOM-id property for grobs.
http://code.google.com/p/lilypond/issues/detail?id=2171
From Rietveld and here, it sounds as though this is still a work in process.
__
Updates:
Labels: -Patch-countdown Patch-push
Comment #6 on issue 2198 by colinpkc...@gmail.com: Document use of PATH
statement in Windows
http://code.google.com/p/lilypond/issues/detail?id=2198
Counted down to 20120112, please push
Updates:
Labels: -Patch-countdown Patch-needs_work
Comment #16 on issue 2203 by colinpkc...@gmail.com: Patch: separate
narrowed accidentals
http://code.google.com/p/lilypond/issues/detail?id=2203
Per Neil's comments
___
bug-lilypond mailin
Updates:
Labels: -Patch-countdown Patch-push
Comment #3 on issue 2204 by colinpkc...@gmail.com: Patch: Gets rid of
PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly
http://code.google.com/p/lilypond/issues/detail?id=2204
Counted down to 20120112, please push
Updates:
Labels: -Patch-new patch-new
Comment #14 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
I elected not to push this patch because of the concern about reviewing the
log.
I've now
Updates:
Labels: Patch-new
Comment #13 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c13
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Comment #6 on issue 2191 by pkx1...@gmail.com: Web: update to version 2.15,
use it in the "site:" part
http://code.google.com/p/lilypond/issues/detail?id=2191
Graham, can you look at
http://codereview.appspot.com/5530043/
I am the 'owner' of this patch, but I cannot tell if you want to push
hello,
On 12 January 2012 05:47, Graham Percival wrote:
> On Wed, Jan 11, 2012 at 12:19:27PM +0100, Janek Warchoł wrote:
>> 2012/1/10 Xavier Scheuer :
>> > I guess this message would be more appropriate on lilypond-u...@gnu.org
>> > rather than on the bug reports mailing list. May I suggest you
Status: Accepted
Owner: pkx1...@gmail.com
Labels: Type-Documentation Patch-new
New issue 2218 by pkx1...@gmail.com: Web: Added Concert to
Introduction.itexi
http://code.google.com/p/lilypond/issues/detail?id=2218
http://codereview.appspot.com/5543044/
Came from email to lilypond-user mail li
Graham Percival-3 wrote:
>
> On Thu, Jan 12, 2012 at 02:29:05AM -0800, -Eluze wrote:
>>
>> lilypond-4 wrote:
>> > This is deliberate to avoid misunderstandings in environments like
>> > frescobaldi and related "lilypond IDEs". You'll note that we create
>> > the .pdf even though it reports
On Tue, Jan 10, 2012 at 7:55 PM, Carl Sorensen wrote:
>
>
> On 1/10/12 10:03 AM, "Jean-Alexis Montignies"
> wrote:
>
> >>
> >% no problem without mark alignment to the left or lyrics
> >% third staff line is to show that there's no problem after second line
> >
> >\score {
> ><<
> >\
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2217 by ralphbug...@gmail.com: Chord names collide with notes
(vertical space missing on second line staff)
http://code.google.com/p/lilypond/issues/detail?id=2217
Jean-Alexis and Carl wrote :
% no problem without mark alignment to the
On Mon, Jan 9, 2012 at 10:54 AM, -Eluze wrote:
>
> hi
>
> everybody knows how cumbersome it is to write parameters in a shell - it
> would be nice to have them in a lilypond file.
>
> LilyPond provides an alternative for many of the command line options but
> they are not well documented in an ap
Status: Accepted
Owner:
Labels: Type-Documentation Needs-policy
New issue 2216 by ralphbug...@gmail.com: add the internal functions to
the "Application Usage" manual
http://code.google.com/p/lilypond/issues/detail?id=2216
Eluze wrote :
everybody knows how cumbersome it is to write param
On Thu, Jan 12, 2012 at 02:29:05AM -0800, -Eluze wrote:
>
> lilypond-4 wrote:
> > This is deliberate to avoid misunderstandings in environments like
> > frescobaldi and related "lilypond IDEs". You'll note that we create
> > the .pdf even though it reports an error.
>
> unbelievable! and even
lilypond-4 wrote:
>
> Updates:
> Status: Invalid
>
> Comment #1 on issue 2214 by gra...@percival-music.ca: "fatal error"
> reported when version is too old but correct output is still generated
>
> This is deliberate to avoid misunderstandings in environments like
> frescobaldi and r
Comment #18 on issue 695 by m...@apollinemike.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
I'd vote for nay - I think that the only things worth mentioning in changes
are things that'll potentially impact the way users use lilypond. If
Updates:
Labels: Patch-new
Comment #18 on issue 1846 by mts...@gmail.com: Improves horizontal spacing
of axis groups that SpanBar grobs traverse
http://code.google.com/p/lilypond/issues/detail?id=1846
Fix for comment 17 at http://codereview.appspot.com/5528081
This sorting can be del
Comment #17 on issue 695 by pkx1...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
Is this worth a mention in the 'changes' tely?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https:/
37 matches
Mail list logo
